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 2003/06/06 15:24:18 UTC

[PLAN] Release Struts RC2 with FileUpload RC1

I've posted an updated Release Plan to reflect the consensus we reached 
on RC2. I'm going to work on the struts-legacy release first make the 
necessary adjustments to the build. Then, I'll start on the tests 
gauntlet for RC2, so that I can cut the actual release first thing 
tomorrow morning.

Accordingly, if there is no objection, the codebase will freeze at 
midnight tonight.

The one non-enchancement issue is

http://issues.apache.org/bugzilla/show_bug.cgi?id=19911

I pinged Cedric, and if nothing else comes up, I'll mark it LATER and 
then reopen it against the nightly build after RC2 ships.

Everything else is marked Enhancement, and so I added that clause to the 
Release Plan.

-Ted.



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


Re: [PLAN] Release Struts RC2 with FileUpload RC1

Posted by Ted Husted <hu...@apache.org>.
Forgot the plan URL (which is also on the RoadMap):

http://jakarta.apache.org/struts/proposals/release-plan-1.1rc2.html

Ted Husted wrote:
> I've posted an updated Release Plan to reflect the consensus we reached 
> on RC2. I'm going to work on the struts-legacy release first make the 
> necessary adjustments to the build. Then, I'll start on the tests 
> gauntlet for RC2, so that I can cut the actual release first thing 
> tomorrow morning.
> 
> Accordingly, if there is no objection, the codebase will freeze at 
> midnight tonight.
> 
> The one non-enchancement issue is
> 
> http://issues.apache.org/bugzilla/show_bug.cgi?id=19911
> 
> I pinged Cedric, and if nothing else comes up, I'll mark it LATER and 
> then reopen it against the nightly build after RC2 ships.
> 
> Everything else is marked Enhancement, and so I added that clause to the 
> Release Plan.
> 
> -Ted.
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-dev-help@jakarta.apache.org
> 
> 


-- 
Ted Husted,
Struts in Action <http://husted.com/struts/book.html>



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


Re: [VOTE] Convert RC2 to Beta 5

Posted by Vic Cekvenich <vi...@baseBeans.com>.
(Thanks Ted and others comitters CVSing fixes (David, Martin) for 
donating yet another weekend to Struts, either way).
My comprehension (not again.... Its not flamey this time) is this:

Ted can release today under Beta 5 beta as is (with the known failed 
test) with all the work he did. Plus for this side is... who knows when 
is the next time a release will come, and no release for Java One?, that 
was the motivation here. So it's a step sideways to go forward. +1 means 
release Today, that is how I read it. It's just a name.

Else... someone else (who has tech. skills/experience of Ted) has to 
step forward, at another time to fix and build and release.   So if you 
look at it as beta  vs RC 2... it seems RC2! But when, a week? A month? 
What about the work done last few days? So a - 1 means.... wait.

If you say, hey, lets release something! that works and passes most 
tests in how it's used, and lets move towards final then ... beta 5.

+0 for B5.

.V


James Turner wrote:
> Frankly, since these seem to be problems in the tests and demo
> applications, rather than in the base code, I'd be -1 on this.  Going to
> a beta 5 seems to me to be a unnecessary step unless the problem is in
> the actual core libraries themselves.  
> 
> James
> 
> 
>>-----Original Message-----
>>From: Ted Husted [mailto:husted@apache.org] 
>>Sent: Sunday, June 08, 2003 6:14 PM
>>To: Struts Developers List
>>Subject: [VOTE] Convert RC2 to Beta 5
>>
>>
>>In final testing of RC2, some compatibility issues have been found 
>>between Tomcat 3.3.1 and the struts-exercise-taglib 
>>application as well 
>>as the tiles-documentation application.
>>
>>Martin Cooper has been looking into the problems and has 
>>found that for 
>>the struts-exercise-taglibs cookie test, it is the
>>
>>   <jsp:getProperty name="sess" property="name"/>
>>
>>expression that is failing.
>>
>>The <jsp:getProperty> tags earlier on the page succeeded. The 
>>only difference seems to be that the earlier ones all have 
>>setters as well as 
>>getters in the Tomcat CookieFacade class, whereas there is 
>>only a getter 
>>for 'name'. So this actually looks like some kind of 
>>JSP/reflection bug, 
>>not related to Struts. (The <bean:cookie> tag must have 
>>worked, because 
>>we know the <jsp:getProperty> tag is trying to access a cookie!)
>>
>>Also, the (rather complex) comparison test is killing the JVM 
>>when run 
>>under TC3.
>>
>>In the Tiles application, servlet exceptions are being noted. One 
>>example is the extendedDefinitionTag page, but there may be others.
>>
>>Unless fixes to these problems are immediately forthcoming, I propose 
>>that we document the issues and release Stuts 1.1 beta 5.
>>
>>By getting this milestone out to the community, we would have 
>>a better 
>>chance of resolving the remaining issues so that we can go to Struts 
>>1.1. final as soon as possible
>>
>>This proposal has my +1.
>>
>>-Ted.
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: struts-dev-help@jakarta.apache.org
> 
> 



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


