Performed some LICENSE and NOTICE cleanup, and created an ASF Release Guidelines document based on feedback on the [VOTE] and [DISCUSS] (plus next two messages) threads.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Added an asf-release.sh script for building the release, which excludes the LICENSE and NOTICE files from the subdirectories, signs and checksums the release, and prompts for the information to fill in the [VOTE] thread template.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The release script looks pretty good to me. I'd rather use git archive to make the zip file, rather than using a working copy & excluding files. Working copies could have other files that aren't noticed (hidden by local git ignore settings). Also there is a "1.0.0" hard coded in the email template.
Beyond that I think the script is good to go, the real test is in its usage.
I would like us to put together a 1.0.1 section in the CHANGES file before we run the script though. It'll be a good exercise even though 1.0.0 was never release (and maybe CHANGES should state that fact too)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Pending vote on allura-dev. Also waiting for https://dist.apache.org/repos/dist/release/allura to work (supposed to be 24hr but is still not working; may need to reopen https://issues.apache.org/jira/browse/INFRA-6660).
allura:cj/6422Performed some LICENSE and NOTICE cleanup, and created an ASF Release Guidelines document based on feedback on the [VOTE] and [DISCUSS] (plus next two messages) threads.
Added an
asf-release.shscript for building the release, which excludes the LICENSE and NOTICE files from the subdirectories, signs and checksums the release, and prompts for the information to fill in the [VOTE] thread template.Making this public to get some reviews on my LICENSE / NOTICE changes and the release script.
Which commits in https://git-wip-us.apache.org/repos/asf?p=incubator-allura.git;a=shortlog;h=refs/heads/cj/6422 exactly are new since last time? (Might want to mention on the non-ticket email thread too)
The release script looks pretty good to me. I'd rather use
git archiveto make the zip file, rather than using a working copy & excluding files. Working copies could have other files that aren't noticed (hidden by local git ignore settings). Also there is a "1.0.0" hard coded in the email template.Beyond that I think the script is good to go, the real test is in its usage.
I would like us to put together a 1.0.1 section in the CHANGES file before we run the script though. It'll be a good exercise even though 1.0.0 was never release (and maybe CHANGES should state that fact too)
Changed release script to use git archive and added change log generation.
allura:cj/6422