On 5/7/06, Paul Benedict <[EMAIL PROTECTED]> wrote:

#1) The Development milestones haven't been updated since 1.2.6.
If you don't care about documenting anything else in 1.2.x, at least
split off 1.3.x into 1.3.3 and 1.3.x, so that the notes are official.
There's a couple of "TODO" items still listed there :)

#2) Milestone page links to "Struts Classic Release Plan 1.3.0" which
I think is no longer a relevant proposal, as it is under the Relevant
Proposal section. We've consolidated all those libraries back into
one numbered version, haven't we?

I think Don worked on these already (after that snapshot).  Does this
look better?
  http://struts.apache.org/struts-action/milestones.html

#3) Consider listing links to the latest of previous GA releases
on the download page,

The download page is part of the top-level Struts site, so this can be
addressed separately from 1.3.3.

#4a) Why do the Table of Contents for the User Guide
list out the release notes for all 1.1 version? Looks a bit
odd. I'd either remove them or add links to the other
versions. I'd prefer the latter.
#4b) Page header is for 1.3.2.
#4c) Page title is 1.3.1.

I thought we were going to accumulate release notes for 1.3 until we
hit GA.  IMO we shouldn't have a "release notes" page for 1.3.1, which
was only a test build, nor should we refer to it on the 1.3.2 page as
"Release Notes (since 1.3.1)".

I'm going to drop that page and go from1.2.9 to 1.3.3, but it likely
will not be complete.  Not everything is marked 'fixed' in JIRA with
the correct release number.  If anyone would like to go through JIRA
tickets and figure out which version they belong to, that would be
great.

#5) 40M is a hefty download. ...I hope there is a "lib" only version release 
too.

Good suggestion.  I opened STR-2863 for this.  As long as the assembly
plugin cooperates, I think it can be done for 1.3.3.

Thanks for taking the time to review the snapshot!

--
Wendy

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to