Amol,

I don't think there's a need to update the proposal for this, it's an 
implementation detail that can be dealt with upon entry. The proposal should be 
treated as immutable while the vote is underway (which is why proposals are 
always attached to the VOTE -- so people know exactly what they are voting on).

In the (seemingly unlikely) event that the vote doesn't pass, the proposal can 
be revisited.

Just an FYI...

-Taylor

> On Aug 14, 2015, at 4:49 PM, Amol Kekre <a...@datatorrent.com> wrote:
> 
> Niall,
> Thanks for following up and resolving the ask. We will remove '_' from the
> keys.
> 
> Thks,
> Amol
> 
> 
> On Fri, Aug 14, 2015 at 1:03 PM, Niall Pemberton <niall.pember...@gmail.com>
> wrote:
> 
>>> On Wed, Aug 12, 2015 at 3:55 AM, Amol Kekre <a...@datatorrent.com> wrote:
>>> 
>>> Niall,
>>> Thanks for catching. I replaced '-' with '_' as per atlassian policy. I
>> am
>>> suspecting that ASF does not allow '_' as none of the project keys have
>>> '_'. I have added a comment that '_' can be removed if that is the
>> policy.
>>> Wiki updated.
>>> 
>> 
>> I asked on the infra list what the JIRA key format was and whether it could
>> be changed to include underscore and got the following response:
>> 
>> "They are all uppercase alpha characters. Sadly it cannot be changed."
>> 
>> Niall
>> 
>> 
>> 
>>> 
>>> Thks,
>>> Amol
>>> 
>>> 
>>> On Tue, Aug 11, 2015 at 7:46 PM, Niall Pemberton <
>>> niall.pember...@gmail.com>
>>> wrote:
>>> 
>>>> On Wed, Aug 12, 2015 at 2:08 AM, Amol Kekre <a...@datatorrent.com>
>>> wrote:
>>>> 
>>>>> 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
>>>>> 
>>>> 
>>>> Hyphens are not allowed as project keys, but underscore is a
>> possibility.
>>>> The default format is only upper case letters - but you'll need to
>> check
>>>> what ASF has configured.
>>>> 
>>>> 
>>>> 
>>> 
>> https://confluence.atlassian.com/display/JIRA/Changing+the+Project+Key+Format
>>>> 
>>>> Niall
>>>> 
>>>> 
>>>> Thks,
>>>>> Amol
>>>>> 
>>>>> 
>>>>> On Tue, Aug 11, 2015 at 1:44 PM, Hitesh Shah <hit...@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 <a...@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 <
>>>>>> 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
>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>> 
>> 

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Reply via email to