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.
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. Not only that it makes you not forget anything, having an overview also takes of much mental pressure of your shoulders, because then you avoid the feeling of having a "mountain of work which does never decrease in size" in front of you. Therefore, Toad and maybe others, could you maybe start to review some of the non-closed issues *EVERY DAY*, starting with the oldest, and spending enough time for closing let's say 5 or 10 issues every day. That'll probably take 20 minutes or so, and slow but steady progress will help us cleaning up the bug tracker completely. It's a nice procedure for doing during the morning coffee and I'd be glad if it became mandatory. 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. I can of course continue closing 5-10 issues per day myself, however I can only do that with issues which are very easy to understand, I have no clue of the fred-core so toad will need to manage those issues. Greetings, xor -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part. URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20090526/296d081a/attachment.pgp>
