We really need to find a way that people add better information.
For me one thing I will try to do: to not use the issue tracker anymore as my private TODO list.
This means that the ���I should maybe look into this but i have no time to even add a description���
entries are now in my private list and if I make an issue on the issue tracker I will try to write it
in a way that it explains how someone else could fix it.
Marcus
This is it.
Finally this problem is spotted. It's been years since I read a Pharo issue because of their targeted "narrative" to a bunch of 5 - 10 people who share a daily operational knowledge. This is more severe with the VM front.
Other communities, like R, use a lot minimum reproducible example (MRE). So nothing new should be invented here, if Pharo just could adopt one of the standard practices...
Cheers,
Hern��n
El mar., 29 oct. 2019 a las 8:56, Torsten Bergmann (<
astares@gmx.de>) escribi��:
+1000
I've seen this several times that issues where just a short title only "wizards" were able to understand
The "Full description requires time" is not an argument here. We all should get more professional
and disciplined here - so anyone is able to reproduce and understand what an issue is about. This will
also increase the trust into Pharo and its dev process...
Bye
T.