It seems like a good time to discuss what we plan to deliver for Trac 1.2, and when we will deliver it. So far I see one big feature, and some components that have been significantly improved:
- Enhanced notification system - Time custom fields - Numerous minor enhancements to the TracWorkflow We've dropped support for Python 2.5 and removed a lot of deprecated code from the API, which will make Trac easier to develop going forward. There have been numerous minor enhancements to functionality, lots of tidying of the user interface and I like the improvements that Christian has been working on for the ticket changelog view. It's always nice to have a new look for pages when we push out a new release. In addition to the tickets currently assigned to 1.0.4 and 1.1.4, there are a few key features that I'd like to implement for 1.2: - #11469: Custom field admin panel - #1233: Components and Versions become first-class objects in the TicketSystem with their own Roadmap-like pages, TracLinks, macros, permissions, ... - #3098: Repository README rendering 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 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". With a bimonthly release schedule, the next two releases will be: March 1: 1.0.4 and 1.1.4 May 1: 1.0.5 and 1.1.5 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. Somewhere in there we should release Trac 0.12.7 as well, after pulling the latest translations from Transifex for several languages. 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? As we get close to releasing 1.2 I'll raise another thread to talk about what features we have in mind for development in the 1.3.x line. 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 I'm looking forward to hearing comments, and excited to push out some more releases! - Ryan -- 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.
