On Tue, May 26, 2009 at 12:14 PM, Matthew Toseland <
toad at amphibian.dyndns.org> wrote:

> On Tuesday 26 May 2009 13:24:36 xor wrote:
> > I've spent some hours reading random very-old (years!) issues in the bug
> > tracker which are still open, and it seems that we have very very many
> issues
> > which are actually fixed but have not been closed.
>
> Big deal. Yes we should mark fixed bugs as fixed.
>

Xor raises a very valid point, bugtrackers are a *lot* less useful if the
information they contain isn't accurate and current.  I've had a good
experience with a process where you have a weekly "bug scrub", where
everyone goes through each open bug assigned to them and verifies that it is
still valid, and that it shouldn't be reassigned.


> > I consider it as crucial for efficient software development to have a
> CLEAR
> > *per-next-version* overview of what IS done already and what HAS TO BE
> DONE.
>
> I don't. We do need to know what needs to be done for the immediate next
> version, but we only need to have a vague idea of what is necessary for the
> following version.


Well, I'm not sure that Xor was suggesting that we need to formulate a 15
year plan and stick to it, but you are right, really it is only the highest
priority tasks that are essential.


> > Further, I would be glad if we could consider it as mandatory to specify
> a
> > target-version for each issue, which will help us having a roadmap (using
> the
> > roadmap feature of mantis!) for the next release and the releases after
> that.
>
> How many users encountering a bug have any idea what the target version for
> that bug should be?
>

We really don't use versions with Freenet, I mean, we have them, but we roll
out a new version every day.

I think the important thing is to have clearly prioritization of bugs so
that at any given time there is a small menu of things that must be
addressed "next".

Ian.

-- 
Ian Clarke
CEO, Uprizer Labs
Email: ian at uprizer.com
Ph: +1 512 422 3588
Fax: +1 512 276 6674
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://emu.freenetproject.org/pipermail/devl/attachments/20090526/63af0a73/attachment.html>

Reply via email to