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 01:08:45 GMT
oh! We preferred that during our discussion. Somehow we thought there was a
limit. I have changed it to full names (APEX-CORE, APEX-MALHAR). If there
is a limit we can reduce the number of chars later. wiki is updated.

https://wiki.apache.org/incubator/ApexProposal

Thks,
Amol


On Tue, Aug 11, 2015 at 1:44 PM, Hitesh Shah <hitesh@apache.org> wrote:

> If there isn’t a char limit on project names in JIRA, wouldn’t it just be
> better to use “APEX-CORE” and “APEX-MALHAR” to match the actual project
> names, repos, etc?
>
> thanks
> — Hitesh
>
> On Aug 11, 2015, at 1:25 PM, Amol Kekre <amol@datatorrent.com> wrote:
>
> > Chris,
> > Thanks for articulating what I was going to respond with after talking to
> > folks here. We indeed see versions for Malhar and Apex differing. We
> expect
> > Malhar versions to change much more rapidly than Apex.
> >
> > Ted,
> > We discussed the impact of single jira on versioning.  For example we
> > expect Malhar X.0.0 to happen much earlier than Apex X.0.0. There was
> > discomfort in naming versions with prefix. The consensus was to have
> > version numbers convey stuff. If folks don't have strong opinion on two
> > jiras, we would prefer to use two jiras. We have taken up Bertrand's
> scope
> > naming and changed the names of jira projects as follows
> >
> > APX-CORE
> > APX-MLHR
> >
> > I have changed the wiki to reflect the above as jira project names.
> >
> > Thks,
> > Amol
> >
> >
> > On Tue, Aug 11, 2015 at 10:03 AM, 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