FogBugz (Case [Issue]14819) Refactoring - Option in “Source code refactoring” menu to simplify control messages sent to literals

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

FogBugz (Case [Issue]14819) Refactoring - Option in “Source code refactoring” menu to simplify control messages sent to literals

Pharo Issue Tracker
FogBugz Notification
avatar
Ulysse The Galactic Monkey From Outer Space resolved Case 14819: Option in “Source code refactoring” menu to simplify control messages sent to literals and assigned it to Kris Gybels:
Feature in Project:  Refactoring: 1. Pharo Image  •  You are subscribed to this case
Pharo is moving fast: We release a new major version every year, with many, many changes. Issue tracker entries tend to get stale after a new release. Bugs are fixed, subsystems replaced or removed. After seeing many out-dated, very old issues staying around forever, we have adopted the following policy: - Issues that do not see ​*any*​ activity are closed autmatically after one year of inactivity. - This is done by a completely automated job which closes up to 5 issues per day older than one year. The issue can (and should!) be re-opened if it is still relavant in the current development version!
Status changed:
Work Needed  changed to  Stale (Timeout)

Assigned To changed:
Everyone  changed to  Kris Gybels

Priority Priority: 5 – Fix If Time Status Status: Stale (Timeout)
Assigned To Assigned to: Kris Gybels Milestone Milestone: Later

Go to Case
No longer need updates? Unsubscribe from this case.

Don't want FogBugz notifications anymore? Update your preferences.

FogBugz

_______________________________________________
Pharo-bugtracker mailing list
[hidden email]
https://lists.gforge.inria.fr/mailman/listinfo/pharo-bugtracker