[ http://issues.apache.org/jira/browse/JDO-363?page=comments#action_12414096 ]
Craig Russell commented on JDO-363: ----------------------------------- Based on feedback we got from other Apache projects, I propose we use the following workflow for our JIRA issues. Open<->Resolved->Closed When the engineer has fixed an issue, she sets the issue to resolved. The submitter can reset it to open if there is some problem with it. When the release in which the issue is fixed ships, the issue is set to closed. If the same issue comes up again after release, another JIRA is opened, referring to the original issue. This accommodates fixes being backported (if ever necessary) to dot releases after the original release ships. This workflow can be elaborated to add more steps between open and resolved but for now that seems unnecessary. With this change, we can use JIRA features to track changes by release and automatically generate release notes. > Add links to site to JIRA filters for open and closed issues by release > ----------------------------------------------------------------------- > > Key: JDO-363 > URL: http://issues.apache.org/jira/browse/JDO-363 > Project: JDO > Type: Task > Components: site and infrastructure > Reporter: Michelle Caisse > Assignee: Michelle Caisse > Attachments: bugtrackiing.html > > Add links from the JDO web site to the JIRA page to do calculations of the > open and closed issues by release. Must first ake sure that all JIRA issues > have a "resolved in release" entry. Might have to reopen some JIRA issues > just to add this info. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
