[jira] [Comment Edited] (AURORA-278) Review Incubator release check list

["Kevin Sweeney (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AURORA-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13942204#comment-13942204 ] 

Kevin Sweeney edited comment on AURORA-278 at 3/20/14 8:00 PM:
---------------------------------------------------------------

One question - ideally we'll support publishing Python sdists to PyPI (so components can be pip installed/pex assembled) and jars + source jars to Maven. Is the plan to create one tarball snapshot of a git tag and call that the RC or will these derived artifacts be included as well?


was (Author: ksweeney):
One question - ideally we'll support publishing to PyPI and 

> Review Incubator release check list
> -----------------------------------
>
>                 Key: AURORA-278
>                 URL: https://issues.apache.org/jira/browse/AURORA-278
>             Project: Aurora
>          Issue Type: Task
>            Reporter: Dave Lester
>            Assignee: Jake Farrell
>
> Prior to a release in the incubator, we must comply with the [release check list|http://incubator.apache.org/guides/releasemanagement.html#check-list]. This ticket is to review the list and check whether there are additional tasks that must be completed in order to be ready for a release.
> 1.1 Checksums and PGP signatures are valid.
> See the Release Signing dev documentation.
> 2.1 Build is successful including automated tests.
> The expanded source archive is expected to build and pass tests.
> 3.1 DISCLAIMER is correct, filenames include "incubating".
> See the Podling Branding Guide.
> 3.2 Top-level LICENSE and NOTICE are correct for each distribution.
> See the Licensing How-To, plus various pages under Legal Affairs.
> 3.3 All source files have license headers where appropriate.
> See the ASF Source Header and Copyright Notice Policy.
> 3.4 The provenance of all source files is clear (ASF or software grants).
> See the IP clearance section of the Mentor's guide, as well as the Releases section of the Incubator's policy page.
> 3.5 Dependencies licenses are ok as per http://apache.org/legal/
> See ASF Legal Previously Asked Questions.
> 3.6 Release consists of source code only, no binaries.
> Each Apache release must contain a source package. This package may not contain compiled components (such as "jar" files) because compiled components are not open source, even if they were built from open source.



--
This message was sent by Atlassian JIRA
(v6.2#6252)