incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Amol Kekre <a...@datatorrent.com>
Subject Re: [DISCUSS] Apex Incubation Proposal
Date Wed, 12 Aug 2015 16:29:12 GMT
Rod,
We did consider prefixed versions. We also understand and agree that
technically prefix works. There is discomfort among us with regards to
using prefixes. Based on community discussions, I prefer to keep the ask
for separate jiras. If during incubation approval, this becomes a blocker,
we will reconsider the ask for separate jiras.

Thks,
Amol


On Wed, Aug 12, 2015 at 2:15 AM, Rob Vesse <rvesse@dotnetrdf.org> wrote:

> 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" <cnauroth@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" <amol@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.dunning@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
> >>><bdelacretaz@apache.org>
> >>> wrote:
> >>> >
> >>> > As for JIRA, I would apply the same rule, so APX-CORE and APX-MHAR
> >>>maybe.
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >>> For additional commands, e-mail: general-help@incubator.apache.org
> >>>
> >>>
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >For additional commands, e-mail: general-help@incubator.apache.org
> >
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message