Alright, first round of updates is done (and sorry for all the spam).  If I 
mislabeled something please let me know or just correct it.  Thanks!

Some ideas to improve our JIRA hygiene:

1) Create the version tag for the next release before we fix All The Bugs :-)
2) Set a Fix Version when you resolve a bug.
3) Only set one Fix Version unless it is really being fixed on multiple 
releases.

Anthony

> On Jan 7, 2016, at 5:09 PM, Anthony Baker <[email protected]> wrote:
> 
> Good point, I’ll keep an eye out for those.
> 
> Anthony
> 
>> On Jan 6, 2016, at 9:11 PM, Nitin Lamba <[email protected]> wrote:
>> 
>> This would be true in general unless a JIRA has been resolved but the 
>> feature is still in a branch. Long-running branches and sub-task JIRAs would 
>> probably exhibit this behavior.
>> 
>> I'll check JIRA tomorrow to see if I can find any counter examples.
>> 
>> Thanks,
>> Nitin
>> 
>> ________________________________________
>> From: Anthony Baker <[email protected]>
>> Sent: Wednesday, January 6, 2016 8:54 PM
>> To: [email protected]
>> Subject: Assigning JIRA fix version
>> 
>> Looking at the JIRA roadmap [1] [2] we have:
>> 
>> 12 issues fixed in 1.0.0-alpha1
>> 78 issues fixed in 1.0.0-incubating
>> 276 issues with empty Fix version
>> 
>> I suspect we want all the resolved issues to show up in the changelog for 
>> 1.0.0-alpha1.  This means we need to correct the Fix version field.  Make 
>> sense?
>> 
>> Anthony
>> 
>> [1] 
>> https://issues.apache.org/jira/browse/GEODE/?selectedTab=com.atlassian.jira.jira-projects-plugin:roadmap-panel
>> [2] 
>> https://issues.apache.org/jira/browse/GEODE-135?jql=project%20%3D%20GEODE%20AND%20status%20in%20(Resolved%2C%20Closed)%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20%3D%20EMPTY%20ORDER%20BY%20priority%20DESC
>> 
> 

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail

Reply via email to