You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by Ted Husted <hu...@apache.org> on 2004/07/01 03:35:00 UTC
RE: Struts 1.2.1 release?
So, if we can solve 29285, it looks like 1.2.1 would be ready to roll.
On Fri, 25 Jun 2004 22:27:39 -0400, Ted Husted wrote:
> OK, we're down to 4 problem tickets. Two are against the validator,
> but patches are not available. Two are against Struts-Faces, and
> could actually be skipped since Struts-Faces would not be in the
> 1.2.1 release.
>
>
> The release notes are updated, so if we can swat #29285 and #29796,
> we could try rolling Struts 1.2.1.
>
>
> I'll be away through Thursday. I may have email, but don't know if
> the connection would be good enough to try and roll a release.
>
>
> If anyone want to jump in, please feel free.
>
>
> -Ted.
>
>
> --------------------------------------------------------------------
> - 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: Struts 1.2.1 release?
Posted by James Holmes <ja...@jamesholmes.com>.
Sounds good! Thanks for taking care of it.
-James
-----Original Message-----
From: Ted Husted [mailto:husted@apache.org]
Sent: Friday, July 02, 2004 6:15 PM
To: Struts Developers List
Subject: Re: Struts 1.2.1 release?
OK, I'd like to make one last pass on the documentation to be sure
everything seems consistent with the 1.2.1 release, and then roll it Sunday
night. We can then vote on whether to promote it past Alpha stage, and, if
so, mirror the Beta for community testing.
-Ted.
On Fri, 02 Jul 2004 16:32:51 +0100, Niall Pemberton wrote:
> I changed the bugzilla priority to enhacement for this bug
> yesterday - I don't know if the problem is my end but I didn't see
> the usual bugzilla email on this list after I made the change, so
> I'm posting this here.
>
> http://issues.apache.org/bugzilla/show_bug.cgi?id=29285
>
>
> Niall
>
>
> ----- Original Message -----
> From: "Ted Husted" <hu...@apache.org>
> To: "Struts Developers List" <de...@struts.apache.org>
> Sent: Thursday, July 01, 2004 11:44 PM
> Subject: Re: Struts 1.2.1 release?
>
>
> On Thu, 01 Jul 2004 22:19:39 +0100, Niall Pemberton wrote:
>
>> I agree.
>>
>>
>> Also it seems to me that validwhen was never built to work with
>> mapped properties and therefore this should be an enhancement
>> request rather than bug. I guess the assumption is that as
>> requiredif has been labelled as "deprecated" in favour of
>> validwhen, then validwhen should provide at least the same
>> functionality as requiredif - including handling mapped
>> properties. Even so, if it wasn't designed/built to handle mapped
>> properties then its not a bug.
>>
>> Niall
>>
>
> If you want to change the Severity of this report, Niall, that's
> fine with me.
>
> Though, we might want to document this issue, especially since
> validwhen is a new feature.
>
> -Ted.
>
>
>> ----- Original Message -----
>> From: "Don Brown" <mr...@twdata.org>
>> To: "Struts Developers List" <de...@struts.apache.org>
>> Sent: Thursday, July 01, 2004 9:13 PM
>> Subject: RE: Struts 1.2.1 release?
>>
>>
>>> I vote we just roll it anyways. If we have switched to tomcat-
>>> style releases, we can just not label it as stable. I asked
>>> one of the tomcat guys last nite at the JakartaOne party if
>>> they close out all their bugs and he laughed :)
>>>
>>> Don
>>>
>>>
>>>> So, if we can solve 29285, it looks like 1.2.1 would be ready
>>>> to roll.
>>>>
>>>>
>>>> On Fri, 25 Jun 2004 22:27:39 -0400, Ted Husted wrote:
>>>>
>>>>
>>>>> OK, we're down to 4 problem tickets. Two are against the
>>>>> validator, but patches are not available. Two are against
>>>>> Struts-Faces, and could actually be skipped since Struts-
>>>>> Faces would not be in the 1.2.1 release.
>>>>>
>>>>>
>>>>> The release notes are updated, so if we can swat #29285 and
>>>>> #29796, we could try rolling Struts 1.2.1.
>>>>>
>>>>>
>>>>> I'll be away through Thursday. I may have email, but don't
>>>>> know if the connection would be good enough to try and roll
>>>>> a release.
>>>>>
>>>>>
>>>>> If anyone want to jump in, please feel free.
>>>>>
>>>>>
>>>>> -Ted.
>
>
> --------------------------------------------------------------------
> - 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
---------------------------------------------------------------------
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: Struts 1.2.1 release?
Posted by Ted Husted <hu...@apache.org>.
OK, I'd like to make one last pass on the documentation to be sure everything seems consistent with the 1.2.1 release, and then roll it Sunday night. We can then vote on whether to promote it past Alpha stage, and, if so, mirror the Beta for community testing.
-Ted.
On Fri, 02 Jul 2004 16:32:51 +0100, Niall Pemberton wrote:
> I changed the bugzilla priority to enhacement for this bug
> yesterday - I don't know if the problem is my end but I didn't see
> the usual bugzilla email on this list after I made the change, so
> I'm posting this here.
>
> http://issues.apache.org/bugzilla/show_bug.cgi?id=29285
>
>
> Niall
>
>
> ----- Original Message -----
> From: "Ted Husted" <hu...@apache.org>
> To: "Struts Developers List" <de...@struts.apache.org>
> Sent: Thursday, July 01, 2004 11:44 PM
> Subject: Re: Struts 1.2.1 release?
>
>
> On Thu, 01 Jul 2004 22:19:39 +0100, Niall Pemberton wrote:
>
>> I agree.
>>
>>
>> Also it seems to me that validwhen was never built to work with
>> mapped properties and therefore this should be an enhancement
>> request rather than bug. I guess the assumption is that as
>> requiredif has been labelled as "deprecated" in favour of
>> validwhen, then validwhen should provide at least the same
>> functionality as requiredif - including handling mapped
>> properties. Even so, if it wasn't designed/built to handle mapped
>> properties then its not a bug.
>>
>> Niall
>>
>
> If you want to change the Severity of this report, Niall, that's
> fine with me.
>
> Though, we might want to document this issue, especially since
> validwhen is a new feature.
>
> -Ted.
>
>
>> ----- Original Message -----
>> From: "Don Brown" <mr...@twdata.org>
>> To: "Struts Developers List" <de...@struts.apache.org>
>> Sent: Thursday, July 01, 2004 9:13 PM
>> Subject: RE: Struts 1.2.1 release?
>>
>>
>>> I vote we just roll it anyways. If we have switched to tomcat-
>>> style releases, we can just not label it as stable. I asked
>>> one of the tomcat guys last nite at the JakartaOne party if
>>> they close out all their bugs and he laughed :)
>>>
>>> Don
>>>
>>>
>>>> So, if we can solve 29285, it looks like 1.2.1 would be ready
>>>> to roll.
>>>>
>>>>
>>>> On Fri, 25 Jun 2004 22:27:39 -0400, Ted Husted wrote:
>>>>
>>>>
>>>>> OK, we're down to 4 problem tickets. Two are against the
>>>>> validator, but patches are not available. Two are against
>>>>> Struts-Faces, and could actually be skipped since Struts-
>>>>> Faces would not be in the 1.2.1 release.
>>>>>
>>>>>
>>>>> The release notes are updated, so if we can swat #29285 and
>>>>> #29796, we could try rolling Struts 1.2.1.
>>>>>
>>>>>
>>>>> I'll be away through Thursday. I may have email, but don't
>>>>> know if the connection would be good enough to try and roll
>>>>> a release.
>>>>>
>>>>>
>>>>> If anyone want to jump in, please feel free.
>>>>>
>>>>>
>>>>> -Ted.
>
>
> --------------------------------------------------------------------
> - 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts 1.2.1 release?
Posted by Niall Pemberton <ni...@blueyonder.co.uk>.
I changed the bugzilla priority to enhacement for this bug yesterday - I
don't know if the problem is my end but I didn't see the usual bugzilla
email on this list after I made the change, so I'm posting this here.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29285
Niall
----- Original Message -----
From: "Ted Husted" <hu...@apache.org>
To: "Struts Developers List" <de...@struts.apache.org>
Sent: Thursday, July 01, 2004 11:44 PM
Subject: Re: Struts 1.2.1 release?
On Thu, 01 Jul 2004 22:19:39 +0100, Niall Pemberton wrote:
> I agree.
>
>
> Also it seems to me that validwhen was never built to work with
> mapped properties and therefore this should be an enhancement
> request rather than bug. I guess the assumption is that as
> requiredif has been labelled as "deprecated" in favour of
> validwhen, then validwhen should provide at least the same
> functionality as requiredif - including handling mapped properties.
> Even so, if it wasn't designed/built to handle mapped properties
> then its not a bug.
>
> Niall
If you want to change the Severity of this report, Niall, that's fine with
me.
Though, we might want to document this issue, especially since validwhen is
a new feature.
-Ted.
> ----- Original Message -----
> From: "Don Brown" <mr...@twdata.org>
> To: "Struts Developers List" <de...@struts.apache.org>
> Sent: Thursday, July 01, 2004 9:13 PM
> Subject: RE: Struts 1.2.1 release?
>
>
>> I vote we just roll it anyways. If we have switched to tomcat-
>> style releases, we can just not label it as stable. I asked one
>> of the tomcat guys last nite at the JakartaOne party if they
>> close out all their bugs and he laughed :)
>>
>> Don
>>
>>
>>> So, if we can solve 29285, it looks like 1.2.1 would be ready
>>> to roll.
>>>
>>>
>>> On Fri, 25 Jun 2004 22:27:39 -0400, Ted Husted wrote:
>>>
>>>> OK, we're down to 4 problem tickets. Two are against the
>>>> validator, but patches are not available. Two are against
>>>> Struts-Faces, and could actually be skipped since Struts-
>>>> Faces would not be in the 1.2.1 release.
>>>>
>>>>
>>>> The release notes are updated, so if we can swat #29285 and
>>>> #29796, we could try rolling Struts 1.2.1.
>>>>
>>>>
>>>> I'll be away through Thursday. I may have email, but don't
>>>> know if the connection would be good enough to try and roll a
>>>> release.
>>>>
>>>>
>>>> If anyone want to jump in, please feel free.
>>>>
>>>>
>>>> -Ted.
---------------------------------------------------------------------
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: Struts 1.2.1 release?
Posted by Ted Husted <hu...@apache.org>.
On Thu, 01 Jul 2004 22:19:39 +0100, Niall Pemberton wrote:
> I agree.
>
>
> Also it seems to me that validwhen was never built to work with
> mapped properties and therefore this should be an enhancement
> request rather than bug. I guess the assumption is that as
> requiredif has been labelled as "deprecated" in favour of
> validwhen, then validwhen should provide at least the same
> functionality as requiredif - including handling mapped properties.
> Even so, if it wasn't designed/built to handle mapped properties
> then its not a bug.
>
> Niall
If you want to change the Severity of this report, Niall, that's fine with me.
Though, we might want to document this issue, especially since validwhen is a new feature.
-Ted.
> ----- Original Message -----
> From: "Don Brown" <mr...@twdata.org>
> To: "Struts Developers List" <de...@struts.apache.org>
> Sent: Thursday, July 01, 2004 9:13 PM
> Subject: RE: Struts 1.2.1 release?
>
>
>> I vote we just roll it anyways. If we have switched to tomcat-
>> style releases, we can just not label it as stable. I asked one
>> of the tomcat guys last nite at the JakartaOne party if they
>> close out all their bugs and he laughed :)
>>
>> Don
>>
>>
>>> So, if we can solve 29285, it looks like 1.2.1 would be ready
>>> to roll.
>>>
>>>
>>> On Fri, 25 Jun 2004 22:27:39 -0400, Ted Husted wrote:
>>>
>>>> OK, we're down to 4 problem tickets. Two are against the
>>>> validator, but patches are not available. Two are against
>>>> Struts-Faces, and could actually be skipped since Struts-
>>>> Faces would not be in the 1.2.1 release.
>>>>
>>>>
>>>> The release notes are updated, so if we can swat #29285 and
>>>> #29796, we could try rolling Struts 1.2.1.
>>>>
>>>>
>>>> I'll be away through Thursday. I may have email, but don't
>>>> know if the connection would be good enough to try and roll a
>>>> release.
>>>>
>>>>
>>>> If anyone want to jump in, please feel free.
>>>>
>>>>
>>>> -Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts 1.2.1 release?
Posted by Niall Pemberton <ni...@blueyonder.co.uk>.
I agree.
Also it seems to me that validwhen was never built to work with mapped
properties and therefore this should be an enhancement request rather than
bug. I guess the assumption is that as requiredif has been labelled as
"deprecated" in favour of validwhen, then validwhen should provide at least
the same functionality as requiredif - including handling mapped properties.
Even so, if it wasn't designed/built to handle mapped properties then its
not a bug.
Niall
----- Original Message -----
From: "Don Brown" <mr...@twdata.org>
To: "Struts Developers List" <de...@struts.apache.org>
Sent: Thursday, July 01, 2004 9:13 PM
Subject: RE: Struts 1.2.1 release?
> I vote we just roll it anyways. If we have switched to tomcat-style
> releases, we can just not label it as stable. I asked one of the tomcat
> guys last nite at the JakartaOne party if they close out all their bugs
> and he laughed :)
>
> Don
>
> > So, if we can solve 29285, it looks like 1.2.1 would be ready to roll.
> >
> > On Fri, 25 Jun 2004 22:27:39 -0400, Ted Husted wrote:
> >> OK, we're down to 4 problem tickets. Two are against the validator,
> >> but patches are not available. Two are against Struts-Faces, and
> >> could actually be skipped since Struts-Faces would not be in the
> >> 1.2.1 release.
> >>
> >>
> >> The release notes are updated, so if we can swat #29285 and #29796,
> >> we could try rolling Struts 1.2.1.
> >>
> >>
> >> I'll be away through Thursday. I may have email, but don't know if
> >> the connection would be good enough to try and roll a release.
> >>
> >>
> >> If anyone want to jump in, please feel free.
> >>
> >>
> >> -Ted.
> >>
> >>
> >> --------------------------------------------------------------------
> >> - 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
> >
> >
>
>
> ---------------------------------------------------------------------
> 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: Struts 1.2.1 release?
Posted by Martin Cooper <ma...@apache.org>.
On Thu, 1 Jul 2004, Don Brown wrote:
> I vote we just roll it anyways. If we have switched to tomcat-style
> releases, we can just not label it as stable. I asked one of the tomcat
> guys last nite at the JakartaOne party if they close out all their bugs
> and he laughed :)
You weren't talking to Costin, by any chance, were you? ;-)
(Rhetorical question - you were spotted. ;)
--
Martin Cooper
>
> Don
>
>> So, if we can solve 29285, it looks like 1.2.1 would be ready to roll.
>>
>> On Fri, 25 Jun 2004 22:27:39 -0400, Ted Husted wrote:
>>> OK, we're down to 4 problem tickets. Two are against the validator,
>>> but patches are not available. Two are against Struts-Faces, and
>>> could actually be skipped since Struts-Faces would not be in the
>>> 1.2.1 release.
>>>
>>>
>>> The release notes are updated, so if we can swat #29285 and #29796,
>>> we could try rolling Struts 1.2.1.
>>>
>>>
>>> I'll be away through Thursday. I may have email, but don't know if
>>> the connection would be good enough to try and roll a release.
>>>
>>>
>>> If anyone want to jump in, please feel free.
>>>
>>>
>>> -Ted.
>>>
>>>
>>> --------------------------------------------------------------------
>>> - 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
>>
>>
>
>
> ---------------------------------------------------------------------
> 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: Struts 1.2.1 release?
Posted by Joe Germuska <Jo...@Germuska.com>.
At 7:58 AM -0700 7/8/04, KUROSAKA Teruhiko wrote:
>Ted,
>
>I'm now testing, tagging, and rolling Struts 1.2.1. Please stand by :)
>
>As far as I can tell by monitoring this list, 1.2.1 seems to fix
>only face related few bugs. It didn't pick most patches available
>in bugzilla.
>
>Could you tell comitters pick patches for the next release? Only
>by a chance?
>
>I'm not complaining. I just want to know what else I can do
>to make sure my patch will be picked next time.
As far as I know, there's no formal way in which patches are applied.
Obviously, non-enhancements are applied sooner, especially if there
is a test case available to help guarantee that the patch fixes the
problem and doesn't cause others.
As for enhancement requests, Ted has indicated that he is most
interested in applying patches that have a healthy discussion in
Bugzilla, because it indicates to him that there are interested
parties. Bugzilla also supports "votes" for patches, and I think
that it makes sense for people to vote for enhancements which they
think would be particularly good additions to Struts. Finally, users
who are really interested in helping out can apply patches themselves
to their own CVS repository and provide feedback about whether they
work as advertised and don't break anything.
You can understand that committers are hesitant to apply every
enhancement simply because it has been requested. I'd be reluctant
to commit a patch if I didn't feel that I could test it adequately.
Hence, it is helpful if in addition to submitting enhancements other
users of Struts can also test enhancements that they think would be
good to add.
Just my opinion (plus one paraphrase of Ted :^)
Joe
PS While I was composing this, Roberto wrote:
>Given that the committers are busy people, I'd guess one way to get
>a patch considered is to actively seek out struts developers who are
>experiencing the problem that your patch fixes, and get them to test
>it for you - you're doing them a favour, and if several of them add
>a 'works for me' to the ticket, there's a better chance it'll get
>noticed by the commiters.
As long as "developers" is understood as any user who is willing to
treat the source code as "his own", I agree completely -- just don't
think that "developers" == "committers".
--
Joe Germuska
Joe@Germuska.com
http://blog.germuska.com
"In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn
back; I'll know I'm in the wrong place."
- Carlos Santana
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts 1.2.1 release?
Posted by Craig McClanahan <cr...@apache.org>.
KUROSAKA Teruhiko wrote:
> Ted,
>
>> I'm now testing, tagging, and rolling Struts 1.2.1. Please stand by :)
>
>
> As far as I can tell by monitoring this list, 1.2.1 seems to fix
> only face related few bugs. It didn't pick most patches available
> in bugzilla.
If by "face" you mean JavaServer Faces, it doesn't actually include
*any* of those changes ... the Struts-Faces integration library is not a
part of the core release, and will be released separately when it's
done. That being said, there have been a very large number of changes
(both enhancements and bug fixes) to Struts since 1.1 was released (over
a year ago). A brief summary of those changes can be found in the
release notes document (grab the nightly build, install the
struts-documentation webapp, and navigate to page
"userGuide/release-notes.html"). Yet, few people are benefitting from
those changes because they are hesitant to rely on "unreleased" software.
So, our primary mission at this point is to get one stable release out
the door in the 1.2.x chain, so that users can get the benefits of all
those improvements. After that occurs, I for one will certainly feel
less hesitant about applying patches provided in Bugzilla reports --
especially those that have unit test additions to, so we can avoid
future regressions in the areas being corrected.
>
> Could you tell comitters pick patches for the next release? Only
> by a chance?
>
> I'm not complaining. I just want to know what else I can do
> to make sure my patch will be picked next time.
>
> Regards,
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Struts 1.2.1 release?
Posted by KUROSAKA Teruhiko <ku...@bhlab.com>.
Ted,
> I'm now testing, tagging, and rolling Struts 1.2.1. Please stand by :)
As far as I can tell by monitoring this list, 1.2.1 seems to fix
only face related few bugs. It didn't pick most patches available
in bugzilla.
Could you tell comitters pick patches for the next release? Only
by a chance?
I'm not complaining. I just want to know what else I can do
to make sure my patch will be picked next time.
Regards,
--
KUROSAKA ("Kuro") Teruhiko, San Francisco, California, USA
Internationalization Consultant --- now available for new contracts!
http://www.bhlab.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1
release)
Posted by Vic Cekvenich <ce...@portalvu.com>.
#2 I think.
.V
Ted Husted wrote:
> The repository is tagged for STRUTS_1_2_1, and the release is available for review at
>
> * http://www.apache.org/~husted/struts/v1.2.1
>
> Once you have had a chance to review the release, please respond as to whether we should
>
> ----
>
> [ ] Keep this release at Alpha. Followup reports filed to Bugzilla.
>
> [*] Promote this release to Beta and announce on Struts User for further testing
>
> [ ] Promote this release to General Availability now (*)
>
> ----
>
> (*) A vote to promote Struts 1.2.1 to GA must follow a corresponding vote to promote Commons Validator 1.1.3 to GA.
>
> Releases are subject to majority approval of the PMC, and the status may be changed at any time.
>
> Votes and feedback from *all* Struts developers is very welcome.
>
> -Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1
release)
Posted by Nicolas De Loof <ni...@capgemini.com>.
+1 to promote to Beta.
We do not use some 1.2.x added feature, but I didn't notice any trouble when upgrading to 1.2.1 jars.
Nico.
> The repository is tagged for STRUTS_1_2_1, and the release is available for review at
>
> * http://www.apache.org/~husted/struts/v1.2.1
>
> Once you have had a chance to review the release, please respond as to whether we should
>
> ----
>
> [ ] Keep this release at Alpha. Followup reports filed to Bugzilla.
>
> [*] Promote this release to Beta and announce on Struts User for further testing
>
> [ ] Promote this release to General Availability now (*)
>
> ----
>
> (*) A vote to promote Struts 1.2.1 to GA must follow a corresponding vote to promote Commons Validator 1.1.3 to GA.
>
> Releases are subject to majority approval of the PMC, and the status may be changed at any time.
>
> Votes and feedback from *all* Struts developers is very welcome.
>
> -Ted.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
Our name has changed. Please update your address book to the following format: "recipient@capgemini.com".
This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1 release)
Posted by Niall Pemberton <ni...@blueyonder.co.uk>.
It counts but its just not "binding" - like mine.
+1 from me too.
Niall
----- Original Message -----
From: "Michael Rassmussen" <ra...@gmail.com>
To: "Struts Developers List" <de...@struts.apache.org>
Sent: Friday, July 23, 2004 4:46 PM
Subject: Re: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1
release)
> +1 even though my vote doesn't count
>
> On Fri, 23 Jul 2004 09:33:44 -0400, Ted Husted <hu...@apache.org> wrote:
> > We've only had a very few, very light tickets since the release of
Struts 1.2.1 Beta.
> >
> > I'd like to propose that we tag and release Struts 1.2.2 on Monday and
post it for a quality vote.
> >
> > Please note that we can vote a release directly from Alpha to GA, if
that's how we feel about it.
> >
> >
> >
> > -Ted.
> >
> > ---------------------------------------------------------------------
> > 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
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1 release)
Posted by Michael Rassmussen <ra...@gmail.com>.
+1 even though my vote doesn't count
On Fri, 23 Jul 2004 09:33:44 -0400, Ted Husted <hu...@apache.org> wrote:
> We've only had a very few, very light tickets since the release of Struts 1.2.1 Beta.
>
> I'd like to propose that we tag and release Struts 1.2.2 on Monday and post it for a quality vote.
>
> Please note that we can vote a release directly from Alpha to GA, if that's how we feel about it.
>
>
>
> -Ted.
>
> ---------------------------------------------------------------------
> 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: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1 release)
Posted by Craig McClanahan <cr...@gmail.com>.
On Fri, 23 Jul 2004 17:07:25 +0100, Niall Pemberton
<ni...@blueyonder.co.uk> wrote:
> Looking at the outstanding bugs (only 3 hooray!) seems to me the only issue
> is with 29809
>
> http://issues.apache.org/bugzilla/show_bug.cgi?id=29809
>
> Craig questioned whether this patch was needed at all. I guess that unless
> the issue is resolved the decision needs to be made on whether to release
> with or without this patch included.
>
Actually, that patch isn't relevant to Struts 1.2.2, since it applies
to struts-faces, which isn't included :-).
+1 on 1.2.2
> Niall
Craig
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1 release)
Posted by Niall Pemberton <ni...@blueyonder.co.uk>.
Looking at the outstanding bugs (only 3 hooray!) seems to me the only issue
is with 29809
http://issues.apache.org/bugzilla/show_bug.cgi?id=29809
Craig questioned whether this patch was needed at all. I guess that unless
the issue is resolved the decision needs to be made on whether to release
with or without this patch included.
Niall
----- Original Message -----
From: "Ted Husted" <hu...@apache.org>
To: "Struts Developers List" <de...@struts.apache.org>
Sent: Friday, July 23, 2004 2:33 PM
Subject: Re: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1
release)
We've only had a very few, very light tickets since the release of Struts
1.2.1 Beta.
I'd like to propose that we tag and release Struts 1.2.2 on Monday and post
it for a quality vote.
Please note that we can vote a release directly from Alpha to GA, if that's
how we feel about it.
-Ted.
---------------------------------------------------------------------
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: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1 release)
Posted by James Holmes <ja...@jamesholmes.com>.
+1
Ted Husted wrote:
>We've only had a very few, very light tickets since the release of Struts
1.2.1 Beta.
>
>I'd like to propose that we tag and release Struts 1.2.2 on Monday and post
it for a quality vote.
>
>Please note that we can vote a release directly from Alpha to GA, if that's
how we feel about it.
>
>-Ted.
>
>
>
>---------------------------------------------------------------------
>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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1
release)
Posted by Don Brown <mr...@twdata.org>.
+1 on Struts 1.2.2
Ted Husted wrote:
>We've only had a very few, very light tickets since the release of Struts 1.2.1 Beta.
>
>I'd like to propose that we tag and release Struts 1.2.2 on Monday and post it for a quality vote.
>
>Please note that we can vote a release directly from Alpha to GA, if that's how we feel about it.
>
>-Ted.
>
>
>
>---------------------------------------------------------------------
>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: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1 release)
Posted by Ted Husted <hu...@apache.org>.
We've only had a very few, very light tickets since the release of Struts 1.2.1 Beta.
I'd like to propose that we tag and release Struts 1.2.2 on Monday and post it for a quality vote.
Please note that we can vote a release directly from Alpha to GA, if that's how we feel about it.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1 release)
Posted by Ted Husted <hu...@apache.org>.
Or, if someone else want to put 1.2.1 into distribution today, that would be fine with me too :)
On Sat, 10 Jul 2004 11:16:09 -0400, Ted Husted wrote:
> The earliest I can schedule another block of time for Struts is
> tomorrow night.
>
> I'm thinking #27332 would be good to include, so I may tag, roll,
> and post 1.2.2 as the Beta instead, with the 2.0.8 ORO dependency.
>
> If there are any other "mostly harmless" changes people would like
> to slip in, now is the time.
>
> -Ted.
>
> On Sat, 10 Jul 2004 16:08:57 +0100, Niall Pemberton wrote:
>
>> Ted,
>>
>> 48 Hours since your call for a vote and its a unanimous +1 for
>> Beta so far (from the people who matter) - theres only 4 PMC
>> members who are active on this list who haven't voted so far -
>> how long before the VOTE is declared?
>>
>> Niall
>>
>>
>> PMC Binding Votes:
>> --------------------------
>> Don Brown: +1 GA or Beta
>> David Graham +1 Beta
>> Joe Germuska +1 Beta
>> James Homes +1 Beta
>> Steve Raeburn +1 Beta
>> Ted Husted (presume +1 but hasn't indicated a preference)
>>
>> Other Non-Binding Votes
>> ----------------------------------
>> Niall Pemberton +1 GA or Beta
>> Manfred Wolff +1 GA
>> Nicolas De Loof +1 Beta
>> Vik Cekvenich +1 Beta
>>
>>
>> "Active" PMC Members Who Haven't Voted
>> -------------------------------------------------------------
>> Craig McClanahan Rob Leland Martin Cooper James Mitchell
>>
>> "Don't Seem to be Active" PMC Members Who Haven't Voted ---------
>> ----------------------------------------------------------- -----
>> --- -------- Cedric Dumoulin Arron Bates David Karr James Turner
>>
>>
>> ----- Original Message -----
>> From: "Ted Husted" <hu...@apache.org>
>> To: "Struts Developers List" <de...@struts.apache.org> Sent:
>> Thursday, July 08, 2004 3:47 PM
>> Subject: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts
>> 1.2.1 release)
>>
>>
>> The repository is tagged for STRUTS_1_2_1, and the release is
>> available for review at
>>
>> * http://www.apache.org/~husted/struts/v1.2.1
>>
>> Once you have had a chance to review the release, please respond
>> as to whether we should
>>
>> ----
>>
>> [ ] Keep this release at Alpha. Followup reports filed to
>> Bugzilla.
>>
>> [ ] Promote this release to Beta and announce on Struts User for
>> further testing
>>
>> [ ] Promote this release to General Availability now (*)
>>
>> ----
>>
>> (*) A vote to promote Struts 1.2.1 to GA must follow a
>> corresponding vote to promote Commons Validator 1.1.3 to GA.
>>
>> Releases are subject to majority approval of the PMC, and the
>> status may be changed at any time.
>>
>> Votes and feedback from *all* Struts developers is very welcome.
>>
>> -Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1 release)
Posted by Ted Husted <hu...@apache.org>.
The earliest I can schedule another block of time for Struts is tomorrow night.
I'm thinking #27332 would be good to include, so I may tag, roll, and post 1.2.2 as the Beta instead, with the 2.0.8 ORO dependency.
If there are any other "mostly harmless" changes people would like to slip in, now is the time.
-Ted.
On Sat, 10 Jul 2004 16:08:57 +0100, Niall Pemberton wrote:
> Ted,
>
> 48 Hours since your call for a vote and its a unanimous +1 for Beta
> so far (from the people who matter) - theres only 4 PMC members who
> are active on this list who haven't voted so far - how long before
> the VOTE is declared?
>
> Niall
>
>
> PMC Binding Votes:
> --------------------------
> Don Brown: +1 GA or Beta
> David Graham +1 Beta
> Joe Germuska +1 Beta
> James Homes +1 Beta
> Steve Raeburn +1 Beta
> Ted Husted (presume +1 but hasn't indicated a preference)
>
> Other Non-Binding Votes
> ----------------------------------
> Niall Pemberton +1 GA or Beta
> Manfred Wolff +1 GA
> Nicolas De Loof +1 Beta
> Vik Cekvenich +1 Beta
>
>
> "Active" PMC Members Who Haven't Voted
> ------------------------------------------------------------- Craig
> McClanahan Rob Leland Martin Cooper James Mitchell
>
> "Don't Seem to be Active" PMC Members Who Haven't Voted
> --------------------------------------------------------------------
> -------- -------- Cedric Dumoulin Arron Bates David Karr James
> Turner
>
>
> ----- Original Message -----
> From: "Ted Husted" <hu...@apache.org>
> To: "Struts Developers List" <de...@struts.apache.org>
> Sent: Thursday, July 08, 2004 3:47 PM
> Subject: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts
> 1.2.1 release)
>
>
> The repository is tagged for STRUTS_1_2_1, and the release is
> available for review at
>
> * http://www.apache.org/~husted/struts/v1.2.1
>
> Once you have had a chance to review the release, please respond as
> to whether we should
>
> ----
>
> [ ] Keep this release at Alpha. Followup reports filed to Bugzilla.
>
> [ ] Promote this release to Beta and announce on Struts User for
> further testing
>
> [ ] Promote this release to General Availability now (*)
>
> ----
>
> (*) A vote to promote Struts 1.2.1 to GA must follow a
> corresponding vote to promote Commons Validator 1.1.3 to GA.
>
> Releases are subject to majority approval of the PMC, and the
> status may be changed at any time.
>
> Votes and feedback from *all* Struts developers is very welcome.
>
> -Ted.
>
>
> --------------------------------------------------------------------
> - 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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1 release)
Posted by Niall Pemberton <ni...@blueyonder.co.uk>.
Ted,
48 Hours since your call for a vote and its a unanimous +1 for Beta so far
(from the people who matter) - theres only 4 PMC members who are active on
this list who haven't voted so far - how long before the VOTE is declared?
Niall
PMC Binding Votes:
--------------------------
Don Brown: +1 GA or Beta
David Graham +1 Beta
Joe Germuska +1 Beta
James Homes +1 Beta
Steve Raeburn +1 Beta
Ted Husted (presume +1 but hasn't indicated a preference)
Other Non-Binding Votes
----------------------------------
Niall Pemberton +1 GA or Beta
Manfred Wolff +1 GA
Nicolas De Loof +1 Beta
Vik Cekvenich +1 Beta
"Active" PMC Members Who Haven't Voted
-------------------------------------------------------------
Craig McClanahan
Rob Leland
Martin Cooper
James Mitchell
"Don't Seem to be Active" PMC Members Who Haven't Voted
----------------------------------------------------------------------------
--------
Cedric Dumoulin
Arron Bates
David Karr
James Turner
----- Original Message -----
From: "Ted Husted" <hu...@apache.org>
To: "Struts Developers List" <de...@struts.apache.org>
Sent: Thursday, July 08, 2004 3:47 PM
Subject: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1
release)
The repository is tagged for STRUTS_1_2_1, and the release is available for
review at
* http://www.apache.org/~husted/struts/v1.2.1
Once you have had a chance to review the release, please respond as to
whether we should
----
[ ] Keep this release at Alpha. Followup reports filed to Bugzilla.
[ ] Promote this release to Beta and announce on Struts User for further
testing
[ ] Promote this release to General Availability now (*)
----
(*) A vote to promote Struts 1.2.1 to GA must follow a corresponding vote to
promote Commons Validator 1.1.3 to GA.
Releases are subject to majority approval of the PMC, and the status may be
changed at any time.
Votes and feedback from *all* Struts developers is very welcome.
-Ted.
---------------------------------------------------------------------
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: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1 release)
Posted by Niall Pemberton <ni...@blueyonder.co.uk>.
+1 for GA or if not at least Beta - I know the last release never went
anywhere, but there was no pointer on the web site as to where it could be
downloaded from and "where is it" came up regularly on the user list.
Niall
----- Original Message -----
From: "Ted Husted" <hu...@apache.org>
To: "Struts Developers List" <de...@struts.apache.org>
Sent: Thursday, July 08, 2004 3:47 PM
Subject: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1
release)
The repository is tagged for STRUTS_1_2_1, and the release is available for
review at
* http://www.apache.org/~husted/struts/v1.2.1
Once you have had a chance to review the release, please respond as to
whether we should
----
[ ] Keep this release at Alpha. Followup reports filed to Bugzilla.
[ ] Promote this release to Beta and announce on Struts User for further
testing
[ ] Promote this release to General Availability now (*)
----
(*) A vote to promote Struts 1.2.1 to GA must follow a corresponding vote to
promote Commons Validator 1.1.3 to GA.
Releases are subject to majority approval of the PMC, and the status may be
changed at any time.
Votes and feedback from *all* Struts developers is very welcome.
-Ted.
---------------------------------------------------------------------
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: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1 release)
Posted by Ted Husted <hu...@apache.org>.
Going from Alpha/Beta to GA is no different than going from RC to Final. A belief that the distribution has been widely tested and an absence of problem reports.
I doubt that we'd have the courage to promote 1.2.1 from Alpha to GA, but if some minor issues were found and fixed in a 1.2.1 beta, we might want to take a 1.2.2 from Alpha direct to GA. Of course, I'd prefer that 1.2.1 went from Beta to GA, if it merits that lofty status :)
-Ted.
<<... leaving on that midnight train to Georgia ...>>
On Fri, 09 Jul 2004 09:48:02 -0500, Joe Germuska wrote:
>�+1 �for beta; I've plugged 1.2.1 into an app which in in another
>�dev cycle and so should be able to give it a pretty good workout.
>�Not quite sure what our threshold for GA is... a certain time
>�period? Sworn testimonials? �A sign from above?
>
>�Joe
>
>�At 10:47 AM -0400 7/8/04, Ted Husted wrote:
>>�The repository is tagged for STRUTS_1_2_1, and the release is
>>�available for review at
>>
>>�* http://www.apache.org/~husted/struts/v1.2.1
>>
>>�Once you have had a chance to review the release, please respond
>>�as to whether we should
>>�[ ] Keep this release at Alpha. Followup reports filed to
>>�Bugzilla.
>>
>>�[* ] Promote this release to Beta and announce on Struts User for
>>�further testing
>>
>>�[ ] Promote this release to General Availability now (*)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1
release)
Posted by Joe Germuska <Jo...@Germuska.com>.
+1 for beta; I've plugged 1.2.1 into an app which in in another dev
cycle and so should be able to give it a pretty good workout. Not
quite sure what our threshold for GA is... a certain time period?
Sworn testimonials? A sign from above?
Joe
At 10:47 AM -0400 7/8/04, Ted Husted wrote:
>The repository is tagged for STRUTS_1_2_1, and the release is
>available for review at
>
>* http://www.apache.org/~husted/struts/v1.2.1
>
>Once you have had a chance to review the release, please respond as
>to whether we should
>[ ] Keep this release at Alpha. Followup reports filed to Bugzilla.
>
>[* ] Promote this release to Beta and announce on Struts User for
>further testing
>
>[ ] Promote this release to General Availability now (*)
--
Joe Germuska
Joe@Germuska.com
http://blog.germuska.com
"In fact, when I die, if I don't hear 'A Love Supreme,' I'll turn
back; I'll know I'm in the wrong place."
- Carlos Santana
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1
release)
Posted by Manfred Wolff <wo...@manfred-wolff.de>.
+1 for GA. I use the nightly builds since the 1.2.0 branch is forked.
-Manfred
Ted Husted wrote:
>The repository is tagged for STRUTS_1_2_1, and the release is available for review at
>
>* http://www.apache.org/~husted/struts/v1.2.1
>
>Once you have had a chance to review the release, please respond as to whether we should
>
>----
>
>[ ] Keep this release at Alpha. Followup reports filed to Bugzilla.
>
>[ ] Promote this release to Beta and announce on Struts User for further testing
>
>[ ] Promote this release to General Availability now (*)
>
>----
>
>(*) A vote to promote Struts 1.2.1 to GA must follow a corresponding vote to promote Commons Validator 1.1.3 to GA.
>
>Releases are subject to majority approval of the PMC, and the status may be changed at any time.
>
>Votes and feedback from *all* Struts developers is very welcome.
>
>-Ted.
>
>
>---------------------------------------------------------------------
>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: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1
release)
Posted by Don Brown <mr...@twdata.org>.
+1 for GA or Beta
This would still be made available through the usual apache download
pages as a Beta correct?
Don
Ted Husted wrote:
>The repository is tagged for STRUTS_1_2_1, and the release is available for review at
>
>* http://www.apache.org/~husted/struts/v1.2.1
>
>Once you have had a chance to review the release, please respond as to whether we should
>
>----
>
>[ ] Keep this release at Alpha. Followup reports filed to Bugzilla.
>
>[ ] Promote this release to Beta and announce on Struts User for further testing
>
>[ ] Promote this release to General Availability now (*)
>
>----
>
>(*) A vote to promote Struts 1.2.1 to GA must follow a corresponding vote to promote Commons Validator 1.1.3 to GA.
>
>Releases are subject to majority approval of the PMC, and the status may be changed at any time.
>
>Votes and feedback from *all* Struts developers is very welcome.
>
>-Ted.
>
>
>---------------------------------------------------------------------
>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: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1 release)
Posted by James Holmes <ja...@jamesholmes.com>.
+1 for beta
-----Original Message-----
From: Ted Husted [mailto:husted@apache.org]
Sent: Thursday, July 08, 2004 9:48 AM
To: Struts Developers List
Subject: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1
release)
The repository is tagged for STRUTS_1_2_1, and the release is available for
review at
* http://www.apache.org/~husted/struts/v1.2.1
Once you have had a chance to review the release, please respond as to
whether we should
----
[ ] Keep this release at Alpha. Followup reports filed to Bugzilla.
[ ] Promote this release to Beta and announce on Struts User for further
testing
[ ] Promote this release to General Availability now (*)
----
(*) A vote to promote Struts 1.2.1 to GA must follow a corresponding vote to
promote Commons Validator 1.1.3 to GA.
Releases are subject to majority approval of the PMC, and the status may be
changed at any time.
Votes and feedback from *all* Struts developers is very welcome.
-Ted.
---------------------------------------------------------------------
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: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1 release)
Posted by David Graham <gr...@yahoo.com>.
+1 on beta. I'm not sure we really need a separate lib distro though.
David
--- Ted Husted <hu...@apache.org> wrote:
> The repository is tagged for STRUTS_1_2_1, and the release is available
> for review at
>
> * http://www.apache.org/~husted/struts/v1.2.1
>
> Once you have had a chance to review the release, please respond as to
> whether we should
>
> ----
>
> [ ] Keep this release at Alpha. Followup reports filed to Bugzilla.
>
> [ ] Promote this release to Beta and announce on Struts User for further
> testing
>
> [ ] Promote this release to General Availability now (*)
>
> ----
>
> (*) A vote to promote Struts 1.2.1 to GA must follow a corresponding
> vote to promote Commons Validator 1.1.3 to GA.
>
> Releases are subject to majority approval of the PMC, and the status may
> be changed at any time.
>
> Votes and feedback from *all* Struts developers is very welcome.
>
> -Ted.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
>
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
RE: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1 release)
Posted by Steve Raeburn <sr...@apache.org>.
+1 Beta
Steve
> -----Original Message-----
> From: Ted Husted [mailto:husted@apache.org]
> Sent: July 8, 2004 7:48 AM
> To: Struts Developers List
> Subject: [VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1
> release)
>
>
> The repository is tagged for STRUTS_1_2_1, and the release is
> available for review at
>
> * http://www.apache.org/~husted/struts/v1.2.1
>
> Once you have had a chance to review the release, please
> respond as to whether we should
>
> ----
>
> [ ] Keep this release at Alpha. Followup reports filed to Bugzilla.
>
> [ ] Promote this release to Beta and announce on Struts User
> for further testing
>
> [ ] Promote this release to General Availability now (*)
>
> ----
>
> (*) A vote to promote Struts 1.2.1 to GA must follow a
> corresponding vote to promote Commons Validator 1.1.3 to GA.
>
> Releases are subject to majority approval of the PMC, and the
> status may be changed at any time.
>
> Votes and feedback from *all* Struts developers is very welcome.
>
> -Ted.
>
>
> ---------------------------------------------------------------------
> 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
[VOTE] Struts 1.2.1 Alpha, Beta, or GA? (was Re: Struts 1.2.1 release)
Posted by Ted Husted <hu...@apache.org>.
The repository is tagged for STRUTS_1_2_1, and the release is available for review at
* http://www.apache.org/~husted/struts/v1.2.1
Once you have had a chance to review the release, please respond as to whether we should
----
[ ] Keep this release at Alpha. Followup reports filed to Bugzilla.
[ ] Promote this release to Beta and announce on Struts User for further testing
[ ] Promote this release to General Availability now (*)
----
(*) A vote to promote Struts 1.2.1 to GA must follow a corresponding vote to promote Commons Validator 1.1.3 to GA.
Releases are subject to majority approval of the PMC, and the status may be changed at any time.
Votes and feedback from *all* Struts developers is very welcome.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
RE: Struts 1.2.1 release?
Posted by Ted Husted <hu...@apache.org>.
I'm now testing, tagging, and rolling Struts 1.2.1. Please stand by :)
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
RE: Struts 1.2.1 release?
Posted by Martin Cooper <ma...@apache.org>.
On Thu, 1 Jul 2004, Ted Husted wrote:
> On Thu, 01 Jul 2004 13:13:43 -0700 (PDT), Don Brown wrote:
>> I vote we just roll it anyways. If we have switched to tomcat-
>> style releases, we can just not label it as stable. I asked one of
>> the tomcat guys last nite at the JakartaOne party if they close out
>> all their bugs and he laughed :)
>>
>> Don
>
> If you want to roll it, Don, that's fine with me.
>
> Though, since it's been a year-and-a-day since our last stable release, I was hoping 1.2.1 would be It :)
I haven't been counting quite as closely, but I agree with the sentiment.
Let's not just throw another release out there for the sake of it, let's
try to make this one the stable 1.2.x so that we can move on to bigger and
better things.
--
Martin Cooper
>
> -Ted.
>
>>
>>
>>> So, if we can solve 29285, it looks like 1.2.1 would be ready to
>>> roll.
>>>
>>>
>>> On Fri, 25 Jun 2004 22:27:39 -0400, Ted Husted wrote:
>>>
>>>> OK, we're down to 4 problem tickets. Two are against the
>>>> validator, but patches are not available. Two are against
>>>> Struts-Faces, and could actually be skipped since Struts-Faces
>>>> would not be in the 1.2.1 release.
>>>>
>>>>
>>>> The release notes are updated, so if we can swat #29285 and
>>>> #29796, we could try rolling Struts 1.2.1.
>>>>
>>>>
>>>> I'll be away through Thursday. I may have email, but don't know
>>>> if the connection would be good enough to try and roll a
>>>> release.
>>>>
>>>>
>>>> If anyone want to jump in, please feel free.
>>>>
>>>>
>>>> -Ted.
>>>>
>>>>
>>>> ----------------------------------------------------------------
>>>> ---- - 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
>>
>>
>> --------------------------------------------------------------------
>> - 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
RE: Struts 1.2.1 release?
Posted by Ted Husted <hu...@apache.org>.
On Thu, 01 Jul 2004 13:13:43 -0700 (PDT), Don Brown wrote:
> I vote we just roll it anyways. If we have switched to tomcat-
> style releases, we can just not label it as stable. I asked one of
> the tomcat guys last nite at the JakartaOne party if they close out
> all their bugs and he laughed :)
>
> Don
If you want to roll it, Don, that's fine with me.
Though, since it's been a year-and-a-day since our last stable release, I was hoping 1.2.1 would be It :)
-Ted.
>
>
>> So, if we can solve 29285, it looks like 1.2.1 would be ready to
>> roll.
>>
>>
>> On Fri, 25 Jun 2004 22:27:39 -0400, Ted Husted wrote:
>>
>>> OK, we're down to 4 problem tickets. Two are against the
>>> validator, but patches are not available. Two are against
>>> Struts-Faces, and could actually be skipped since Struts-Faces
>>> would not be in the 1.2.1 release.
>>>
>>>
>>> The release notes are updated, so if we can swat #29285 and
>>> #29796, we could try rolling Struts 1.2.1.
>>>
>>>
>>> I'll be away through Thursday. I may have email, but don't know
>>> if the connection would be good enough to try and roll a
>>> release.
>>>
>>>
>>> If anyone want to jump in, please feel free.
>>>
>>>
>>> -Ted.
>>>
>>>
>>> ----------------------------------------------------------------
>>> ---- - 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
>
>
> --------------------------------------------------------------------
> - 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: Struts 1.2.1 release?
Posted by Don Brown <mr...@twdata.org>.
I vote we just roll it anyways. If we have switched to tomcat-style
releases, we can just not label it as stable. I asked one of the tomcat
guys last nite at the JakartaOne party if they close out all their bugs
and he laughed :)
Don
> So, if we can solve 29285, it looks like 1.2.1 would be ready to roll.
>
> On Fri, 25 Jun 2004 22:27:39 -0400, Ted Husted wrote:
>> OK, we're down to 4 problem tickets. Two are against the validator,
>> but patches are not available. Two are against Struts-Faces, and
>> could actually be skipped since Struts-Faces would not be in the
>> 1.2.1 release.
>>
>>
>> The release notes are updated, so if we can swat #29285 and #29796,
>> we could try rolling Struts 1.2.1.
>>
>>
>> I'll be away through Thursday. I may have email, but don't know if
>> the connection would be good enough to try and roll a release.
>>
>>
>> If anyone want to jump in, please feel free.
>>
>>
>> -Ted.
>>
>>
>> --------------------------------------------------------------------
>> - 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
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org