aurora-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <>
Subject [jira] [Commented] (AURORA-278) Review Incubator release check list
Date Tue, 29 Apr 2014 11:01:18 GMT


Hudson commented on AURORA-278:

FAILURE: Integrated in Aurora #337 (See [])

> Review Incubator release check list
> -----------------------------------
>                 Key: AURORA-278
>                 URL:
>             Project: Aurora
>          Issue Type: Task
>            Reporter: Dave Lester
>            Assignee: Jake Farrell
>             Fix For: 0.5.0
> Prior to a release in the incubator, we must comply with the [release 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
> 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

View raw message