Hello, As more and more people start to ask when 0.11 will be released, I wanted to discuss the topic here.
I think that we can now start to schedule /new/ enhancements tickets to 0.12, directly. The same for things that look like being either long standing issues or non important bugs. Bug reports against defects directly related to or introduced by 0.11 should of course still be scheduled for the 0.11 milestone. We should also start to move some of the existing opened 0.11 tickets to either 0.12 or a new 0.10.1, for things we don't absolutely wish to have for a 0.11. I'll do that triage for my own 74 tickets, which leaves 90 tickets for the other owners. If you don't feel like doing this for your own tickets, please at least say so, so that others (not necessarily me) could do this triaging for you. I think this month will still see some heavy changes, like the ticket preview changes and hopefully other outcomes from Pycon (workflow, security, ...?), as well as my wiki refactoring, if I manage to find enough time to get it in shape, so that we could think about a 0.11beta1 release early next month. I have the feeling that we're just /starting/ to see 0.10.3 widely deployed, with 0.9 becoming now an exception rather than the rule, so I think there's also no big reason to rush for a 0.11 release before we feel we're ready with it, so that we can safely finish what has already been started. -- Christian --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
