+1 to Gunnar's suggestion. This is the practice I have been following. I don't know that it is documented anywhere though. Perhaps the "Development Workflow" on the wiki is the place to document this?
-----Original Message----- From: Gunnar Tapper [mailto:[email protected]] Sent: Wednesday, July 6, 2016 11:06 PM To: [email protected] Subject: Re: Trafodion Jira Maintenance Hi Seth, In my opinion, the Jira should be CLOSED once the release has been made available for public usage. Therefore, I recommend that the status is set to FIXED once the pull request has been merged. Others may have other opinions? Thanks, Gunnar On Thu, Jul 7, 2016 at 12:00 AM, Jin, Jian (Seth) <[email protected]> wrote: > When shall we set JIRA status to FIXED? Before or after release? > > Br, > > Seth > > -----Original Message----- > From: Pierre Smits [mailto:[email protected]] > Sent: 2016年7月7日 4:18 > To: [email protected] > Subject: Re: Trafodion Jira Maintenance > > That will help putting a complete set of release notes together for > the release we recently voted on, as well as future releases. > > Best regards, > > Pierre > > On Wednesday, July 6, 2016, Gunnar Tapper <[email protected]> wrote: > > > Hi, > > > > The 2.0 release fixed 250+ jiras. If you have not yet done so, > > please update and close the fixed jiras. > > > > -- > > Thanks, > > > > Gunnar > > *If you think you can you can, if you think you can't you're right.* > > > > > -- > Pierre Smits > > ORRTIZ.COM <http://www.orrtiz.com> > OFBiz based solutions & services > > OFBiz Extensions Marketplace > http://oem.ofbizci.net/oci-2/ > -- Thanks, Gunnar *If you think you can you can, if you think you can't you're right.*
