I want to fix the problem with the empty spaces in the param names,
and then head to xwork and see if there are any blocking bugs open,
and try to help there. I am trying to get Rene to do the xwork
release, and me and Wes will step thru the Struts release, so there is
more people involved with the process, and we don't stall in the
future because there is only one person doing releases.

I think we can merge the changes from the branch back into trunk, but
I am waiting on Rene's confirmation on that. I still think we should
get Convention out for 2.1 but I am giving up on that hope.

regards
musachy

On Tue, Dec 2, 2008 at 10:01 AM, James Holmes <[EMAIL PROTECTED]> wrote:
> Yes, see the Struts home page for the following info:
>
> =====
> The latest release of Struts 2 is Struts 2.1.2, which was promoted to "Beta"
> on 26 March 2008. For the latest production release ("General
> Availability"), see Struts 2.0.14.
> =====
>
>
>
> On Tue, Dec 2, 2008 at 9:58 AM, Wes Wannemacher <[EMAIL PROTECTED]> wrote:
>
>> Was 2.1.2 a BETA?
>>
>> -Wes
>>
>> On Tue, Dec 2, 2008 at 9:53 AM, James Holmes <[EMAIL PROTECTED]>
>> wrote:
>> > It looks like we're almost there! Musachy is killing it!
>> >
>> > From what I can tell the only real outstanding issue left for the 2.1.3
>> > release is:
>> >
>> > https://issues.apache.org/struts/browse/WW-2197
>> >
>> > That said, what is the plan to get 2.1 to GA? Are we going to close out
>> the
>> > last 2 or 3 2.1.3 bugs and make an attempt at GA?
>> >
>> > James
>> >
>>
>>
>>
>> --
>> Wesley Wannemacher
>> President, Head Engineer/Consultant
>> WanTii, Inc.
>> http://www.wantii.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>



-- 
"Hey you! Would you help me to carry the stone?" Pink Floyd

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

Reply via email to