Following the right road
Manuzhai
> could you pls clearly state what needs to be done iyo until release?
> backport genshi and release 0.10.6?
Rupert makes the same point I was thinking about last night (and I
think it merits its own thread). Now that there seems to be a
consensus that the road was wrong, where are we going with 0.11 now?
What needs to make it into 0.11, what API's need to be changed or
refined or scrapped, without resorting to feature creep?
Cheers,
Manuzhai (just released my first plugin, feeling pretty good about it, too)
Christopher Lenz
> On 9/24/07, rupert....@gmail.com <rupert....@gmail.com> wrote:
>> could you pls clearly state what needs to be done iyo until release?
>> backport genshi and release 0.10.6?
There's definitely not going to be a backport. First, dot releases
are reserved for bug and security fixes, second that'd simply be too
much work, and only distract from getting 0.11 done.
> Rupert makes the same point I was thinking about last night (and I
> think it merits its own thread). Now that there seems to be a
> consensus that the road was wrong, where are we going with 0.11 now?
> What needs to make it into 0.11, what API's need to be changed or
> refined or scrapped, without resorting to feature creep?
The most important thing we need to fix IMHO is the trac.context API,
and the ITimelineEventProvider/TimelineEvent API. The one feature
that should really be moved out into a plugin is "Clone Ticket".
It should be obvious that we shouldn't be trying to squeeze any more
new features in for 0.11, at least from where I'm standing :).
Cheers,
Chris
--
Christopher Lenz
cmlenz at gmx.de
http://www.cmlenz.net/
Manuzhai
> The most important thing we need to fix IMHO is the trac.context API,
> and the ITimelineEventProvider/TimelineEvent API. The one feature
> that should really be moved out into a plugin is "Clone Ticket".
Okay, so where is the whole context going to go? What should it become?
And does the ITimelineEventProvider just go back yielding tuples?
Cheers,
Manuzhai
rupert....@gmail.com
> Am 24.09.2007 um 12:44 schrieb Manuzhai:
> > Rupert makes the same point I was thinking about last night (and I
> > think it merits its own thread). Now that there seems to be a
> > consensus that the road was wrong, where are we going with 0.11 now?
> > What needs to make it into 0.11, what API's need to be changed or
> > refined or scrapped, without resorting to feature creep?
>
> The most important thing we need to fix IMHO is the trac.context API,
> and the ITimelineEventProvider/TimelineEvent API. The one feature
> that should really be moved out into a plugin is "Clone Ticket".
which direction should it be fixed, and what would happen if it is
fixed in 0.12 not now?
rupert.
Christian Boos
On Oct 5, 12:16 pm, "rupert.thur...@gmail.com"
The context refactoring is progressing well, I have a working
prototype. What's still to be done is to push those changes in a
branch and justify the design the way it is. I've got time for neither
so far, but it's coming "soon".
The timeline API changes are of much smaller scope and will follow.
Then, for #4686 (Ticket cloning), it's true that it can be done as a
plugin now, but I think that'll need the Genshi transformation API
though, so either a dependency on Genshi trunk or wait for 0.5. That
feature will also make a nice sample plugin for the template
transformation API (trac.web.api.ITemplateStreamFilter).
-- Christian
Christopher Lenz
> Then, for #4686 (Ticket cloning), it's true that it can be done as a
> plugin now, but I think that'll need the Genshi transformation API
> though, so either a dependency on Genshi trunk or wait for 0.5. That
> feature will also make a nice sample plugin for the template
> transformation API (trac.web.api.ITemplateStreamFilter).
I'm pretty sure Genshi 0.5 will be out before Trac 0.11, so don't
worry about that ;)