Right. I'm trying to look at it from the view of someone coming in and not being familiar with the process.
For example, there's nothing that says that a Jira story must be associated with a fix version, if you don't associate your Jira story with a fix version, there's nothing that stops that fix from being committed, and being part of the eventual release. It's just work that's undocumented. The story will also not get closed, as that's part of the release process. When should I associate a story with a Fix version? If I want the story to go into the next release then do I create the story and add the fix version immediately? Do I wait till the story is resolved? Who should set the fix version, the creator of the story of the person who has taken it up to fix it? Some of this should be self evident to us because we're in the process. But that doesn't mean it shouldn't be written down. - Jason On Thu, Mar 15, 2018, at 11:04 AM, Antonio Sanso wrote: > hi Jason, > > > this is (at least partially) covered in > http://sling.apache.org/documentation/development/release-management.html#update-jira > > > regards > > > antonio > > ________________________________ > From: Jason E Bailey <[email protected]> > Sent: Thursday, March 15, 2018 4:02:08 PM > To: [email protected] > Subject: Re: setting up for a release > > I appreciate the link, for some reason I didn't make the connection. > > There is one part missing , not necessarily from the release but impacts > releases, is the management of JIRA issues and the need to associate a > issues with Fixed versions when a solution is put into place so that > it's properly tied to a release. > > Once I get some time I'll update the Issue Tracking page. > > - Jason > > On Wed, Mar 14, 2018, at 12:26 PM, Bertrand Delacretaz wrote: > > Hi Jason, > > > > On Wed, Mar 14, 2018 at 5:20 PM, Jason E Bailey <[email protected]> wrote: > > > Looking for information on how to set up for a release. What do I need > > > to do in Jira etc.... > > > > http://sling.apache.org/documentation/development/release-management.html > > should have everything - if not let's fix that! > > > > -Bertrand
