That would mean just adding it as a version, there aren't two different lists for affects vs fixes. If we added it to affectsVersions we are adding it to fixVersions. So if we started a trend of creating a 1.9 Alpha, 1.9 Beta, 1.9 Beta 2, 1.9 RC, 1.9 RC1, etc, our version dropdown becomes very cumbersome. Just picking OpenMRS 1.9 as the fixVersion has two added benefits: 1) Five less versions listed with every release and 2) queries on how to find tickets needing to be fixed for a release are just for OpenMRS 1.9 instead of all affects/fixVersions.
Ben On Tue, Nov 15, 2011 at 9:10 AM, Michael Seaton <[email protected]> wrote: > 1.9 Alpha has been released though. We could add a “1.9 Alpha” to the > affects versions.**** > > ** ** > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of *Ben Wolfe > *Sent:* Tuesday, November 15, 2011 8:52 AM > > *To:* [email protected] > *Subject:* Re: [OPENMRS-DEV] 1.9 alpha version in JIRA**** > > ** ** > > Is it possible to have those be separate lists? I only see one. For > something in the fixVersion to be in the affectsVersion it has to be > RELEASED. And OpenMRS 1.9 has not been. However, putting a fixVersion of > 1.9 will force us to look at it before 1.9 beta is released. > > Ben**** > > On Tue, Nov 15, 2011 at 8:28 AM, Michael Seaton <[email protected]> wrote:** > ** > > Hi Ben,**** > > **** > > My point was that the granular versions are what currently exist, and > there is not generic version for “OpenMRS 1.9”. I’m referring to the > “Affects Versions” here, not the “Fix Version”.**** > > **** > > Mike**** > > **** > > *From:* [email protected] [mailto:[email protected]] *On Behalf Of *Ben Wolfe > *Sent:* Tuesday, November 15, 2011 5:48 AM > *To:* [email protected] > *Subject:* Re: [OPENMRS-DEV] 1.9 alpha version in JIRA**** > > **** > > We haven't gotten into that granularity in the past. Just adding it to > OpenMRS 1.9 should be sufficient. > > I think we already have too many versions: > https://tickets.openmrs.org/browse/TRUNK?selectedTab=com.atlassian.jira.plugin.system.project:versions-panel&subset=-1 > For the sprint jira and grasshopper pages to work well we have to use a > fixVersion for the tickets. Anyone opposed to clearing out the > fixVersions? If anyone is desperate to know the history of a ticket we can > automatically add a tag to the ticket for that sprint before the fixVersion > is dropped. > > Ben**** > > On Thu, Nov 10, 2011 at 2:29 PM, Michael Seaton <[email protected]> wrote:** > ** > > Hi all, > > Can someone please add OpenMRS 1.9 Alpha to the available "Affects > Versions" in JIRA? I just entered 2 tickets (TRUNK-2849, TRUNK-2850) while > running against the alpha, and marked them as "1.9 RoadMap Sprint 3" for > lack of a better option. > > Thanks, > Mike > > _________________________________________ > > To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to > [email protected] with "SIGNOFF openmrs-devel-l" in the body > (not the subject) of your e-mail. > > [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]**** > > **** > ------------------------------ > > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list > **** > ------------------------------ > > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list > **** > > ** ** > ------------------------------ > > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list > **** > ------------------------------ > Click here to > unsubscribe<[email protected]?body=SIGNOFF%20openmrs-devel-l>from > OpenMRS Developers' mailing list > _________________________________________ To unsubscribe from OpenMRS Developers' mailing list, send an e-mail to [email protected] with "SIGNOFF openmrs-devel-l" in the body (not the subject) of your e-mail. [mailto:[email protected]?body=SIGNOFF%20openmrs-devel-l]
