Manuscript (Case [Issue]22851) _Inbox - Refactorings got broken

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

Manuscript (Case [Issue]22851) _Inbox - Refactorings got broken

Pharo Issue Tracker
Manuscript Notification
avatar
Stephane Ducasse edited Case 22851: Refactorings got broken:
Bug in Project:  _Inbox: Not Spam  •  You are subscribed to this case
Yes I know. I did not say that it was related to calypso. Still I have to enter a bug entry to fix it. Now my point is that if calypso would be managed within Pharo then
people producing enhancement could change it directly instead of having to two three or four PR. Because this is one for Pharo and one for Iceberg and one for Calypso at the minimum. So I expect to see only little changes such as recategorisation in the future because this infrastructure will bored people that want to really improve Pharo.
This is why I will stop!
Priority Priority: 1 – Show Stopper !!!!!! Status Status: Work Needed
Assigned To Assigned to: Everyone Milestone Milestone: Pharo7.0

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

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

Manuscript

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