Yep. So we need to have had a testing branch for a few weeks before creating stable.
We probably also need tags for bugs - testing/stable/master?
And will we link only stable executables on the webpage then?
(05-09-2015, 12:07 AM)bearbin Wrote: [ -> ]Yep.
can you confirm this flow as correct?
master -> testing -> stable
where master is updated all the time, and merged into testing every 2/3 weeks, bugs are fixed in testing then merged back into master, then after 2/3 weeks testing is promoted into stable.
The time period doesn't have to be constant. For example, Debian packages are promoted to the next branch when there are no bugs at all for (10?) days.
I don't think MCServer is likely to be in a position of having 0 bugs anytime soon
Who's going to test the testing branch?
Just like the people who test the bukkit testing branch - normal server owners who want a more updated server.
Also, I created some builds for the testing branch, you can find them on the buildserver.
Then why not have master as testing?