On Apr 7, 2005 11:53 AM, Frank W. Zammetti <[EMAIL PROTECTED]> wrote:
> Ok, that's what I figured, this is an "as of 1.3" thing.
> 
> You know, this is an especially bad time for those not on the Struts team
> to be trying to contribute anything it seems... you really can't do
> anything against the currently released version because you are told no
> new development is going into them, and you really can't do too much
> against 1.3 itself because it is still in flux (and if nothing else you
> can't check out code to change so what you do might be stepped on, and the
> team is busy doing their thing so they don't have the time to integrate
> what someone outside might do).
> 
> I don't mean that as a criticism or a complaint, just stating what I see
> as the reality.

The reality is that all the development conversations really do happen
on dev@, and anyone who follows dev@ knows as much as the committers.

It is easier for committers to apply patches and refactorings. But, as
far as a significant new component goes, the reality is that we all go
through the same gauntlet. Struts Chain was in the sandbox for going
on a year before we integrated it into the head.

In any event, the taglibs themselves are not changing between 1.2.x
and 1.3.x, only how they are distributed. An extension based on the
1.2.x code would be easy enough to refactor for distribution with
1.3.x, when the time comes.

But, if whether an extension will be adopted into the main project is
a deciding factor, then, realistically, I'd suggest spending the time
on other pursuits. Even the committers don't know if a subproject
proposal would be accepted.

Looking back, Don didn't know if Flow or Scripting would be adopted as
a subproject. Craig didn't know if Shale would be adopted as a
subproject. Looking forward, Naill doesn't know if we would adopt
LazyDynaBeans. Hubert doesn't know if we would accept formdef. And I
don't know if we would accept OverDrive. The journey has to be the
reward.

-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to