[S2] Merge from 2_0_X to trunk

[Antonio Petrelli <an...@gmail.com>]

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: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: [S2] Merge from 2_0_X to trunk

[Musachy Barroso <mu...@gmail.com>]

Release Manager wanted for 2.1, anyone? :)

musachy

On 6/7/07, Ted Husted <hu...@apache.org> wrote:
>
> 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 <al...@al-and-andrea.org.uk> 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:musachy@gmail.com]
> > 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 <an...@gmail.com> 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: dev-unsubscribe@struts.apache.org For
> > > additional commands, e-mail: dev-help@struts.apache.org
> > >
> > >
> >
> >
> > --
> > "Hey you! Would you help me to carry the stone?" Pink Floyd
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
>
>
> --
> HTH, Ted <http://www.husted.com/ted/blog/>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>


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

Re: [S2] Merge from 2_0_X to trunk

[Musachy Barroso <mu...@gmail.com>]

what is new on xwork 2.1?

musachy

On 6/7/07, Ted Husted <hu...@apache.org> wrote:
>
> On 6/7/07, Rainer Hermanns <he...@aixcept.de> wrote:
> > I would volunteer as release manager for the 2.1.0 release.
>
> :) Wow! We didn't scare you away! :)
>
> Of course, a RM still needs all the help he or she can get, and the
> number of tickets posted against 2.1.0 could still use another
> volunteer's kind attention.
>
>
> > 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.
>
> Would the plan then be to keep Struts 2.0.x aligned with XWork 2.0.x,
> and Struts 2.1.x with the new XWork 2.1.x?
>
> -Ted.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>


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

Re: [S2] Merge from 2_0_X to trunk

[Ted Husted <hu...@apache.org>]

On 6/7/07, Rainer Hermanns <he...@aixcept.de> wrote:
> I would volunteer as release manager for the 2.1.0 release.

:) Wow! We didn't scare you away! :)

Of course, a RM still needs all the help he or she can get, and the
number of tickets posted against 2.1.0 could still use another
volunteer's kind attention.


> 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.

Would the plan then be to keep Struts 2.0.x aligned with XWork 2.0.x,
and Struts 2.1.x with the new XWork 2.1.x?

-Ted.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: [S2] Merge from 2_0_X to trunk

[Rainer Hermanns <he...@aixcept.de>]

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 <al...@al-and-andrea.org.uk> 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:musachy@gmail.com]
>> 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 <an...@gmail.com> 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: dev-unsubscribe@struts.apache.org For
>> > additional commands, e-mail: dev-help@struts.apache.org
>> >
>> >
>>
>>
>> --
>> "Hey you! Would you help me to carry the stone?" Pink Floyd
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
>> For additional commands, e-mail: dev-help@struts.apache.org
>>
>>
>
>
> -- 
> HTH, Ted <http://www.husted.com/ted/blog/>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: [S2] Merge from 2_0_X to trunk

[Ted Husted <hu...@apache.org>]

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 <al...@al-and-andrea.org.uk> 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:musachy@gmail.com]
> 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 <an...@gmail.com> 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: dev-unsubscribe@struts.apache.org For
> > additional commands, e-mail: dev-help@struts.apache.org
> >
> >
>
>
> --
> "Hey you! Would you help me to carry the stone?" Pink Floyd
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>


-- 
HTH, Ted <http://www.husted.com/ted/blog/>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

RE: [S2] Merge from 2_0_X to trunk

[Al Sutton <al...@al-and-andrea.org.uk>]

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:musachy@gmail.com] 
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 <an...@gmail.com> 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: dev-unsubscribe@struts.apache.org For 
> additional commands, e-mail: dev-help@struts.apache.org
>
>


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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: [S2] Merge from 2_0_X to trunk

[Ted Husted <hu...@apache.org>]

The key question is whether someone is ready to roll a 2.1.0 release.
Once that happens, it makes sense to put the prior minor release
series into "maintenance mode". But, until that happens, it makes
equal sense to keep pumping out 2.0.x releases with any likely
changes. We don't want to fall behind on the 2.0.x branch if the 2.1.0
branch is not ready-to-go.

-Ted.

On 6/7/07, Musachy Barroso <mu...@gmail.com> wrote:
> 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 <an...@gmail.com> 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: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
> >
>
>
> --
> "Hey you! Would you help me to carry the stone?" Pink Floyd
>


-- 
HTH, Ted <http://www.husted.com/ted/blog/>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org

Re: [S2] Merge from 2_0_X to trunk

[Musachy Barroso <mu...@gmail.com>]

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 <an...@gmail.com> 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: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>


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

Re: [S2] Merge from 2_0_X to trunk

[Rainer Hermanns <he...@aixcept.de>]

Antonio,

my latest changes will be ported over to trunk either today or tomorrow.
These changes  were only important for the release assembly, but have  
no impact on functionality.

Rainer

Am 07.06.2007 um 12:55 schrieb Antonio Petrelli:

> 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: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org