Giving MCServer a version number
#17
The general approach would be to split the repo into three tracks, release, testing and trunk. release track would not have any changes applied directly, testing would only have bugfixes merged not features, and trunk would be where features would be added. Then every few weeks/months we would take the trunk and make that the new testing and make what was in testing the new release. The actual planning of features would continue as we are now, its just they would get more testing and bugfixing before reaching release.
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 worktycho - 03-30-2015, 06:08 AM
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 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: 1 Guest(s)