Use of "Future"
Christian Robottom Reis
kiko at async.com.br
Thu Mar 18 21:51:06 UTC 2004
On Thu, Mar 18, 2004 at 09:13:10PM +0000, Gervase Markham wrote:
> Currently, we appear to be pushing a load of bugs from "2.18" to "2.20".
> I can see the same thing happening again in six months time.
> In the interests of having a 2.20 list which is always fairly accurate,
> why don't we start using "Future", and pull _in_ bugs as appropriate,
> rather than always pushing them out?
I have my reservations aboute the use of Future. I think the current
"pushout" of bugs might not be the best way of triaging things, but that
should be solved by stronger planning ("this is the feature set or
general target we want for 2.20") and using the plan to justify what
we'll be working on for a certain release. Whether this is practical for
an OSS project with a small team is yet to be determined <wink>.
I appreciate pushing bugs off because it's a chance you have of actually
looking at stuff that might have been forgotten -- I added a one-liner
patch today that wouldn't have been added if I hadn't noticed it during
the retargetting. My impression is that stuff in "Future" tends to be
forgotten since we aren't targetting having it fixed at all, ever.
Christian Robottom Reis | http://async.com.br/~kiko/ | [+55 16] 261 2331
More information about the developers