05-10-2015, 10:17 AM
master is simply same as always all commits go there,
At a point when somebody finds its time to start testing roll outs aka pre-stable it gets put into testing.
any bugs found will be put into master at that time testing will just be updated and updated and updated, until master sync tester sync stable
This is just my understanding how it mostly go's.
There is no use in separating testing completely from master by implementing fixes into it and skipping master.
Its called master for a reason.
Of course as before big things that you test would probably still get there own spot like always, as it could break a lot of stuff in master.
If people start a re-write of (sample) the socket system.
But i might be wrong though, i am quite random..
At a point when somebody finds its time to start testing roll outs aka pre-stable it gets put into testing.
any bugs found will be put into master at that time testing will just be updated and updated and updated, until master sync tester sync stable
This is just my understanding how it mostly go's.
There is no use in separating testing completely from master by implementing fixes into it and skipping master.
Its called master for a reason.
Of course as before big things that you test would probably still get there own spot like always, as it could break a lot of stuff in master.
If people start a re-write of (sample) the socket system.
But i might be wrong though, i am quite random..