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/06/08 15:44:32 UTC
Re: Validator/Struts bugs
[Moving from off-list]
Thanks, Don.
I took this morning "off" to get the the Commons Validator 1.1.3 rolled. Of course, as soon as the updated dependencies hit the street, we can plug those in and roll 1.1.4.
I pinged the Jakarta PMC list about karma for you and Niall, so you should be able to handle these yourself next time around.
So, there's 14 problem tickets open for Struts. If we can squash these, we'll have a Commons Validator 1.1.3 against which to roll Struts 1.2.1. If CV 1.1.3 then goes stable, Struts 1.2.1 could follow suit. Or, if the other Commons dependencies ship, we can roll Struts 1.2.2 against those. But, I believe we do need to keep squashing and releasing, lest we find ourselves on another death march.
I can roll Struts 1.2.1 if no one else is up for it, but someone else would like to give a whirl, please do chime in.
-Ted.
On Mon, 07 Jun 2004 16:43:34 -0400, Don Brown wrote:
> Ok, I've posted patches (and unit tests) or suggested resolutions
> for every bug, but I don't have commit privs yet so I'll let you
> apply them. Now for Struts... :)
>
> Don
>
> Ted Husted wrote:
>
>
>> I read the problem descriptions, but I haven't actually *worked*
>> on any. Was saving that for tonight.
>>
>>
>> Try checking out a copy of jakarta-commons using your Apache
>> login. If you can't commit a change back, like adding your name
>> to the developers list, then I'll ping the PMC again.
>>
>>
>> I'd like to turn around and do Struts 1.2.1 the next day, so
>> we'll need the Struts problem list cleared too, and the Change
>> Log updated. Trying the Validator fixes and posting a "works for
>> me" won't hurt either.
>>
>>
>> -Ted.
>>
>>
>> On Mon, 07 Jun 2004 12:27:03 -0400, Don Brown wrote:
>>
>>
>>> Ted,
>>>
>>>
>>> Any bugs you still haven't worked on? I have some time today I
>>> could help out. Not sure if I have validator commit access
>>> yet, but at least I could post patches.
>>>
>>> Don
---------------------------------------------------------------------
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 plan (was Re: Validator/Struts bugs)
Posted by Niall Pemberton <ni...@blueyonder.co.uk>.
I have committ privledge so I am going to apply the patch.
Niall
----- Original Message -----
From: "James Holmes" <ja...@jamesholmes.com>
To: "'Struts Developers List'" <de...@struts.apache.org>
Sent: Tuesday, June 08, 2004 7:48 PM
Subject: RE: Struts 1.2.1 release plan (was Re: Validator/Struts bugs)
> Ted,
>
> I'd like to get the Struts-Faces build working again (bug #: 28668) for
this
> build. Basically all that needs to happen is the patches attached to bug
#:
> 22207 need to be applied. Does Niall have commit privileges at this
point?
> If not I'd like to commit the patch so that we can get the code in. Any
> issues with this?
>
> -James
>
> -----Original Message-----
> From: Ted Husted [mailto:husted@apache.org]
> Sent: Tuesday, June 08, 2004 1:17 PM
> To: Struts Developers List
> Subject: Struts 1.2.1 release plan (was Re: Validator/Struts bugs)
>
> The Commons Validator tickets and docs are up-to-date now. The next couple
> of days are busy, but I can try to roll Validator 1.1.3 on Thursday, and
> then we could roll Struts 1.2.1 on Friday, if we can get the tickets
> squashed.
>
> -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 plan (was Re: Validator/Struts bugs)
Posted by James Holmes <ja...@jamesholmes.com>.
Ted,
I'd like to get the Struts-Faces build working again (bug #: 28668) for this
build. Basically all that needs to happen is the patches attached to bug #:
22207 need to be applied. Does Niall have commit privileges at this point?
If not I'd like to commit the patch so that we can get the code in. Any
issues with this?
-James
-----Original Message-----
From: Ted Husted [mailto:husted@apache.org]
Sent: Tuesday, June 08, 2004 1:17 PM
To: Struts Developers List
Subject: Struts 1.2.1 release plan (was Re: Validator/Struts bugs)
The Commons Validator tickets and docs are up-to-date now. The next couple
of days are busy, but I can try to roll Validator 1.1.3 on Thursday, and
then we could roll Struts 1.2.1 on Friday, if we can get the tickets
squashed.
-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: Roll back Commons Validator dependancy ( was Struts 1.2.1 release plan)
Posted by David Graham <gr...@yahoo.com>.
Actually, I don't think any Struts release has included a validator 1.1.x
build. So we haven't given people a chance to remove references to
deprecated functionality that has been removed in the 1.2.x series.
You could either apply the patches to the branch or just release 1.1.3
from the branch without patches.
David
--- David Graham <gr...@yahoo.com> wrote:
> Since you patched HEAD, maybe we should forget about the branch and
> 1.1.3
> and just release 1.2.0. If 1.2.0 is a dud we can quickly patch it and
> release 1.2.1. Quick releases are one benefit of the (IMO confusing)
> httpd style versioning.
>
> I would rather see us moving forward than rolling back patches and
> creating more confusion.
>
> David
>
> --- Ted Husted <hu...@apache.org> wrote:
> > I just found out I've been patching and testing the wrong branch of
> the
> > Commons Validator component :(
> >
> > Between this snafu and the issues with Struts Faces, perhaps the best
> > thing would be to roll back the changes that create a dependence on
> > Commons Validator 1.1.3.
> >
> > Do we know if there are any dire issues with Commons Validator 1.1.2
> > that would scuttle a vote to make that a stable release?
> >
> > -Ted.
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> > For additional commands, e-mail: dev-help@struts.apache.org
> >
>
>
>
>
>
> __________________________________
> Do you Yahoo!?
> Friends. Fun. Try the all-new Yahoo! Messenger.
> http://messenger.yahoo.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Re: Roll back Commons Validator dependancy ( was Struts 1.2.1 release plan)
Posted by David Graham <gr...@yahoo.com>.
Since you patched HEAD, maybe we should forget about the branch and 1.1.3
and just release 1.2.0. If 1.2.0 is a dud we can quickly patch it and
release 1.2.1. Quick releases are one benefit of the (IMO confusing)
httpd style versioning.
I would rather see us moving forward than rolling back patches and
creating more confusion.
David
--- Ted Husted <hu...@apache.org> wrote:
> I just found out I've been patching and testing the wrong branch of the
> Commons Validator component :(
>
> Between this snafu and the issues with Struts Faces, perhaps the best
> thing would be to roll back the changes that create a dependence on
> Commons Validator 1.1.3.
>
> Do we know if there are any dire issues with Commons Validator 1.1.2
> that would scuttle a vote to make that a stable release?
>
> -Ted.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
> For additional commands, e-mail: dev-help@struts.apache.org
>
__________________________________
Do you Yahoo!?
Friends. Fun. Try the all-new Yahoo! Messenger.
http://messenger.yahoo.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Roll back Commons Validator dependancy ( was Struts 1.2.1 release plan)
Posted by Ted Husted <hu...@apache.org>.
I just found out I've been patching and testing the wrong branch of the Commons Validator component :(
Between this snafu and the issues with Struts Faces, perhaps the best thing would be to roll back the changes that create a dependence on Commons Validator 1.1.3.
Do we know if there are any dire issues with Commons Validator 1.1.2 that would scuttle a vote to make that a stable release?
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org
Struts 1.2.1 release plan (was Re: Validator/Struts bugs)
Posted by Ted Husted <hu...@apache.org>.
The Commons Validator tickets and docs are up-to-date now. The next couple of days are busy, but I can try to roll Validator 1.1.3 on Thursday, and then we could roll Struts 1.2.1 on Friday, if we can get the tickets squashed.
-Ted.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@struts.apache.org
For additional commands, e-mail: dev-help@struts.apache.org