[mb-devel] Stealing issues in jira

[Paul Taylor]

Oliver Charles wrote:
> On Fri, 26 Feb 2010 09:52:43 +0000, Paul Taylor <paul_t100 at fastmail.fm> wrote:
>
>   
>> It depends a bit on why they are being estimated, I mean I don't 
>> estimate any of my tickets, am in meant to, its seems uneccessary if 
>> noone is paying for my time
>>     
>
> Rob likes estimates, because it lets us work out the critical path and
> it lets us plan exactly when we can hope to have work done by. It gives
> a slightly clearer picture as to where we are on the map.
>
> I think this is right, anyway!
>
> --
>     Oliver Charles / aCiD2
>
>   
Was a consensus reached on this in the end ?

As I understand it the reason why these are all assigned is so that 
either warp or acid2 give estimates, but I bet the estimates for many of 
these tasks is very very rough and will turn out to very inaccurate. 
Other way to do this would have ruaok estimate new ones
and only assign a few issues at a time, whereby the estimates could be 
refined by the devloper as and when work starts on them.

Compare this with Lucene which has a similar setup of a few more or 
less  fulltime developers and then another load of developers who dip in 
from time to time.

http://issues.apache.org/jira/browse/LUCENE

The most issues any individual has is  21, they also have  a  user 
called 'Lucene-Devlopers',  seems like a group of some sort  I  wonder 
what its purpose is.


Paul