Pardon me for butting in where I haven't been invited. I realize I haven't earned the right to direct development here, but I had a few concerns. No offense is intended, and I hope no offense will be perceived.
on Thu Jun 28 2007, Christian Boos <cboos-AT-neuf.fr> wrote: > 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. Aren't point releases are usually reserved for fixing problems discovered in a major release? I guess sticking things in 0.11.1 for now is a good idea, but I suggest that once you decide what's in 0.11, everything else in 0.11.1 gets moved to 0.12. > 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. Yes, and I suggest adding an item about making http://trac.edgewall.org/wiki/TracDev/ApiChanges/0.11 more complete. Most of the information I ended up needing to port a few plugins wasn't on that page. I did my best to add what I learned, but I may have missed a few things. It isn't easy to document what you're learning when you're not sure that it's right :) It needs to be done by someone who actually understands the code. > 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. 'scuse again, but wouldn't it be worse to have a brand new API come out that you're planning to retire in the very next release? -- Dave Abrahams Boost Consulting http://www.boost-consulting.com The Astoria Seminar ==> http://www.astoriaseminar.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
