In my experience, the only difficult part of a release is catching up the release notes. The rest is just mechanics. I'll setup a release notes page for Struts 1.36, and if someone wants to bring it up to date, I'll take care of the rest.
-Ted. On 11/26/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:
On 11/26/06, Ted Husted <[EMAIL PROTECTED]> wrote: > My best suggestion would be to tag and roll a 1.3.6 build now, before > getting into a new line of development. Creating a branch would then > be less important. I think a 1.3.6 release goes in the 'would be nice' column. There were a few fixes, etc., but nothing earth shattering. I'd hate to divert the energy that's currently going into development, over to getting through our release process. So, I'd say tag the trunk as BEFORE_I18N, and carry on. We can always branch from that tag if we need to do another 1.3.x release. I just don't see that happening unless someone shows up with a serious issue. -- Wendy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
