+1 to Alexander's suggestion. I don't know where to put stuff like that, but once we have one we should link to it from our new CIO instructions page.
On Wed, Nov 7, 2018 at 2:59 PM Alexander Murmann <amurm...@pivotal.io> wrote: > Kirk, I think most of us are in agreement that it works as you are > describing. The notes for the release manager also assume that we are all > following this process. > However, I also was unable to find something obvious in the wiki. The > closest is the "JIRA Guidelines" page > <https://cwiki.apache.org/confluence/display/GEODE/JIRA+Guidelines>. That > page is pretty implicit about it by just mentioning that you should set the > version as part of completing a story. > > It might be nice to have a paragraph somewhere that explains how to file a > JIRA ticket. Where would be a good place(s) that would actually be seen? > > On Wed, Nov 7, 2018 at 2:52 PM Kirk Lund <kl...@apache.org> wrote: > > > Does anyone have a link to a wiki page describing our use of "Fix > > Version/s" on Geode Jira tickets? > > > > My understanding is that when we file a ticket we leave it blank. Then > when > > we commit a fix to develop we change the Jira ticket to "Resolved" and > fill > > in the "Fix Version/s" with the upcoming release (ex: 1.8.0). Then when > we > > release 1.8.0, all tickets that are in "Resolved" with "Fix Version/s" of > > 1.8.0 will be changed to "Closed" with "Fix Version/s" 1.8.0. > > > > Some of our community are filing tickets with "Fix Version/s" pre-filled > > with the version that we hope to fix the ticket in. > > > > Anyone have a definitive answer for this process? > > > > Thanks, > > Kirk > > >
