Mailing-List: contact dev-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Developers List" <dev@struts.apache.org>
Received-SPF: pass (athena.apache.org: domain of ted.husted@gmail.com
 designates 209.85.198.188 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=X8v5NZ/ZUTRBe1QXoams/oc8F7gOWdz9+OkfK6LB2/eGmtrZXsUw0Ix9VlFZmwAZeVcXiZm/mP78R1kOZXn+a9O2nsl/8awEXczokdJFnG5Yyg2GAdbYU8HPw1IyH8lrGkFZ6WUFjLQXHI7Hrivzr/Xg3TtgrbqOkMyIbXzGIn0=
Message-ID: <8b3ce3790708140948h3b439c89g1aaf8f5ea56a619e@mail.gmail.com>
Date: Tue, 14 Aug 2007 12:48:19 -0400
From: "Ted Husted" <husted@apache.org>
Sender: ted.husted@gmail.com
To: "Struts Developers List" <dev@struts.apache.org>, james@jamesholmes.com
Subject: Re: [s2] 2.0.10 release - when?
In-Reply-To: <8b3ce3790708140941q5516740ak2b395e8c39944ece@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <32506.1187097639@jamesholmes.com>
	 <8b3ce3790708140941q5516740ak2b395e8c39944ece@mail.gmail.com>

The other thing that might help speed up the process would be to
follow up on the Selenium tests that Martin Gilday started

* http://www.nabble.com/Release-process-and-release-Maven-plugin-%28WAS%3A-Re%3A-Voting-Process-%28was-Re%3A-Struts-2.0.9-release-%28WAS%3A-Re%3A-S2-security-fix-release-planning-%28XWork-2.0.4-is-out%29%29%29%29-tf4164719.html#a11934860

Actually testing the Showcase UI is a *huge* time sink.

-T.

On 8/14/07, Ted Husted <husted@apache.org> wrote:
> The best way to put us in a position of regular releases is to attend
> to the JIRA tickets, update the release notes, and test the
> applications as often as possible. Any committer can do that as time
> allows, without worrying about rolling a distribution.
>
> It's also not necessary for there to be a single release manager. In
> the past, we've often had one individual run point on the tickets,
> notes, and testing, and then have another roll the final distribution.
> In my experience, at least half of the work has nothing to do with
> rolling the distribution, but just getting the tickets, notes, and
> apps to the point where we can roll the distribution.
>
> If someone is about ready to clear the decks for a 2.0.10 build, then
> rushing out a 2.0.9.1 doesn't seem useful, since it would be
> superseded by 2.0.10 anyway. But, if it helps, I would be happy to
> roll either version at any time, if the tickets, notes, and testing
> are otherwise done.
>
> On 8/14/07, James Holmes <james@jamesholmes.com> wrote:
> > Since the 2.0.X releases are small point releases, I'm all for releasing 2.0.10
> > soon. I'd like to see a regular schedule for these releases so we can keep fixing
> > the minor issues and getting these fixes out to the users. This will help Struts
> > 2 attract new users. It seems 2.1 is still a ways out (although I'd like to see
> > us put some scope around that and make a rough estimate of a goal when we'd like
> > to get it out).
> >
> > My vote is to release 2.0.10 with the WW-2107 security fix instead of doing a
> > special security fix release. I think we can wait the normal 72 hours that a
> > "regular" release requires.
> >
> > Thoughts?
> >
> > That said, we need a release manager. I'm happy to work on bugs, but don't have
> > time to pour into learning all of the release steps and setting up the required
> > infrastructure on my machine right now.
> >
> > James

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