Not really an issue JIRA allows a lot of flexibility in the configuration of Versions (I.e. the version strings are free text) so you could easily have "Apex x.y.z" and "Malhar x.y.z" as separate versions under a single JIRA key. It just needs the community managing the JIRA to be careful about ensuring issues are tagged with the correct Affects and Fix Versions as necessary
We've used this workflow for years in the Jena project and not had an issue with it. Of course the community may prefer to have separate JIRA keys as appears to be the case here in which case I see no reason not to allow them that and there are other precedents for that (e.g. Apache Commons) Rob On 11/08/2015 18:03, "Chris Nauroth" <cnaur...@hortonworks.com> wrote: >One thing to consider is that release version numbers are tied to specific >JIRA projects. If the intention is for Apex and Malhar version numbers to >be independent, then using a single JIRA project could introduce some risk >of confusion if an Apex version number accidentally gets applied to a >Malhar issue. It might necessitate prefixing the version numbers with >"apex-" and "malhar-" to differentiate. > >Based on that, I have a slight preference for separate JIRA projects. >However, I don't object to using a single unified JIRA project if others >feel strongly about it. > >--Chris Nauroth > > > > >On 8/11/15, 8:23 AM, "Amol Kekre" <a...@datatorrent.com> wrote: > >>Ted, >>I agree that repo is more critical than jira instance. I am taking up >>your >>suggesstion with folks and should get back soon. >> >>Thks >>Amol >> >>On Tue, Aug 11, 2015 at 3:48 AM, Ted Dunning <ted.dunn...@gmail.com> >>wrote: >> >>> >>> I personally see far less reason for separate JIRA instances than git >>> repos. Having all jiras under APEX seems a good choice. >>> >>> Sent from my iPhone >>> >>> > On Aug 11, 2015, at 2:32, Bertrand Delacretaz >>><bdelacre...@apache.org> >>> wrote: >>> > >>> > As for JIRA, I would apply the same rule, so APX-CORE and APX-MHAR >>>maybe. >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >>> For additional commands, e-mail: general-h...@incubator.apache.org >>> >>> > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >For additional commands, e-mail: general-h...@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
