On Monday, October 27, 2014 8:36:17 PM UTC-7, RjOllos wrote: > > On Sun, Oct 26, 2014 at 6:15 AM, Christian Boos <christian.b...@free.fr> > wrote: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On 10/26/2014 9:01 AM, Remy Blank wrote: >> > 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. >> >> >> >> 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? >> > >> > I'm not really qualifying as a dev anymore, and I tend to have a >> > radical view on such issues, but I would make the just-released >> > 0.12.6 the last release on the 0.12 branch, and only patch it for >> > security issues. >> > >> > Rationale: the dev team is small, and the time that you guys can >> > spend on Trac (thanks a lot, BTW!) should be spent on new features >> > and bug fixes, not on maintenance. >> > >> >> Here is one proposal: - 0.12.7 / 1.0.3 / 1.1.3: Jan 2015 >> >> Here's a middle ground: I basically agree with what Remy said, except >> that 0.12.6 wasn't announced as being the last release. Maybe there >> are still people blocked with Python 2.4(?) and hoping for a few last >> bugfixes(?). We could announce that 0.12.7 will be the last "bugfix" >> release for 0.12.x and if there are people who still care about this >> line of development, here's their chance to bring forward their >> patches! After 0.12.7, only have releases for important security fixes >> (and that could still go on for a while, without much additional work). >> >> Also, make clear that 0.11.x will no longer be updated, even for >> security fixes (and remove it from TracDownload). >> >> - -- Christian >> > > Having a final planned release on 0.12.x sounds like a friendly > transition. How should we go about announcing this? Is the discussion in > this thread along with some edits to the wiki enough, or should we post a > formal message to the trac-announce channel? >
>From the discussion I've seen it looks like we've arrived at the conclusion that only critical issues will be fixed for Trac 0.12.7. We'll update the translations for that release and after that only security fixes will be provided. I'm happy that we are putting the main effort towards 1.0-stable and beyond, which might result in a bit more overall momentum for the project. I will add however, that while I'm happy to not have to prepare fixes for 0.12-stable for most of the tickets that I'm working, I would have no problem with someone backporting fixes to 0.12-stable if they have a vested interested in the branch. I say this based on two things: 1. Christian's comment about 0.11-stable (1) 2. Jun seems to have a vested interested in 0.12-stable (2), going so far as to make a plugin to backport fixes (3). Jun, if you'd prefer to put that effort to backporting fixes to 0.12-stable, that would be just as well to me at least. Assuming I'm the "release manager" for the next set of releases, I'm just as happy to a prepare release for the 0.12 line as well. It will be done for 0.12.7 regardless, and it's not that much extra effort to add a 0.12.8 with 1.0.4. I'm just happy to not have to backporting many fixes myself :) (1) http://trac.edgewall.org/ticket/9602#comment:1 (2) http://trac.edgewall.org/ticket/11796#comment:7 (3) http://trac-hacks.org/wiki/TracFewFixesPlugin -- 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.
