[jira] [Updated] (OPTIQ-353) Comply with release check-list

["Julian Hyde (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OPTIQ-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Hyde updated OPTIQ-353:
------------------------------

    Description: 
Check that our release complies with the incubator release check-list: http://incubator.apache.org/guides/releasemanagement.html#check-list.

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.

  was:Check that our release complies with the incubator release check-list: http://incubator.apache.org/guides/releasemanagement.html#check-list.


> Comply with release check-list
> ------------------------------
>
>                 Key: OPTIQ-353
>                 URL: https://issues.apache.org/jira/browse/OPTIQ-353
>             Project: Optiq
>          Issue Type: Task
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>
> Check that our release complies with the incubator release check-list: http://incubator.apache.org/guides/releasemanagement.html#check-list.
> 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)