You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by "Alan D. Cabrera" <li...@toolazydogs.com> on 2010/01/13 15:20:25 UTC

What various priorities mean in Mina's Jira was: Toward 2.0-RC2/2.0.0 : status

On Jan 13, 2010, at 6:14 AM, Julien Vermillard wrote:

> Le Wed, 13 Jan 2010 06:10:21 -0800,
> "Alan D. Cabrera" <li...@toolazydogs.com> a écrit :
>
>> I was wondering, what does the various priorities mean in Mina's  
>> Jira?
>>
> Well nothing special.


:)

The reason that I asked was that it would be nice if one could look at  
the roadmap and discover what the group thought needed to be fixed  
before a release could happen.  It would also be nice to look at the  
roadmap and be able to pick out those issues that are being time-boxed  
and potentially left out of the release.


Regards,
Alan



Re: What various priorities mean in Mina's Jira was: Toward 2.0-RC2/2.0.0 : status

Posted by Emmanuel LŽcharny <el...@gmail.com>.
Alan D. Cabrera a écrit :
>
> The reason that I asked was that it would be nice if one could look at 
> the roadmap and discover what the group thought needed to be fixed 
> before a release could happen.  It would also be nice to look at the 
> roadmap and be able to pick out those issues that are being time-boxed 
> and potentially left out of the release.

https://issues.apache.org/jira/browse/DIRMINA-742 is a serious issue. We 
have to reproduce it, and then analyze why we enter into a deadlock.
>
>
> Regards,
> Alan
>
>
>


Re: What various priorities mean in Mina's Jira was: Toward 2.0-RC2/2.0.0 : status

Posted by Emmanuel LŽcharny <el...@gmail.com>.
Alan D. Cabrera a écrit :
>
> On Jan 13, 2010, at 6:30 AM, Emmanuel LŽcharny wrote:
>
>> Alan D. Cabrera a écrit :
>>>
>>> On Jan 13, 2010, at 6:14 AM, Julien Vermillard wrote:
>>>
>>>> Le Wed, 13 Jan 2010 06:10:21 -0800,
>>>> "Alan D. Cabrera" <li...@toolazydogs.com> a écrit :
>>>>
>>>>> I was wondering, what does the various priorities mean in Mina's 
>>>>> Jira?
>>>>>
>>>> Well nothing special.
>>>
>>>
>>> :)
>>>
>>> The reason that I asked was that it would be nice if one could look 
>>> at the roadmap and discover what the group thought needed to be 
>>> fixed before a release could happen.  It would also be nice to look 
>>> at the roadmap and be able to pick out those issues that are being 
>>> time-boxed and potentially left out of the release.
>> This is what I'm currently doing. There are many issues in the 
>> 'unscheduled' state which needs to be moved to a version in the 
>> roadmap, and also many JIRA's priority need to be set to the correct 
>> level. I agree that some missing Javadoc can be set to critical, as 
>> soon as it's not considered as a bug, and also that uf some log 
>> generates a NPE, hen t shuld not be considered as critical.
>>
>> I'm currently processing the bug list to update those informations.
>
> Sorry, I'm not prescribing what we should do for this release but am 
> trying to make more concrete what the various priorities mean in 
> Mina's Jira.  Jullien's reply implied, to me, that there was none and 
> that it was not important.  My reply addressed this personal perception.

I would say that there are none, yep, but IMO, it's important to 
moderate them and attribute the correct priority to JIRAs in the close 
future...


Re: What various priorities mean in Mina's Jira was: Toward 2.0-RC2/2.0.0 : status

Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
On Jan 13, 2010, at 6:30 AM, Emmanuel LŽcharny wrote:

> Alan D. Cabrera a écrit :
>>
>> On Jan 13, 2010, at 6:14 AM, Julien Vermillard wrote:
>>
>>> Le Wed, 13 Jan 2010 06:10:21 -0800,
>>> "Alan D. Cabrera" <li...@toolazydogs.com> a écrit :
>>>
>>>> I was wondering, what does the various priorities mean in Mina's  
>>>> Jira?
>>>>
>>> Well nothing special.
>>
>>
>> :)
>>
>> The reason that I asked was that it would be nice if one could look  
>> at the roadmap and discover what the group thought needed to be  
>> fixed before a release could happen.  It would also be nice to look  
>> at the roadmap and be able to pick out those issues that are being  
>> time-boxed and potentially left out of the release.
> This is what I'm currently doing. There are many issues in the  
> 'unscheduled' state which needs to be moved to a version in the  
> roadmap, and also many JIRA's priority need to be set to the correct  
> level. I agree that some missing Javadoc can be set to critical, as  
> soon as it's not considered as a bug, and also that uf some log  
> generates a NPE, hen t shuld not be considered as critical.
>
> I'm currently processing the bug list to update those informations.

Sorry, I'm not prescribing what we should do for this release but am  
trying to make more concrete what the various priorities mean in  
Mina's Jira.  Jullien's reply implied, to me, that there was none and  
that it was not important.  My reply addressed this personal perception.


Regards,
Alan
  

Re: What various priorities mean in Mina's Jira was: Toward 2.0-RC2/2.0.0 : status

Posted by Emmanuel LŽcharny <el...@gmail.com>.
Alan D. Cabrera a écrit :
>
> On Jan 13, 2010, at 6:14 AM, Julien Vermillard wrote:
>
>> Le Wed, 13 Jan 2010 06:10:21 -0800,
>> "Alan D. Cabrera" <li...@toolazydogs.com> a écrit :
>>
>>> I was wondering, what does the various priorities mean in Mina's Jira?
>>>
>> Well nothing special.
>
>
> :)
>
> The reason that I asked was that it would be nice if one could look at 
> the roadmap and discover what the group thought needed to be fixed 
> before a release could happen.  It would also be nice to look at the 
> roadmap and be able to pick out those issues that are being time-boxed 
> and potentially left out of the release.
This is what I'm currently doing. There are many issues in the 
'unscheduled' state which needs to be moved to a version in the roadmap, 
and also many JIRA's priority need to be set to the correct level. I 
agree that some missing Javadoc can be set to critical, as soon as it's 
not considered as a bug, and also that uf some log generates a NPE, hen 
t shuld not be considered as critical.

I'm currently processing the bug list to update those informations.