Updates:
Status: Closed
Comment #5 on issue 4686 by
[hidden email]: method category change
creates no new version
http://code.google.com/p/pharo/issues/detail?id=4686With Pharo 2.0 now beta, time has come to review bug reports that have not
seen any activity in 2012.
To keep the amount of issues managable, we close reports that have not
drawn any attention for over one
year.
The reporter (and thus owner) of the issue should:
-> check the issue in 2.0. Is it still relevant?
-> If yes, just add a note to the report and we will be opened again.
As your issue has not seen any attention for over a year, please consider
to give more information.
A good idea can be to send a mail to the mailinglist to get other people to
help fixing the bug or
implementing an improvement.
_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker