I agree with quick-release cycle plan, but 2-month cycle is very short, so it's tough for trac-team I guess. I think it's important to set a milestone to be reliable and include features/bug fixes many users hope.
For me, I'm looking forward 1.2.0 including multi project feature. thanks, Tetsuya On Sun, Oct 26, 2014 at 1:12 PM, RjOllos <[email protected]> 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. > > 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? > > 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. > > There are many tickets associated with 0.12-stable. I started going through > these a month or two back. It would be good to triage these and re-target > the tickets that are more appropriate for 1.0-stable, of which I suspect > there are many. > http://trac.edgewall.org/milestone/next-minor-0.12.x > > -- > 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 [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/trac-dev. > For more options, visit https://groups.google.com/d/optout. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/trac-dev. For more options, visit https://groups.google.com/d/optout.
