Christian Boos wrote: > Ilias Lazaridis wrote: > > Ilias Lazaridis wrote: > >> I've notices that the milestone 0.11 contains many tasks: > >> > >> http://trac.edgewall.org/milestone/0.11 > >> > >> Wouldn't it be preferable to split this work into a few more > >> milestones? > >> > >> This could be of benefit (in order to avoid similar delays as with the > >> actual 0.10 version). > >> > >> 0.11 - Focusing on Genshi Migration > > ... > > > > within this thread... > > > > CONTRIBUTION - Would like to do some work on the Genshi Migration > > http://groups.google.com/group/trac-dev/browse_frm/thread/a0932139d50ad20a > > > > ... the teem seems to agree to a 'Genshi Centric' 0.11 milestone > > > > the milestone entries have changed, too: > > > > http://trac.edgewall.org/milestone/0.11 > > > > The roadmap should show more concise information, thus interested > > contributors get immediately an overview. > > > > * the section "Likely to be post-poned even more:", should be moved to > > 0.12 (including related tickets). > > Eh, for now it's quite adequate, as actually we (at least I) don't know > if they will be part of 0.12 or not, in the end. If development speed > remains, the first items in the list would be completed quite soon, and > there will still be time to do more, like the WorkFlow merge, especially > given the fact that this can be started in parallel anytime now (Alec?)...
You've stated this points: " * Ditch ClearSilver in favor of Genshi for templating * Timezone support and internal use of `datetime` * Use setuptools for setup * Integration of WebAdmin into core " Development of Trac 0.11dev has started http://groups.google.com/group/trac-dev/browse_thread/thread/27d028d385620a0a Those points should be stabelized in release(!!!) quality, _before_ including major changes to the core like those introduced by workflow. Seeing development going on nice should not make you forget the 0.10 delays. > > * the entries within the milestone should start with (wiki)pointers to > > working-plans which contain actual 'help-needed' sections (thus > > contributors can immediately get an overview of how to assist for a > > functionality of their interest) > > Well, sure, this can always be improved. But feel free to discuss this > here first. I think I've made a rational suggestion, which the team can choose to apply or not. (I've no access rights to modify the Milestones). > > * the milestone 0.11 should get a date (e.g. 2006-12-29) > > > > It is of course still possible to move solved 0.12 tickets back(!) to > > the milestone 0.11 -this would btw. have an motivating effect (not > > like the negative feeling of having to post-pone something) > > Moving a bunch of ticket back and forth is still inconvenient at this > point (see #525), so we avoid doing it without a good reason. ok, I understand. This seems to be a major weakness of trac, which should not hinder the team to provide concise mileston-information. Possibly applying a keyword to the relevant tickets and moving them manually with an sql-query could help. - Like always: those are thoughts and suggestions to engourage discussion and to move trac forward. . -- http://lazaridis.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 -~----------~----~----~----~------~----~------~--~---
