Before a GA release of 2.1 I'd ideally like to see dojo upgraded to the
latest, greatest stable version, because I can see this may cause some
headaches which would be best done at the start of the 2.1 GA releases as
opposed to half way through the 2.1 lifecycle. I'd also like to see a change
to actrionError and actionMessage handling which removes the need for the
store interceptor for redirects, but I know that's something that's in the
very early stages of thought.
I think there is value in releasing a new stable 2.1 snapshot to give
developers on s2 projects something to play with so they can see where the
2.1 branch is going, but I don't think that the next release will go GA
given the current state of the svn trunk head.
Al.
P.S. Personally I'm not a fan of x.5 versions, they kind of indicate that
it's a almost a big jump, but not quite, but possibly. I think 2.1 reflects
the fact that the API is largely unchanged with only some small sections
that need to be addressed during a migration (such as dojo being split out).
----- Original Message -----
From: "Don Brown" <[EMAIL PROTECTED]>
To: "Struts Developers List" <dev@struts.apache.org>
Sent: Wednesday, February 20, 2008 10:54 PM
Subject: Re: [s2] Let's get out Struts 2.1.1
Here's the thing - I'm going to create the 2.1.1 test build on Sunday,
hopefully followed by test builds every couple weeks or so. Whatever
you can get into the code by those dates will be included in the
subsequent release. Honestly, I don't expect 2.1.1 to be GA, but am
aiming for a Beta vote. I would like to see a GA release sometime
around the 2.1.4 timeframe, though.
Don
On 2/21/08, Brian Pontarelli <[EMAIL PROTECTED]> wrote:
> If convention-plugin is not bundled with the next release, people will
stick
> to the codebehind plugin. Last time I checked there was no smarturls
for
> 2.1.x as well - so there is really not much choice.
> (compiling from the sandbox is no option for most users)
>
You are probably correct. However, unless everyone agrees to promote
convention plugin out of the sandbox and solidify it in the next few
days or so, it will have to be a separate release outside of the bundle.
>> Back to the convention plugin...
>>
>> If folks would like to discuss the API and solidify it over the next
few
>> days, I'd be up for that. I'll start a new thread for that and we can
>> hopefully get things ready for a 2.1.1 final release of the plugin
>> shortly after the release of core.
>>
>
> Is it possible to release a 2.1.1 plugin after the core? In this case
I do not
> feel like it is that important to make it part of the s2.1.1 release
:)
> Until now I thought that the next possible release for the convention
plugin
> would be 2.1.2 (or whatever build makes it).
>
Not really if you want it in the bundle. Otherwise, it would be an
external download until 2.1.2 or some version like that. I'm up for
anything.... Thoughts?
-bp
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