RE: [VOTE] Convert RC2 to Beta 5

Posted by James Turner <tu...@blackbear.com>.
Frankly, since these seem to be problems in the tests and demo
applications, rather than in the base code, I'd be -1 on this.  Going to
a beta 5 seems to me to be a unnecessary step unless the problem is in
the actual core libraries themselves.  

James

> -----Original Message-----
> From: Ted Husted [mailto:husted@apache.org] 
> Sent: Sunday, June 08, 2003 6:14 PM
> To: Struts Developers List
> Subject: [VOTE] Convert RC2 to Beta 5
> 
> 
> In final testing of RC2, some compatibility issues have been found 
> between Tomcat 3.3.1 and the struts-exercise-taglib 
> application as well 
> as the tiles-documentation application.
> 
> Martin Cooper has been looking into the problems and has 
> found that for 
> the struts-exercise-taglibs cookie test, it is the
> 
>    <jsp:getProperty name="sess" property="name"/>
> 
> expression that is failing.
> 
> The <jsp:getProperty> tags earlier on the page succeeded. The 
> only difference seems to be that the earlier ones all have 
> setters as well as 
> getters in the Tomcat CookieFacade class, whereas there is 
> only a getter 
> for 'name'. So this actually looks like some kind of 
> JSP/reflection bug, 
> not related to Struts. (The <bean:cookie> tag must have 
> worked, because 
> we know the <jsp:getProperty> tag is trying to access a cookie!)
> 
> Also, the (rather complex) comparison test is killing the JVM 
> when run 
> under TC3.
> 
> In the Tiles application, servlet exceptions are being noted. One 
> example is the extendedDefinitionTag page, but there may be others.
> 
> Unless fixes to these problems are immediately forthcoming, I propose 
> that we document the issues and release Stuts 1.1 beta 5.
> 
> By getting this milestone out to the community, we would have 
> a better 
> chance of resolving the remaining issues so that we can go to Struts 
> 1.1. final as soon as possible
> 
> This proposal has my +1.
> 
> -Ted.
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-dev-help@jakarta.apache.org
> 



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


[VOTE] Convert RC2 to Beta 5

Posted by Ted Husted <hu...@apache.org>.
In final testing of RC2, some compatibility issues have been found 
between Tomcat 3.3.1 and the struts-exercise-taglib application as well 
as the tiles-documentation application.

Martin Cooper has been looking into the problems and has found that for 
the struts-exercise-taglibs cookie test, it is the

   <jsp:getProperty name="sess" property="name"/>

expression that is failing.

The <jsp:getProperty> tags earlier on the page succeeded. The only
difference seems to be that the earlier ones all have setters as well as 
getters in the Tomcat CookieFacade class, whereas there is only a getter 
for 'name'. So this actually looks like some kind of JSP/reflection bug, 
not related to Struts. (The <bean:cookie> tag must have worked, because 
we know the <jsp:getProperty> tag is trying to access a cookie!)

Also, the (rather complex) comparison test is killing the JVM when run 
under TC3.

In the Tiles application, servlet exceptions are being noted. One 
example is the extendedDefinitionTag page, but there may be others.

Unless fixes to these problems are immediately forthcoming, I propose 
that we document the issues and release Stuts 1.1 beta 5.

By getting this milestone out to the community, we would have a better 
chance of resolving the remaining issues so that we can go to Struts 
1.1. final as soon as possible

This proposal has my +1.

-Ted.



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


Re: [PLAN] Release Struts RC2 with FileUpload RC1

Posted by Ted Husted <hu...@apache.org>.
Craig R. McClanahan wrote:
> +1 ... thanks to all the committers for pitching in and getting us this
> close to 1.1 final!

