On Wed, 09 Mar 2005 17:05:54 -0500, Frank W. Zammetti
<[EMAIL PROTECTED]> wrote:
> Joe Germuska wrote:
> > Most importantly, and I'm sorry that I just realized this after Frank
> > has gone to such great lengths: if we were to patch Struts 1.2 to do
> > this, we would be obligated to support this same functionality in 1.3 as
> > well, in order to continue to provide compatibility.
> 
> I don't think that's the case Joe.  Especially since we're being told
> that once 1.3 comes out than the 1.2 branch essentially "dies" as far as
> new features go... But if people in the community are willing to bring
> new features to that branch, I don't see how that obligates you to
> forward-port things.  Sure, it'd be nice it you did for compatibility,
> but as long as it is clearly documented that some features might exist
> in one branch vs. another that aren't cross-compatible, I don't see why
> it should be a problem.

We take compatibility very seriously, and Joe is absolutely right.
Adding functionality to 1.2.x and not adding it to 1.3.x means that
when people want to upgrade, they may be completely hosed if they were
relying on functionality only available in the earlier version. That
would effectively mean that the "versions" were forks rather than real
versions. There's no way I want to see us going in that kind of
direction.

Note that the 1.2 -> 1.3 scenario isn't any different than 1.0 -> 1.1
or 1.1 -> 1.2. Each time we move to a new point release, the previous
one moves into maintenance mode. That's no different from the vast
majority of other software components in the world today.

--
Martin Cooper


> Some may not want or be able to upgrade to 1.3, and by saying no new
> features will be added to 1.2 people in that boat are being left out in
> the cold as far as new features go (unless they want to do it themselves
> of course).  I'm not claiming this is unusual, but is it really the best
> answer?
> 
> --
> Frank W. Zammetti
> Founder and Chief Software Architect
> Omnytex Technologies
> http://www.omnytex.com
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>

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

Reply via email to