Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@forrest.apache.org
Received-SPF: pass (athena.apache.org: domain of williamstw@gmail.com
 designates 209.85.160.176 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=x/872pZ89E6OGjM3HkROS4RodaM4QeTOoDeZCtRnXZp2pPkHo/jM27mIvS9W8ggAGW
         CnIPoDX7g4MgJwpehWmAtNltnPGebQ//WSiU4w7uAovcFtQJ7ywOqtrUH42rc8IlHz0a
         sVps7fNQT7VZoWPdtXr4AvvXA52Cd+oNOM6mI=
MIME-Version: 1.0
In-Reply-To: <20100526031825.GC2582@beaver.dehavilland>
References: <499888440912071419q1e9b5d33q9ef86978b52e3126@mail.gmail.com>
	<m2l499888441004211654y7bed889u8055479e73b51b71@mail.gmail.com>
	<4BD023C3.9040907@apache.org>
	<4BD56223.60003@pco-innovation.com>
	<u2s499888441004260514k6e870769s7960f2ff085719b6@mail.gmail.com>
	<20100427060403.GA4348@igg.local>
	<5DFC1A23-9FCA-4400-96E7-4B46F3013913@apache.org>
	<AANLkTin_Bx86woGr5lKT4SztgTdIuQ7YNtR8VTbkV9pa@mail.gmail.com>
	<30CF4827-5D22-47E0-9B71-8F536828C766@apache.org>
	<AANLkTimXaX-fNEiVrrRQOfok2ILSULbwsZ73P6Xh133e@mail.gmail.com>
	<20100526031825.GC2582@beaver.dehavilland>
Date: Wed, 26 May 2010 08:21:48 -0400
Message-ID: <AANLkTikEb7zelfghwqJLq5QQTlHAUxdAsa2WDIbRol_6@mail.gmail.com>
Subject: Re: Merging back the dispatcher
From: Tim Williams <williamstw@gmail.com>
To: dev@forrest.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Tue, May 25, 2010 at 11:18 PM, Brian M Dube <bdube@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 <thorsten@apache.org>=
 wrote:
>> >
>> > On 25/05/2010, at 03:15, Tim Williams wrote:
>> >
>> >> On Tue, Apr 27, 2010 at 7:59 AM, Thorsten Scherler <thorsten@apache.o=
rg> 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. =A0I think there's another considerati=
on
>> >>>>> that I didn't mention too. =A0I feel irresponsible releasing softw=
are
>> >>>>> that we can't support and I'm concerned that this would be the cas=
e
>> >>>>> with the dispatcher. =A0I have a difficult enough time now digging=
 up
>> >>>>> Cocoon knowledge when questions come across but with
>> >>>>> dispatcher-related ones I have no clue. =A0Maybe 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 basicall=
y 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? =A0Does anyone have the time in the near future to move i=
t
>> >> 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? =A0I'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