+1
On Feb 14, 2013, at 2:20 PM, Chip Childers <[email protected]> wrote:

> On Thu, Feb 14, 2013 at 11:14:12AM -0800, Min Chen wrote:
>> That may be possible, but we don't need to restrict to only one component
>> in the tag. It is just for quickly filtering emails.
> 
> Sorry, but I think I disagree with this.  I'd rather just have sensible
> subject lines.  Too much tagging is going to be impossible to enforce,
> and frankly seems too complicated to figure out what to do as an email
> author.
> 
>> 
>> Thanks
>> -min
>> 
>> On 2/14/13 11:11 AM, "Chip Childers" <[email protected]> wrote:
>> 
>>> On Thu, Feb 14, 2013 at 11:09:00AM -0800, Min Chen wrote:
>>>> I may prefer to have JIRA bug components rather than bug id in the
>>>> subject. With Components, we can easily figure out what area this
>>>> discussion is about.
>>> 
>>> But aren't many features going to cross the components?  I.e.: UI, API
>>> and plugin changes?
>>> 
>>>> 
>>>> Thanks
>>>> -min
>>>> 
>>>> On 2/14/13 11:04 AM, "Chip Childers" <[email protected]> wrote:
>>>> 
>>>>> On Thu, Feb 14, 2013 at 10:54:34AM -0800, Animesh Chaturvedi wrote:
>>>>>> Folks
>>>>>> 
>>>>>> To make it easier to filter feature discuss emails by mail clients,
>>>>>> Alex suggested that the feature [DISCUSS] emails should be of the
>>>> format
>>>>>> [DISCUSS][$JIRA-BUG-ID] feature short description
>>>>>> 
>>>>>> Example : [DISUSS][CS-527]List API Performance Optimization
>>>>>> 
>>>>>> I think this is a good suggestion and will make it simpler and
>>>>>> consistent way for stakeholders to follow their threads. Can we agree
>>>> to
>>>>>> this? I will update the guidelines in wiki if there is no objection.
>>>>>> 
>>>>>> 
>>>>>> Thanks
>>>>>> Animesh
>>>>> 
>>>>> +1 with the caveat that it's helpful to use the full CLOUDSTACK-X bug
>>>>> ID.
>>>> 
>>>> 
>> 
>> 

Reply via email to