[
https://issues.apache.org/jira/browse/AURORA-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13985045#comment-13985045
]
Hudson commented on AURORA-278:
-------------------------------
SUCCESS: Integrated in Aurora #339 (See
[https://builds.apache.org/job/Aurora/339/])
AURORA-278: Review Incubator release checklist - missing license headers
(jfarrell: rev 892852327aa31b80c1972ee6069c13c5666555d3)
* src/main/python/apache/thermos/observer/http/assets/observer.js
* LICENSE
* src/main/python/apache/thermos/observer/http/assets/jquery.pailer.js
* src/test/python/apache/aurora/common/test_shellify.py
* src/main/python/apache/aurora/common/shellify.py
* src/main/resources/org/apache/aurora/scheduler/http/ui/js/app.js
* src/main/resources/org/apache/aurora/scheduler/http/ui/js/filters.js
* src/main/resources/org/apache/aurora/scheduler/http/ui/js/directives.js
* src/main/resources/org/apache/aurora/scheduler/http/ui/js/services.js
* examples/vagrant/test_tutorial.sh
* src/main/resources/org/apache/aurora/scheduler/http/ui/js/controllers.js
> 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
> Fix For: 0.5.0
>
>
> 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)
