Giving MCServer a version number
#36
(05-09-2015, 12:07 AM)bearbin Wrote: Yep.

@worktycho 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.
Reply
Thanks given by:


Messages In This Thread
Giving MCServer a version number - by sphinxc0re - 03-28-2015, 06:58 AM
RE: Giving MCServer a version number - by Jammet - 03-28-2015, 11:54 PM
RE: Giving MCServer a version number - by xoft - 03-29-2015, 04:53 AM
RE: Giving MCServer a version number - by xoft - 03-29-2015, 05:26 AM
RE: Giving MCServer a version number - by xoft - 03-29-2015, 08:32 PM
RE: Giving MCServer a version number - by xoft - 05-08-2015, 08:20 AM
RE: Giving MCServer a version number - by bearbin - 05-08-2015, 04:34 PM
RE: Giving MCServer a version number - by bearbin - 05-09-2015, 12:07 AM
RE: Giving MCServer a version number - by LogicParrot - 05-09-2015, 02:03 AM
RE: Giving MCServer a version number - by bearbin - 05-09-2015, 12:52 AM
RE: Giving MCServer a version number - by tigerw - 05-09-2015, 01:14 AM
RE: Giving MCServer a version number - by bearbin - 05-09-2015, 01:33 AM
RE: Giving MCServer a version number - by bearbin - 05-09-2015, 02:16 AM
RE: Giving MCServer a version number - by tigerw - 05-09-2015, 02:32 AM
RE: Giving MCServer a version number - by bearbin - 05-09-2015, 02:34 AM
RE: Giving MCServer a version number - by tigerw - 05-09-2015, 02:55 AM
RE: Giving MCServer a version number - by tigerw - 05-09-2015, 09:07 AM
RE: Giving MCServer a version number - by tigerw - 05-09-2015, 10:18 PM



Users browsing this thread: 18 Guest(s)