You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by ant elder <an...@gmail.com> on 2009/05/12 13:06:44 UTC

Re: Release process

On Wed, Apr 29, 2009 at 8:07 AM, ant elder <an...@gmail.com> wrote:
> Just a heads up on a discussion thats been going on for a while on
> legal-discuss@ about how ASF releases should be done. Tuscany may need
> to modify the release process if whats being said is confirmed as
> policy.
>
> See: http://apache.markmail.org/message/3odlybipss4wnczl
>
>   ...ant
>

For those that didn't follow all that discussion the ASF release FAQ
has now been updated, see:
http://www.apache.org/dev/release.html#what-must-every-release-contain

Two things of note are:

"Every ASF release must contain a source package, which must be
sufficient for a user to build and test the release provided they have
access to the appropriate platform and tools."

and

"that package together with its signature must be tested prior to
voting +1 for release"

We have on occasion had Tuscany releases where there is problem with
building the src distribution, its not clear if "must be tested prior
to voting +1" implies it must build perfectly to be released or if
thats ok as long as we've noted any issues.

The "must contain a source package sufficient for a user to build"
appears to say that the way we release the maven plugins is not
allowed because although it include a -src jar you can't actually use
that src jar to build the plugin.

   ...ant