Hi,
We waste a lot of time with
- turning prose descriptions of fixes into code
- trying to fix bugs that are already fixed
- trying to understand issues that have just not enough infos
One thing that would help: If everyone would regularly check their old issue tracker entries.
I think what happens is that when bugs get fixed, everyone assumes that of course the issue gets closed, too
But that is not happening due to multiple reasons:
- Duplicated entries. The *other one* was closed, but not yours
- Fixes happening e.g. due to code rewrites
The easiest is to use the created_by feature:
https://github.com/pharo-project/pharo/issues/created_by/MarcusDenker
-
check if the issue is still relevant
-
has it been fixed?
-
is the description understandable?
-
if it has a suggestion of a fix, do a PR.
(it is much harder to turn prose into code than you would think!)
Marcus
Hi,
We waste a lot of time with
- turning prose descriptions of fixes into code
- trying to fix bugs that are already fixed
- trying to understand issues that have just not enough infos
One thing that would help: If everyone would regularly check their old issue tracker entries.
I think what happens is that when bugs get fixed, everyone assumes that of course the issue gets closed, too
But that is not happening due to multiple reasons:
- Duplicated entries. The *other one* was closed, but not yours
- Fixes happening e.g. due to code rewrites
The easiest is to use the created_by feature:
https://github.com/pharo-project/pharo/issues/created_by/MarcusDenker
- check if the issue is still relevant
- has it been fixed?
- is the description understandable?
- if it has a suggestion of a fix, do a PR.
(it is much harder to turn prose into code than you would think!)
Marcus
