The change I made to xwork is a very minor, internal Guice improvement
that should have no impact on its GA release. I haven't checked with
Rainer lately, but I'd imagine XWork 2.0 could go final very soon.
As for branching for 2.1, yeah, we could do that. I was thinking of
doing the ajax tag changes now, since tag changes for future versions
are generally very painful for people, and honestly, I just don't feel
comfortable with the tags now. For example, as a placeholder during the
incubation, I changed the simple theme to always import Dojo, which is
clearly not a good idea. I'd really like to clean Dojo out of core, so
we can keep the core tags as simple as possible. Simple generally
equals easier to stabilize. Still, if that isn't the consensus, I can
do the changes in the branch.
I'm very much interested in a GA release in Jan or Feb, but I do want to
make sure it isn't one we are ashamed of.
Don
Ted Husted wrote:
[From Tag Reorganization thread]
On 12/30/06, Don Brown <[EMAIL PROTECTED]> wrote:
Quick update: The dojo separation is looking easier than I thought. I
plan to finish it tomorrow, however, it requires the latest xwork so
we should probably put it after 2.0.2. It is looking pretty good for
plugins that want to create a new struts-dependent tag library and
want their tags to work in JSP, Velocity, and Freemarker.
Don
OK, I'll get ready to roll another release then.
BUT, what are these changes going to mean for XWork releases? If we
start making more changes to XWork, is the next distribution of XWork
going remained tagged a "release candidate"? Does this mean that our
next (or first) Struts GA candidate will be Struts 2.0.4, or later?
Even with one milestone a month, that pushes a Struts GA out to to
February or March 2007.
Struts 2.0.2 -> XW RC2 (December)
Struts 2.0.3 -> XW RC3 (January)
Struts 2.0.4 -> XW Final (February)
I'm concerned that it is taking us too long for us to stabalize a
Struts 2.0.x release.
I'm on the verge of suggesting that we branch Struts at 2.0.1 and
XWork at Beta 1, so that we can stabalize those bits, while we twiddle
all these new bits.
It's possible that we've already wandered past "phase 1", and we are
well on our way to "phase 2". At this point, perhaps we should be
getting ready to roll Struts 2.1.0 against a XWork 2.1 beta 1.
If we were to release a Struts 2.0.x GA candidate now, based on a
patched Struts 2.0.1, while we continue work on an imminent Struts
2.1.x, people would have a "heads-up" as to where we are going, and
everyone could make their own decisions as to forward-compatibility.
I would suggest that any argument about confusing the general public
with overlapping Struts 2 release series has already been outweighed
by having no S2 GA releases at all.
-Ted.
---------------------------------------------------------------------
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]
