Page History

...

1. Add an entry in CHANGES.txt, at the beginning of the appropriate section (this is so that most recent patches appear first in CHANGES.txt). This should include the JIRA issue id, the name of the contributor, and the name of the committer (if different from the contributor).
2. Include the JIRA issue id in the commit message, along with a short description of the change and the name of the contributor if it is not you. Be sure to get the issue id right, as this causes JIRA to link to the change in Subversion (use the issue's "All" tab to see these).
3. Resolve the issue as fixed, thanking the contributor. Always set the "Fix Version" at this point, but please only set a single fix version, the earliest release in which the change will appear. Do not close the issue.

Website Changes

In addition to code changes, changes to the site documentation might be necessary. If so, please, follow the HCatalog uses svnpubsub for managing the website (setup in INFRA-5862). To update the website, follow these steps:

• Install forrest - The 0.9 tar.gz version from the archive is confirmed to be working for our build.
• Checkout site documentation: svn co https://svn.apache.org/repos/asf/incubator/hcatalog/site/
• Edit files in author/src/documentation/content/xdocs. See http://forrest.apache.org/ for documentation.
• Build the site: ant -Dforrest.home=<forresthome> where forresthome is the directory you installed forrest in.
• Inspect what's in build/site with your browser
• Once you are happy with the outcome, commit your changes: . svnpubsub will update the public website immediately, so only commit when you are ready to publish the public site.

  Code Block
  svn add ... svn commit -m "blah blah"

  Upload the changes to the documentation site: (The changes will appear an 1 hour after the update.)

  Code Block
  ssh people.apache.org cd /www/incubator.apache.org/content/hcatalog svn up