Hello manu, all, Emmanuel Blot wrote: > I'm afraid about the number of tickets scheduled for 0.11, not > mentioning the ever-growing number of tickets that are marked as > "tentative" for 0.11. >
Ok, as all the other replies suggest, it seems like it's time to think about getting the release done, so I've moved the 0.11 tickets to 0.11.1, as you suggested. Now the problem as usual is deciding what really needs to go in 0.11 vs. 0.11.1, and which tickets to set back to 0.11. I've already put a "short list" up on http://trac.edgewall.org/wiki/TracDev/ToDo, which I've updated today. As you can see there, one of the main concern is about documentation. Among the few tickets I've already selected as important: #5572 (work in progress), #2048 (work started but not finished), #5025. If one moves back a ticket to 0.11, please either volunteer to fix it or make a strong case why it should be fixed for 0.11 as opposed to 0.11.1 (or 0.10.5 ;-) ). Of course, new tickets for immediate problems found while testing the current trunk can still be scheduled for 0.11. For the Trac API itself, there are a few big changes I'm working on that I think would be better to finish before 0.11. Of course, if I don't manage to finish them in the (2 or 3) coming weeks, they'll have to wait for 0.11.1 or later. Those changes are: 1) do the ResourceDescriptor / RenderingContext "split" of the Context. 2) fix the refactored search API (in SearchRefactoring) 3) fix the timeline API along the same lines as 2. 2) was discussed on #IRC and the good suggestions I got there apply to the Timeline module as well. If I implement them, this will make the brand new 0.11 Timeline API obsolete (stillborn?), so if possible, it would be better to complete 3) before the 0.11 release. 2) can eventually wait for 0.11.1. 1) should be doable in a way that stays compatible with the Context class introduced during the 0.11dev period, so it could also eventually wait for 0.11.1. The stuff currently in FieldRefactoring can be merged right away, as for now it mainly consists of code cleanups plus a few useful enhancements (#449 and #5126). The main change planned there (introduction of a Property class) will be postponed. Lastly, before making the release itself, t.e.o. itself should be upgraded to 0.11dev, and used for a few weeks as well. Before doing that, #5025 should be fixed (support for semi-automatic bug report). Also, what about the TicketDelete plugin, has that been ported already? -- 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 -~----------~----~----~----~------~----~------~--~---
