March 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] We crossed 5000 closed issues!
by Marcus Denker March 7, 2012

March 7, 2012

Today the bug tracker: http://code.google.com/p/pharo/issues/list says 436 open out of 5437 issues. Thise means we crossed the line of 5000 reports being closed today. With the first report from damien.cassou, Jun 5, 2008, this translates to 3.65 reports being taken care of *every* day. Marcus -- Marcus Denker -- http://marcusdenker.de

9 8

[Pharo-project] [update 1.4] #14381
by Marcus Denker March 7, 2012

March 7, 2012

14381 ----- Issue 5443: Adding SimpleSwitchMorph (for Stef) http://code.google.com/p/pharo/issues/detail?id=5443 Issue 5105: it allows me to install a method when the class doesnt exists. http://code.google.com/p/pharo/issues/detail?id=5105 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] [update 1.3] #13326
by Marcus Denker March 7, 2012

March 7, 2012

13326 ----- Issue 5153: warningAllowed does not work with undefined selectors http://code.google.com/p/pharo/issues/detail?id=5153 -- Marcus Denker -- http://marcusdenker.de

1 0

Re: [Pharo-project] Pharo-Kernel Gofer broken
by Marcus Denker March 7, 2012

March 7, 2012

On Mar 6, 2012, at 10:11 PM, Pavel Krivanek wrote: > Well, the issue that broke Pharo-Kernel is fixed but in meantime > Pharo-Kernel Gofer is on knees again. The reason is that Monticello is > newly dependent on SystemAnnouncements (that comes together with tests > so it is dependent on SUnit and thus cannot be loaded without the next > remodularization). I will fix that. -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] Pharo-Kernel Gofer broken
by Pavel Krivanek March 6, 2012

March 6, 2012

Well, the issue that broke Pharo-Kernel is fixed but in meantime Pharo-Kernel Gofer is on knees again. The reason is that Monticello is newly dependent on SystemAnnouncements (that comes together with tests so it is dependent on SUnit and thus cannot be loaded without the next remodularization). -- Pavel

1 0

[Pharo-project] .changes are now 37MBâ¦.
by Marcus Denker March 6, 2012

March 6, 2012

... what do we do? http://code.google.com/p/pharo/issues/detail?id=4843 (but that will not help that much. And someone would need to look at the tracker entry and make it ready for integration). or just do a condense? The history is in Monticello. http://code.google.com/p/pharo/issues/detail?id=5379 Marcus -- Marcus Denker -- http://marcusdenker.de

4 3

[Pharo-project] Nautilus feedback
by Alexandre Bergel March 6, 2012

March 6, 2012

Hi! Nautilus is cool! I use it in the Pharo1.4-based Moose image. Some comments: - Cmd-t when selecting a package does not run the tests - Cmd-b does not open a Nautilus, but a standard browser What about the refactoring engine? Does it work in Pharo 1.4? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

4 8

[Pharo-project] [update 1.4] #14380
by Marcus Denker March 6, 2012

March 6, 2012

14380 ----- Issue 5440: Fix isPostmortem http://code.google.com/p/pharo/issues/detail?id=5440 Issue 5438: removeAllButPackages: wants to remove method categories that are owned by traits http://code.google.com/p/pharo/issues/detail?id=5438 Issue 4780: Unify union / difference / intersection on Collections http://code.google.com/p/pharo/issues/detail?id=4780 Issue 5439: GoferOperationTest fails http://code.google.com/p/pharo/issues/detail?id=5439 -- Marcus Denker -- http://marcusdenker.de

1 0

[Pharo-project] Colored Stdout/Stderr logging with headless images
by Sven Van Caekenberghe March 6, 2012

March 6, 2012

This is so cool and beautiful, this new addition where errors with headless images are printed directly to stout or stderr with coloring ! I just saw it the first time today. Really helpful. Thanks a lot Camillo ! Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

4 5

Re: [Pharo-project] We crossed 5000 closed issues!
by Marcus Denker March 6, 2012

March 6, 2012

On Mar 6, 2012, at 3:07 PM, Benoit St-Jean wrote: > Congratulations! Now, we should aim for a much smaller goal... > > Let's make Pharo so good that we'll average less than 1.00 bug fixed a day because Pharo's code will be sooooooooo gooooooooood, rock solid and stable ! ;) > > Keep in mind that these are mostly improvements... We could freeze Pharo and only fix bugs. That would be easy. But is what we have already good enough for that? Do we have a future with Pharo if we only fix bugs? Marcus -- Marcus Denker -- http://marcusdenker.de

2 2