On Thu, Jan 22, 2015 at 11:48 AM, Peter Suter <petsu...@gmail.com> wrote:
> On 21.01.2015 08:00, Ryan Ollos wrote: > >> Some other features that have been worked and look promising for >> inclusion in the release are: >> - PyGit2 plugin >> - #8172: Plugin db upgrade infrastructure >> - #10672: Automatically minify Javascript and CSS >> - #11676: Reusable commenting module >> > > I neglected this a bit, focusing more on notifications. It might be good > to include new interfaces and DB tables in at least one development release > (i.e. 1.1.x or 1.3.x etc.) before freezing them for long-term compatibility > in a stable release (like 1.2). > > What do others have in mind to include in the release? The question >> isn't only for current committers, but I'm hoping to hear from people >> that would be willing to step up and implement the changes as opposed to >> "please include feature X". >> > > The other notification improvements might keep me be busy for a bit. > > I'd like to see 1.1.5 be released as 1.2, but if we aren't ready by May >> 1st, then release 1.2 on July 1st along with 1.0.6. After that I'm >> hoping we can release the minor versions on yearly intervals, which >> would be every 6th maintenance release. >> > > Sounds great. > > Looking forward to 1.2, is it too early to think about dropping support >> for Python 2.6 and support Python 2.7 and 3.3+ from a single codebase? >> > > Has anyone tried Trac on Python 3? > On #10083 I see SVN and HG will be "unlikely". I guess that's less > important now that Git is so popular. > http://trac.edgewall.org/ticket/10083 > > For HG a command-server backend would be an interesting option. > http://trac.edgewall.org/ticket/10411 > > Trac 1.0 still supports Python 2.5. Maybe Trac 1.2 should still support > Python 2.6? > Yeah I think that Trac 1.2 will support Python 2.6. However, as soon as 1.2 is released we start development on the 1.3.x line and we'll need to decide what to support in 1.3.x, which determines what will be supported in 1.4. Even if we don't officially support Python 3.3+ for Trac 1.4, dropping support for 2.6 should allow us to start making more modifications that will lead to a smoother transition to supporting 3.3+. I haven't looked closely at the specifics though. > Finally, we still need a codename for the release, so that is something >> to think about as well. >> http://trac.edgewall.org/wiki/TracDev/ReleaseNotes/1.1#CodeName >> > > Added my suggestion. :) > Looks like we have a few choices now. I think we should give the "old guard" (Jonas, Christian, Remy) the first shot at picking the name. If they don't want to make the choice, we could hold a vote in a trac-dev thread. -- 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.
