> As for 1.2.0 testing, I would suggest we do TC 3.3.1a and 4.1.28,
Ooops, 4.1.29
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
If the Validation 1.1.1 release is imminent, the best thing might be to
just let that be the Struts 1.2.0 trigger. If it happens a few days
later, then so be it. As it stands, TC3 is our 2.2/1.2 benchmark, and we
don't want to start cutting corners.
Of course, if anyone wanted to step up to bat
Ted Husted wrote:
> T e d :
>
> If I understand the X.X.X release convention, a Vote doesn't have to
> be held for a release to occur
> but only to qualify it as Alpha/Beta/GA ? Is that correct?
>
> If that is so I could just stay up tonight and do a release and we
> would vote on the quality
>
> T e d :
>
> If I understand the X.X.X release convention, a Vote doesn't have to
> be held for a release to occur
> but only to qualify it as Alpha/Beta/GA ? Is that correct?
>
> If that is so I could just stay up tonight and do a release and we
> would vote on the quality
> at a later date, on
On Tue, 25 Nov 2003, Ted Husted wrote:
> Do you want to tag-team on the release again?
Sure.
>
> As it happens, I'm out of town again next Tuesday-Friday, and it would
> be good if there were another RM ready to step in for any mopping up
> mopped up.
I'll get my mop and bucket ready. ;-)
--
M
Brandon Goodin wrote:
When are submitted patches going to be reviewed and incorporated? There
seems to be several out there that are useful.
Which patches are you suggesting, and have you tested any of them
yourself or
have any comments about suggested solutions ?
---
Ted Husted wrote:
AFAIK, it's a decent milestone already. :)
I believe to get it ready for "prime time" as a General Availability
release will mainly be a matter of updating the documentation. But,
the best way to generate some interest in doing that may be to publish
a milestone release.
Als
Do you want to tag-team on the release again?
As it happens, I'm out of town again next Tuesday-Friday, and it would
be good if there were another RM ready to step in for any mopping up
mopped up.
-T.
Martin Cooper wrote:
On Tue, 25 Nov 2003, Ted Husted wrote:
With the long weekend coming up
On Tue, 25 Nov 2003, Ted Husted wrote:
> With the long weekend coming up, I was thinking of rolling up my sleeves
> and doing whatever needs to be done to cut 1.2.0.
Funny you should bring that up. I'm planning on spending a good chunk of
this upcoming break in Apache land myself.
>
> Anyone one
I'm going to need to check for any updates to the tag interfaces and
move them to Struts-EL. I'll make sure that's done before this weekend.
> -Original Message-
> From: Ted Husted [mailto:[EMAIL PROTECTED]
>
> With the long weekend coming up, I was thinking of rolling up
> my sleeves
When are submitted patches going to be reviewed and incorporated? There
seems to be several out there that are useful.
>>> [EMAIL PROTECTED] 11/25/2003 5:06:52 AM >>>
With the long weekend coming up, I was thinking of rolling up my
sleeves
and doing whatever needs to be done to cut 1.2.0.
Anyon
AFAIK, it's a decent milestone already. :)
I believe to get it ready for "prime time" as a General Availability
release will mainly be a matter of updating the documentation. But, the
best way to generate some interest in doing that may be to publish a
milestone release.
Also, to make the GA g
TECTED]
> Sent: Tuesday, November 25, 2003 8:45 AM
> To: Struts Developers List
> Subject: Re: 1.2.0 Resurrected
>
>
>
> --- Ted Husted <[EMAIL PROTECTED]> wrote:
> > With the long weekend coming up, I was thinking of rolling up my
> > sleeves
> >
&
--- Ted Husted <[EMAIL PROTECTED]> wrote:
> With the long weekend coming up, I was thinking of rolling up my sleeves
>
> and doing whatever needs to be done to cut 1.2.0.
>
> Anyone one aware of any serious showstoppers?
Nope, the commits have been relatively infrequent and I haven't seen
anyth
What would need to be done to get it to "milestone"
-Tim
Ted Husted wrote:
With the long weekend coming up, I was thinking of rolling up my
sleeves and doing whatever needs to be done to cut 1.2.0.
Anyone one aware of any serious showstoppers?
While under the current scheme, any release has the
With the long weekend coming up, I was thinking of rolling up my sleeves
and doing whatever needs to be done to cut 1.2.0.
Anyone one aware of any serious showstoppers?
While under the current scheme, any release has the potential to make
the General Availability grade, I would anticipate that
16 matches
Mail list logo