Hey all - This was basically me using jira wrong. I was closing issues that were resolved, which isn't the right thing to do with this project.
Alan updated the hcat wiki template to the "documentation theme", which shows the left sidebar. Using pig as an example, I created a "Developer Documentation" section, and moved the how to contribute/commit/release pages there, which are hopefully easier to find. I also updated the JIRAGuidelines<https://cwiki.apache.org/confluence/display/HCATALOG/HowToContribute#HowToContribute-JIRAGuidelines> section to include this note about not closing issue. Thanks for cluing me into the correct process for this project! --travis On Mon, Mar 26, 2012 at 10:46 AM, Alan Gates <[email protected]> wrote: > Some questions have come up recently on how our JIRA workflow. So I > wanted to send a note to clarify it. > > When a patch is checked in for a JIRA we mark it resolved, but we don't > close it. A JIRA is marked closed once a release containing the fix is > made. > > There's a couple of reasons for this. One, once closed they can't be > re-opened, so it's good to leave them in the resolved state for a while to > give people a chance to re-open in case there are issues with the > resolution. Two, it gives a distinction to users that JIRAs have been > resolved but are not yet available in a public release. Once they are > closed, users know they can get their hands on the fix. > > Alan.
