...
- Send email to
hcatalog-dev@incubator.apache.org
to notify that you about to branch the tree and ask to hold off any commits till this is finished. - Update
CHANGES.txt
to include the release version and date (use Unreleased for the date if it is unknown) and remove Trunk (unreleased changes). Below is the example of the top of theCHANGES.txt
file after the update:Code Block Apache HCatalog Change Log Release 0.1.0 - Unreleased INCOMPATIBLE CHANGES NEW FEATURES HCAT-1. Upload initial code to HCatalog (gates)
- Edit
src/docs/src/documentation/content/xdocs/site.xml
. In the external reference for api where the link contains the previous version number change this string to the correct version number. - Commit these changes to trunk:
Code Block svn commit -m "Preparing for release X.Y.Z"
- Create a branch for the release series:
Code Block svn copy https://svn.apache.org/repos/asf/incubator/hcatalog/trunk \ https://svn.apache.org/repos/asf/incubator/hcatalog/branches/branch-X.Y -m "Branching for X.Y releases"
- Update
CHANGES.txt
to add back in Trunk (unreleased changes). Top of theCHANGES.txt
should look like this now:Code Block HCatalog Change Log Trunk (unreleased changes) INCOMPATIBLE CHANGES IMPROVEMENTS OPTIMIZATIONS BUG FIXES Release 0.1.1 - Unreleased ....
- Update the default version in
build.xmlproperties
on trunk to X.Y+1.0-dev.. - Update the versions in all of the pom files,
pom.xml, core/pom.xml, hcatalog-pig-adapter/pom.xml, server-extensions/pom.xml, storage-handlers/hbase/pom.xml, webhcat/svr/pom.xml, webhcat/java-client/pom.xml
to X.Y+1.0 - Commit these changes to trunk:
Code Block svn commit -m "Preparing for X.Y+1.0 development"
...