Page History

...

• all items from the JIRA roadmap for the release must be completed or moved to a future release
• ALL human readable files must contain the Apache license header
  • this includes style sheets, test code, and documentation - when in doubt, add a header
  • files that are part of other software packages that are bundled with a release must not contain the header (unless that software is also ASF software) and should be clearly documented as being bundled software
• LICENSE and NOTICE files should be reviewed
• an export from HEAD should result in a directory tree with all files and directories having appropriate permissions
• documentation on how to upgrade from a previous release must be created
  • if appropriate, scripts to help users upgrade should be created (don't forget steps/scripts to upgrade the database schema)
• RELEASE_NOTES file needs to be updated and should contain:
  • release version
  • an intro to VCL
  • a brief description of the aims of VCL
  • a brief roadmap of VCL and how this release fits in to it
  • a list of ways for users to get involved
  • a description of how users can submit issues
• the following disclaimer in a README file:
  Code Block Apache VCL is an effort undergoing incubation at the Apache Software Foundation (ASF), sponsored by the Apache Incubator PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.

• the README file must also contain all dependencies (this includes PHP, Perl, MySQL versions in addition to perl and php modules, dojo, etc.) for running VCL, any changes in dependencies since the last release must be listed in the CHANGLOG file
• release manager's GPG signing key must be in KEYS file in toplevel directory
• a release/download page needs to be created for the specific release containing:
  • link to release artifact (link to a mirror)
  • link to signatures and checksums (link directly to apache.org)
  • steps explaining how to verify artifact using signatures and checksums
  • either a link to release notes or contain them inline
  • either a link to a change log or contain it inline
• a decision needs to be made determining which, if any, previously released artifacts should be removed from the main distribution site after this release is completed

...