Lydiot wrote in Tue Sep 08, 2015 9:33 pm:So if I understand correctly what you're saying is that "everyone" is working on the same version, and once a certain point is reached it is branched. Then some of the people can move on because they're no longer essential to the branch which will be released sooner, and the remaining people will finish it?
I'm not criticizing anyone or complaining that it's later or anything, just trying to understand the process.
This is the standard development practice in most projects. Before a release the developers are told to hit the breaks on any features they plan, and that they should concentrate purely on fixing bugs and preparing the software for release to users. Once this freeze period is over, the release is tagged. Then the gates are opened and the developers are let out free into the wild
All of the features they had been sitting on during the freeze can then flow into the project, without affecting the tagged and isolated release code. As the majority of developers run free, one or two poor buggers have the hard job of preparing the release and taking the final steps, building the binaries and distribution files, testing them, uploading them, updating a tonne of infrastructure for the new version number, preparing press releases, etc.
Regards,
Edward