On Wed, Jan 21, 2015 at 7:17 AM, Greg Troxel <[email protected]> wrote:
> > Ryan Ollos <[email protected]> writes: > > > 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: > > The two things that I'd like to see long term (separate from what should > be in 1.2 or when there will be code) are: > > Integration of ticket dependencies into the base; this seems too > fundamental to make optional. There are two kinds of dependencies: > one is parent/child for hierarchical WBS (for task/enhancement > tickets), and the other is blocking (for those, or for defects). With > mastertickets you can one or the other, or have it be a little > confused and do both. > That is one of the features I have in mind for development in 1.3.x. The BloodhoundRelationsPlugin looks promising for backporting into Trac. http://trac.edgewall.org/ticket/31#comment:180 > Change of scheme to store numbers as numbers, rather than as strings, > and generally to thereby use database consistency checking. > > > 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. > > From the pkgsrc viewpoint, dropping 2.6 is fine, as 2.6 is getting > pretty crufty. > -- 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.
