[Typo3-bugs] Some ideas for bug fixing guidelines
Michael Scharkow
mscharkow at gmx.net
Wed Mar 9 07:23:45 CET 2005
Hi, as announced, here are some ideas for bugfixing rules, so that we
get the pile reduced more easily:
1. Make better use of the status field. Many bugs are still marked as
new although they are old. As soon as someone has looked at the bug and
not immediately closed it, it should be feedback/acknowledged.
2. In this vein: Bugs should not be assigned unless they are to be
closed in a reasonable time frame, maybe 2 weeks. The point is that I
would not mess with other peoples bugs but there are dozens of bugs that
are assigned and not fixed for months. I do not want to reproach the
devs for not fixing stuff, but rather: If you are unable to fix the
thing real soon, please downgrade the status so we can look for other
people to do it.
So dear devs, please look at 'your' bugs and release them if you are
unable/unwilling to fix them.
3. Real discussions are better held here because mail is nicer than web
stuff, for me at least. Long lists of bug notes are annoying.
4. A question: Should diffs be made against the current stable version
of TYPO3 or CVS? I prefer the stable version.
That's it for now, please add stuff here, so we have a bug policy real soon.
Greetings,
Michael
More information about the TYPO3-team-bugs
mailing list