Am 16.02.2012 23:20, schrieb Alessandro Molina:
Actually I always thought that the next branch was only for release process like stated on http://www.turbogears.org/book/appendices/preprelease.html#finalizing-changes-on-next-branch
Makes sense, then this is only intended as a temporary branch.
I always used the "development" branch for bugfixes that should have gone in the next to come release.
But if that next release will be 2.2 and we later want to release a 2.1.5 bugfix we should also have a separate 2.1 branch (which still supports Py2.4 and works without Crank). Since the development branch has already progressed to Crank, we need to create the 2.1 branch from the masteror the last "next" branch. There is already a brach-2.0.
-- Christoph -- You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en.
