On Fri, 2008-06-27 at 13:12 +0200, Adrian Lienhard wrote:
Norbert, I think this is a good idea!
I updated the page http://code.google.com/p/pharo/wiki/HowToContribute on how to use the issue tracker.
Good! I would have done it else :) I just need to add that what I said is also applicable for 3.10, 3.11 and so. Therefor we can add Type-3dot10, Type-croquet etc. Norbert
Cheers, Adrian
On Jun 27, 2008, at 10:55 , Norbert Hartl wrote:
Every now and then someone tries to improve the way to go by introducing new processes. Most of time nobody likes them and they fail :)
We have several types of changes that we want to integrate in pharo:
- enhancements to the platform - fixes for reported defects - fixes from another squeak release (e.g. 3.10) - fixes from other bug databases like mantis
The type of an issue you open on google is pretty near to that. Just think about it as a source where the change has its origin. For this purpose I created a Type-Mantis in the tracker to assign to tickets from mantis we like to integrate. It might be a step more to do when opening a ticket but the outcome is that we track a list of things already done.
if you look at
http://code.google.com/p/pharo/issues/list?can=1&q=label%3AType-Mantis
you can see what I mean. I think this way it is easier to track things.
What do you think?
Norbert
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project