On 26.10.2014 05:12, RjOllos wrote:
I'm hopeful that we can have a 2-month release cycle going forward, with the next release by Jan 1st. That set of releases will include 0.12.7.
2-month release cycle would be great. It sounds very ambitious, but you now probably know best if and how it is achievable.
I assume this means a simplified release process e.g. without string-freeze periods? (Personally I think the faster iteration time would more than compensate any drawbacks.)
I don't have any interest in the 0.12 release line, but of course I will continue to fix issues on the branch until we have agreement that it should be dropped and 1.0.x made our LTS release. What do others have in mind, particularly the other devs?
Agreed. I also have no interest in 0.12.
Here is one proposal: - 0.12.7 / 1.0.3 / 1.1.3: Jan 2015 - 0.12.8 / 1.0.4 / 1.2.0: March 2015 ... and have 0.12.8 be the last release on the 0.12 line.
Fine by me. (But I also have no problem if someone else wants to fix more bugs on 0.12 and do more releases.)
-- You received this message because you are subscribed to the Google Groups "Trac Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to trac-dev+unsubscr...@googlegroups.com. To post to this group, send email to trac-dev@googlegroups.com. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
