i personally have absolute no problem with leaving this version list unsorted - so alternatively we could just remove this step from the documentation.
stefan >-----Original Message----- >From: Julian Sedding [mailto:[email protected]] >Sent: Thursday, December 8, 2016 1:33 PM >To: Sling Developers List >Subject: Re: release management - JIRA versions (was: [jira] [Updated] >(SLING-6376) Improve error message "Could not adapt from <A> to <B> within >the collection") > >> another think i'm never doing but is described there is sorting the >versions in jira manually - this would be too much pain, searching by name >does the job as well. > >I agree this is very painful, as the list is almost endless. Maybe we >could create a bookmarklet to simplify this step? Or archive old >versions routinely, so the list isn't as long? > >Regards >Julian > > >On Thu, Dec 8, 2016 at 1:10 PM, Stefan Seifert <[email protected]> >wrote: >> >>>Thanks for the hint, unfortunately our release process described that >>>creating new versions in JIRA is done after the VOTE was successful >>>(http://sling.staging.apache.org/documentation/development/release- >>>management.html#update-jira). >>>Maybe we should insert an additional step "creating a new version in JIRA >>>X.Y.Z+2" before you do the vote. That way you at least see two unreleased >>>versions in the list in JIRA while the Vote is ongoing. >> >> oh - i always create the new version in JIRA when starting the vote and >close the other. i thinks this is the only thing that makes sense. >> yes, we should update our release prozess here. >> >> another think i'm never doing but is described there is sorting the >versions in jira manually - this would be too much pain, searching by name >does the job as well. >> >> stefan >> >>
