Ted,
I would volunteer as release manager for the 2.1.0 release.
Prior to a S2 2.1.0 release lots of issues need to be addressed on
the xwork side.
Since I am the release manager for xwork as well, I can follow up
with the S2
release as soon as xwork 2.1 is out.
-Rainer
Am 07.06.2007 um 18:06 schrieb Ted Husted:
First, someone needs to review the 72 open tickets for 2.1.0 and
decide which of those really need to go into 2.1.0, and which should
be slated for sometime in 2.1.x. At this point, I don't even know if
we have a release manager for 2.1.0. It's not something that I would
be able to do myself anytime soon.
-Ted.
On 6/7/07, Al Sutton <[EMAIL PROTECTED]> wrote:
Given your comments on datetimepicker on the users list, and the
overhead of
having two branches, I personally think it's probably time to
focus solely
on 2.1 and put 2.0 into a maintainence mode whereby only critical
bug fixes
go in.
-----Original Message-----
From: Musachy Barroso [mailto:[EMAIL PROTECTED]
Sent: 07 June 2007 14:01
To: Struts Developers List
Subject: Re: [S2] Merge from 2_0_X to trunk
Yes they should! As a matter of fact I wanted to ask, are we going
to have a
2.0.9 release? I thought we were going to jump into 2.1 after
2.0.8, given
that 2.1 is almost 2.0.8 + ajax refactoring, and the ajax part is
done (few
bugs still open).
musachy
On 6/7/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
>
> Hi all!
> I noticed that, prior to the 2_0_8 tagging, some changes have been
> made to STRUTS_2_0_X and not ported to the trunk.
> Should they be merged to the trunk, or is there a reason for not
doing it?
>
> Ciao
> Antonio
>
>
---------------------------------------------------------------------
> 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]
--
HTH, Ted <http://www.husted.com/ted/blog/>
---------------------------------------------------------------------
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]
