Versions Compared

Old Version 6

changes.mady.by.user Benjamin Reed

Saved on

compared with

New Version 7

changes.mady.by.user Chris Nauroth

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. make sure the code is up-to-date
  2. apply the patch
  3. run the tests are your machine as a final check. (seems redundant, but sometimes issues pop up.)
  4. edit the CHANGES.TXT file and put the jiras that correspond to the patch in the appropriate section. add the Jira number. description (contributor via committer). a convention has emerged of using the committers id for brevity, but using the full names of non-committers.
  5. If the patch includes documentation changes, then regenerate the rendered docs by running "ant -Dforrest.home=<path to Forrest> clean docs".  Modifications should now be shown under the docs folder.  However, DO NOT commit changes in docs/releasenotes.html or docs/releasenotes.pdf.  Release notes are handled separately as a release management activity, as documented here: HowToRelease .
  6. svn commit the changes
  7. resolve (make sure you "resolve" and not "close".) the jiras that correspond to the patch and put the commit message (that one that has the new revision number) in the resolution comment field.

...