Mailing-List: contact general-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of lutter@redhat.com designates
 209.132.183.28 as permitted sender)
Subject: Re: [VOTE] release deltacloud 0.3.0
From: David Lutterkort <lutter@redhat.com>
To: general@incubator.apache.org
In-Reply-To: <BANLkTikZeCNJUYVayqTj6nG1uSBYPM8LVQ@mail.gmail.com>
References: <1302193499.19886.74.camel@avon.watzmann.net>
	 <BANLkTikZeCNJUYVayqTj6nG1uSBYPM8LVQ@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-15"
Organization: Red Hat Inc
Date: Fri, 08 Apr 2011 17:03:45 -0700
Message-ID: <1302307425.14176.20.camel@avon.watzmann.net>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit

Hi,

thanks for the review; I've addressed most of the issues you found. I
will finish that on Monday and spin RC2.

For my education: is there a good checklist for what needs to be in a
release ? It seems that the requirements are fairly well distributed
across the Apache website.

Some comments below:

On Thu, 2011-04-07 at 18:17 +0100, sebb wrote:
> On 7 April 2011 17:24, David Lutterkort <lutter@redhat.com> wrote:
> > Hi all,
> >
> > I just uploaded a release candidate for Deltacloud 0.3.0. The rc is
> > available from http://people.apache.org/~lutter/deltacloud/0.3.0/rc1/
> >
> > Please vote on the release candidate by Monday, 2011-04-10 8:00 PDT
> 
> Where is the SVN tag for the release?

Only had tag in my local git - pushed that as SVN tag release-0.3.0-rc1

> and the KEYS file?

http://www.apache.org/dist/incubator/deltacloud/KEYS

> The tar.gz files don't contain a NOTICE file 

Moving that from trunk/ to trunk/client/ and trunk/server/ so it gets
picked up by the release scripts

> and they don't contain a LICENSE file - the COPYING file won't do as a
> substitute.

Renamed the files.

> There's no DISCLAIMER. 

Added one.

> The website also needs a disclaimer and a more
> obvious notification that it is an Incubator project.

Will do that on Monday.

> The hashes need to be stored as separate files, one for each archive
> (as for the sigs in the .asc files).

Changed my release script.

> Many of the source files contain "Copyright (C) 2009-2011  Red Hat,
> Inc." or other copyright attributions.
> 
> AFAIK, you need to ask the owner for permission to remove them, or at
> least to move them to the NOTICE file.
> 
> There are some other files with non AL headers; these may also need to
> be attributed in the NOTICE file.

I find this extremely confusing - why remove the copyright attribution ?
Isn't it clearer if each file states who holds copyright in it ?

In any event, I assume I can move the copyright notices for the files
that were part of the initial grant, and that come from contributors;
there's also a handful of files that we use under the MIT license - can
I leave the copyright attribution in them ?

Also, it seems to me that the boilerplate text of the NOTICE file is
incorrect since it states 'Copyright YYYY The Apache Software
Foundation' but the contributor license agreement does not actually
assign copyright to the ASF (which would be impossible in some
jurisdictions anyway) - what exactly does the NOTICE file accomplish ?

The FAQ [1] does not really have an answer for this, as it only refers
to a previously used header that incorrectly claimed ASF Copyright.

David

[1] http://apache.org/legal/src-headers.html#notice


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org