Status: Accepted
Owner:
[hidden email]
Labels: Type-Cleanup Difficulty-Easy
New issue 6191 by
[hidden email]: Update Google code for new release
process
http://code.google.com/p/pharo/issues/detail?id=6191 From
http://forum.world.st/Backporting-fixes-tp4633625p4633691.html by Ben
Coman:
* Remove template "Pharo 1.4 Enhancement".
* Template "Pharo 1.4 Bug" currently has an empty description. Change to
something like:
-> No new features.
-> No cleanups
-> If a bug was there in Pharo 1.1 already and we lived with it for
years, fixing it in the current dev version is (in many cases) enough.
(There are exceptions, but is does not happen often).
-> Community input is important. A ready-to-include fix with a
description that it was tested and a note that it for sure works will not
be ignored. For an entry that is nearly finished yet nobody even cares to
test it, why bother?
* change from "Milestone-1.4" to "Maintenance-1.4" - since that milestone
has already passed.
_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker
Locked
