Am 23.02.2012 05:29, schrieb Michael Pedersen:
The only issue I have with anything is the seeming belief that we need a special branch for the 2.1 line. We really don't. We do our planned next release work on development. When we have to do a bug-fix release, we branch from the tag that had the bug, fix there, and merge as appropriate.
That would still a special branch, even when made only at relase time. I think it's better to have an branch existing all the time, and whenever we feel a bug needs to be backported, we can add it to that branch at any time, without immediately making a bugfix release.
In this case, we'll branch from 2.1.4, cherrypick the commits we need from development, and create the 2.1.5 tag from that. In the process, we'll also probably have to update jenkins a bit, but that's livable.
Btw, are Py 2.5 and Py 2.7 available on that server? -- 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.
