Roles for Git

[Mercury Thirteen]

As Tony suggested, let's define some roles for the branches of our Git repository.

We should have one "supervisor" of sorts for each branch. I'm thinking we all can contribute code to Development, and I'll head up that branch. Tony has volunteered to lead the QA branch which will also incorporate stress testing the code after it graduates out of Development. Do we need a leader for Master as well? I don't imagine there being much to do with code which has already passed two other branches.

[Antony]

Perhaps a committee approach to Master as it is the version that will be released to the public.

Unfortunately, I don't have a physical machine, I can only test in emulators/VM

[Mercury Thirteen]

On Monday, July 27, 2015 at 4:27:07 PM UTC-4, Antony wrote:

Perhaps a committee approach to Master as it is the version that will be released to the public.

Sounds good.

Unfortunately, I don't have a physical machine, I can only test in emulators/VM

No matter, I'm using nothing but a VM as well. I have several other computers I can turn into test machines as needed if necessary.

[maarten]

I have a laptop from 11 years ago.... I use it for testing an exploring an OS.
So if needed I can also test on that thing.

[maarten]

This isn't up to date anymore:

Last year it has messed itself up, so that one isn't alive anymore.