I also want to mention that I do appreciate all the work people have put 
into moving most of our core components over to the Commons. While it 
slowed the release of this particular product down, I do believe it is 
helping to accelerate work by the rest of the Java community.

The Java community now has at their disposal production-quality releases 
of packages like the BeanUtils, Collections, Digester, FileUpload, 
Validator, not to mention Lang and Logging, along with many others we 
never dreamed of when the Commons was founded. I'm seeing these packages 
crop up in products all over the net as well as in applications created 
by in-house teams. (Which, after all, is the point of the exercise!)

Bootstrapping the Commons is in itself a much greater accomplishment 
that any release of Struts could ever be. The ASF agrees, and based on 
the success of the Commons has started its own top level project 
(http://commons.apache.org/).

Of course, it would have been nice if we could have moved the packages 
over and managed to ship interim releases too, but hindsight is always 
20:20. =:0)

So, we didn't finish the work on Resources before 1.1, but there is 
always 1.2. In the end, I hope that Struts becomes a true 
component-based framework, showing just one way that all the "cool 
tools" in the Commons can play well together.

-Ted.



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


Re: [PLAN] Release Struts RC2 with FileUpload RC1

Posted by "Craig R. McClanahan" <cr...@apache.org>.

On Fri, 6 Jun 2003, Ted Husted wrote:

> Date: Fri, 06 Jun 2003 09:24:18 -0400
> From: Ted Husted <hu...@apache.org>
> Reply-To: Struts Developers List <st...@jakarta.apache.org>
> To: Struts Developers List <st...@jakarta.apache.org>
> Subject: [PLAN] Release Struts RC2 with FileUpload RC1
>
> I've posted an updated Release Plan to reflect the consensus we reached
> on RC2. I'm going to work on the struts-legacy release first make the
> necessary adjustments to the build. Then, I'll start on the tests
> gauntlet for RC2, so that I can cut the actual release first thing
> tomorrow morning.
>
> Accordingly, if there is no objection, the codebase will freeze at
> midnight tonight.
>

+1 ... thanks to all the committers for pitching in and getting us this
close to 1.1 final!

Craig

> The one non-enchancement issue is
>
> http://issues.apache.org/bugzilla/show_bug.cgi?id=19911
>
> I pinged Cedric, and if nothing else comes up, I'll mark it LATER and
> then reopen it against the nightly build after RC2 ships.
>
> Everything else is marked Enhancement, and so I added that clause to the
> Release Plan.
>
> -Ted.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: struts-dev-help@jakarta.apache.org
>
>

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


Re: [PLAN] Release Struts RC2 with FileUpload RC1

Posted by Ted Husted <hu...@apache.org>.
Thanks, fixed.

Mike Jasnowski wrote:
> Just curious, in the releaes plan under "The plan" it has the following
> line:
> 
> Therefore, the following release plan is proposed for Struts 1.1 Release
> Candidate 1:
> 
> 
> Should this be "Release Candidate 2" ?
> 
> If not, sorry for the noise.
> Mike





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


RE: [PLAN] Release Struts RC2 with FileUpload RC1

Posted by Mike Jasnowski <mj...@bea.com>.
Just curious, in the releaes plan under "The plan" it has the following
line:

Therefore, the following release plan is proposed for Struts 1.1 Release
Candidate 1:


Should this be "Release Candidate 2" ?

If not, sorry for the noise.
Mike

-----Original Message-----
From: Ted Husted [mailto:husted@apache.org]
Sent: Friday, June 06, 2003 9:24 AM
To: Struts Developers List
Subject: [PLAN] Release Struts RC2 with FileUpload RC1


I've posted an updated Release Plan to reflect the consensus we reached
on RC2. I'm going to work on the struts-legacy release first make the
necessary adjustments to the build. Then, I'll start on the tests
gauntlet for RC2, so that I can cut the actual release first thing
tomorrow morning.

Accordingly, if there is no objection, the codebase will freeze at
midnight tonight.

The one non-enchancement issue is

http://issues.apache.org/bugzilla/show_bug.cgi?id=19911

I pinged Cedric, and if nothing else comes up, I'll mark it LATER and
then reopen it against the nightly build after RC2 ships.

Everything else is marked Enhancement, and so I added that clause to the
Release Plan.

-Ted.



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



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