On 10/6/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 10/6/06, Ted Husted <[EMAIL PROTECTED]> wrote:
> The reason I ask is that our 2.0.1 release will be tied to whatever
> version moniker that XWork uses. If tomorrow's XWork release is tagged
> as "beta", and that cannot change for that set of bits, then the 2.0.1
> release will also be forever beta.
Struts 2 also has a dependency on a snapshot of Tiles 2, so by that
logic you're stuck at Alpha for Struts 2.0.1.
This policy of grading a release at the lowest common denominator
doesn't seem to be working out all that well. Different parts of the
distribution have different levels of 'quality' so to speak. If you
have an experimental plugin, that's no reason to downgrade the core.
The core and extras are in separate JARs, and so, if we wanted, they
could have different grades. We could then put experimental members
into extras, and later, when the code is stable, if enough people are
using an extra so that it becomes a defacto essential, we could
graduate the code from extras to core.
Personally, I'm not going to vote GA on a set of bits with a
dependency on a beta. But, that's just me. It's a majority vote.
Speaking of that Tiles 2 dependency, we need to deploy a snapshot with
a fixed version number (such as 20061006-SNAPSHOT) so that future
snapshots of Tiles 2 don't break Struts 2.0.1 for Maven users.
I'm not working with Tiles myself right now, so I'll leave that to
them that do.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
