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 (asf.osuosl.org: domain of ted.husted@gmail.com designates
 64.233.162.200 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=BDk1EoQjFfT+lz93NetXWnJpjiz5jA+shIPAKH9F0fx8T0ih3hOMBG6Ll0wCtJIHFH3RNmUBaEWFajV2o/uSyglnClS1B3JmbFgY3H2KBSgIvCA+r1TSj3pl/mpUcaq0rlYKwiXjfRyTSU83YZkRPmHTYNV2GdMKiI7EBf2RBH4=
Message-ID: <8b3ce3790511260808p1fddd839lad7a4abf953ac4f8@mail.gmail.com>
Date: Sat, 26 Nov 2005 11:08:29 -0500
From: Ted Husted <ted.husted@gmail.com>
Reply-To: husted@apache.org
To: Struts Developers List <dev@struts.apache.org>
Subject: Re: [ANNOUNCEMENT][shale] Struts Shale 1.0.0 Release Candidate 1
 Available
In-Reply-To: <f8b39ace0511251705u67848c58v313583e375e421d6@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <f8b39ace0511251705u67848c58v313583e375e421d6@mail.gmail.com>

I'm not sure if I'm comfortable with going back to using the "release
candidate" nomenclature. If we want to release a distribution, we
should vote on the plan, and release a distribution. If that
distribution needs work to make the GA grade, then we should just
release the next milestone. We worked very hard to develop a canonical
release process, which I believe is serving us well.

If we anticipate that a 1.0.0 release will be soon followed by a
1.0.1, then I would suggest setting up a release plan for the
subsequent release too. There's no reason why we can't use the
canonical process to release early and release often. Since the
release process is already streamlined, I don't think that hosting
"release candidates" and "limited time distributions" on top of the
nightly builds is a good idea.

I am also very uncomforable with us rolling any type of distribution
and announcing it to the *user* list, without (as far as I can tell)
any prior discussion on dev@. There are several Shale committers in
our community, and I believe everyone involved should be given the
express opportunity to chime-in before we do anything like this.

-Ted.


On 11/25/05, Craig McClanahan <craigmcc@apache.org> wrote:
> In preparation for the initial milestone release of Struts Shale 1.0.0, a
> release candidate has been made available at:
>
>     http://people.apache.org/~craigmcc/struts-shale-1.0.0-rc1/<http://peo=
ple.apache.org/craigmcc/struts-shale-1.0.0-rc1/>
> (TIME LIMITED URL)
>
> including both tar.gz and zip artifacts (containing both binary and sourc=
e),
> and an extracted copy of the release notes.  Please help ensure the corre=
ct
> assembly and quality of this release by downloading it, and ensuring that=
 it
> works correctly for you.
>
> Struts Shale 1.0.0 is intended to be an initial test build of the new
> framework (see <http://struts.apache.org/struts-shale/> for more
> information).  It is not intended that this release be subsequently voted=
 on
> as candidate for General Availability.  Instead, it should be considered =
an
> alpha milestone, released in order to provide opportunities for wider
> testing.  Expect to see subsequent point releases of increasing quality a=
nd
> functionality.
>
> Even though this is considered a test build, various developer APIs shoul=
d
> be considered at a more stable (in terms of assurances of backwards
> compatibility in future releases) point than might otherwise be expected =
of
> an alpha release.  Please see the following web page for more details:
>
>     http://struts.apache.org/struts-shale/api-stability.html
>
> Feedback welcome!
>
> Craig McClanahan
>

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