On Tue, May 25, 2010 at 11:18 PM, Brian M Dube <bd...@apache.org> wrote: > On Tue, May 25, 2010 at 08:16:51AM -0400, Tim Williams wrote: >> On Tue, May 25, 2010 at 4:03 AM, Thorsten Scherler <thors...@apache.org> >> wrote: >> > >> > On 25/05/2010, at 03:15, Tim Williams wrote: >> > >> >> On Tue, Apr 27, 2010 at 7:59 AM, Thorsten Scherler <thors...@apache.org> >> >> wrote: >> >>> >> >>> On 27/04/2010, at 08:04, David Crossley wrote: >> >>> >> >>>> Tim Williams wrote: >> >>>>> >> >>>>> Well, if the dispatcher is all that changed in such a release, we >> >>>>> could do a 0.91 afterwards. I think there's another consideration >> >>>>> that I didn't mention too. I feel irresponsible releasing software >> >>>>> that we can't support and I'm concerned that this would be the case >> >>>>> with the dispatcher. I have a difficult enough time now digging up >> >>>>> Cocoon knowledge when questions come across but with >> >>>>> dispatcher-related ones I have no clue. Maybe it's an unfounded >> >>>>> concern, I dunno... >> >>>> >> >>>> I have the same concerns. >> >>>> >> >>>> Perhaps we should get 0.9 released ASAP, >> >>>> then make a concerted effort to build a Dispatcher >> >>>> community. Make another release soon after. >> >>> >> >>> >> >>> I understand what you are all saying, but the dispatcher is basically >> >>> one transformer and >> >>> the usage of locationmap for resolving the structurer and contracts. >> >>> There is not much >> >>> more to it. >> >> >> >> So, would you be against a 0.9 release with dispatcher in the >> >> whiteboard? Does anyone have the time in the near future to move it >> >> from the whiteboard anyway? >> > >> > >> > I am not sure about the community support as reason to keep it in the >> > whiteboard. There are many devs and committer >> > that uses the dispatcher so I do not see the missing community around it. >> >> Thanks Thorsten, fair enough, I'm hoping someone finds time to move it >> to /plugins soon? I've been avoiding the dispatcher related 0.9 >> issues until this decision was made so we'll also need to start >> picking through those issues and figuring which can be pushed off. >> >> --tim > > I can find the time to move it, but do we have a consensus? It's hard > to tell when it's so quiet.
As I understand it, it could happen under lazy approval anyway. I dunno, maybe a vote is in order. On the other hand, I need to find our documentation on plugin releases and how they do/do not necessarily coincide with the app itself - I think Ross has written about this somewhere... --tim
