Page History

...

Please refrain from editing descriptions and comments if possible, as edits spam the mailing list and clutter JIRA's "All" display, which is otherwise very useful. Instead, preview descriptions and comments using the preview button (on the right) before posting them. Keep descriptions brief and save more elaborate proposals for comments, since descriptions are included in JIRA's automatically sent messages. If you change your mind, note this in a new comment, rather than editing an older comment. The issue should preserve this history of the discussion.

When committed, the committer will mark the issue as resolved, but not close it. The issue should remain open until a release containing the issue has been released. As closed issues cannot be reopened, this allows people who experience problems with the patch to reopen it. It also provides a clear signal to others whether the issue is available in a public release.

Stay involved

Contributors should join the HCatalog mailing lists. In particular, the commit list (to see changes as they are made), the dev list (to join discussions of changes) and the user list (to help others).

...