+1

-----Original Message-----
From: Ted Husted [mailto:[EMAIL PROTECTED] 
Sent: Saturday, February 11, 2006 9:56 AM
To: Struts Developers List
Subject: Re: [VOTE] Confirm the Struts Action Library 1.3.0 release plan

OK, we're back down to two patches that could be applied this weekend.

* http://wiki.apache.org/struts/StrutsClassicRelease130

After resolving these items, I'd like to tag and roll the 1.3.0
release on Monday Feburary 13.

There would be a 1.3.0 release for each of the seven dwarfs, and a
"Library" ZIP file with just the JARS utilized by all seven. (Except
the Servlet and JSTL JARs, unless we can redistribute these too.)

Again, this is not a vote on the quality of the release, only whether
to tag the trunk with the marker STRUTS_1_3_0.

-Ted.


On 11/21/05, Ted Husted <[EMAIL PROTECTED]> wrote:
> There are two significant items left on the Struts Action Library
> 1.3.0 (aka Struts Classic) release plan before we would tag and roll
> it. One is renaming struts-action to struts-core, and the other are
> minor changes to the documentation.
>
> * http://wiki.apache.org/struts/StrutsClassicRelease130
>
> At this time, I would ask the PMC, committers, and other interested
> parties to review the plan and the state of the repository. Please
> indicate your opinion on the plan in the usual style: +1, +0, or -1,
> along with any appropriate comments.
>
> Note this this is not a vote on the quality of the intended release,
> but on the release plan.
>
> Given a positive result, it would be our intention to roll the release
> on Thursday or Friday, assuming we rename the struts-core folder on
> Wednesday.
>
> As stated in the plan, this release is intended as a test of the new
> infrastructure, and other releases in the 1.3.x series are expected.
>
> -Ted.

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


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

Reply via email to