- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement

by Mariano Martinez Peck

On Tue, Apr 5, 2011 at 10:07 AM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > > On 05 Apr 2011, at 09:47, Mariano Martinez Peck wrote: > > > Thanks Sven. I would like to remark the ammount of fixes issues. > > Is there an easy why to know this? > > Yeah, it would be cool to add some statistics, like N fixes or commits, R > issues solved, reduced the core complexity from X classes and Y methods to > X' classes and Y' methods, but I cannot easily get to that. > > Is it not so that 1.2 started with #12000 and that we are now on #12345, so > that makes 345 version tags, but of course not all of them are of equal > size/importance. > > If we can't get this half right, we probably better drop it, no ? > > > Just a little note. #12345 is not the number of issues, but for updates. If we take that every update has an average o 3 integrated issues, then the amount of issues should be something like 1000 :) (345 * 3) -- Mariano http://marianopeck.wordpress.com

April 5, 2011

Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement

by Marcus Denker

On Apr 5, 2011, at 9:48 AM, Mariano Martinez Peck wrote: > Thanks Sven. I would like to remark the ammount of fixes issues. > Is there an easy why to know this? > The bug tracker can be queried for issues of a certain tag: 57 for Full: http://code.google.com/p/pharo/issues/list?can=1&q=milestone%3D1.2-DevImage and 693 for Core: http://code.google.com/p/pharo/issues/list?can=1&q=milestone%3D1.2 For all versions, we had 3960 issue tracker submissions, out of which 473 are open. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

April 5, 2011

Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement

by Sven Van Caekenberghe

On 05 Apr 2011, at 09:19, laurent laffont wrote: > On Tue, Apr 5, 2011 at 9:05 AM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > > On 05 Apr 2011, at 07:09, laurent laffont wrote: > > > Remarks: > > - group changed by categories: Morphic/Polymorph, Tools, Under the hood, ... > > - Mocketry is not included in Pharo 1.2 > > Thanks for the feedback, I applied your suggestions. > > For more publicity we can have a word on the new success stories: Inceptive ERP, Issys tracking and DrGeo in http://www.pharo-project.org/about/success-stories > > Laurent. > > > More comments ? > > Sven OK, I added a paragraph 'Success Stories', have a look: http://homepage.mac.com/svc/Pharo/pharo-1.2.1-release.html Are the download links correct ?? Sven

April 5, 2011

Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement

by Sven Van Caekenberghe

On 05 Apr 2011, at 09:47, Mariano Martinez Peck wrote: > Thanks Sven. I would like to remark the ammount of fixes issues. > Is there an easy why to know this? Yeah, it would be cool to add some statistics, like N fixes or commits, R issues solved, reduced the core complexity from X classes and Y methods to X' classes and Y' methods, but I cannot easily get to that. Is it not so that 1.2 started with #12000 and that we are now on #12345, so that makes 345 version tags, but of course not all of them are of equal size/importance. If we can't get this half right, we probably better drop it, no ?

April 5, 2011

Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement

by Mariano Martinez Peck

Thanks Sven. I would like to remark the ammount of fixes issues. Is there an easy why to know this? cheers mariano On Tue, Apr 5, 2011 at 9:19 AM, Sven Van Caekenberghe <sven(a)beta9.be> wrote: > > On 05 Apr 2011, at 07:09, laurent laffont wrote: > > > Remarks: > > - group changed by categories: Morphic/Polymorph, Tools, Under the hood, > ... > > - Mocketry is not included in Pharo 1.2 > > > Thanks for the feedback, I applied your suggestions. And uploaded a newer > version. > > More comments ? > > Sven > -- Mariano http://marianopeck.wordpress.com

April 5, 2011

Re: [Pharo-project] Status of Weak enhancements in Pharo

by Igor Stasenko

On 5 April 2011 06:30, Miguel CobÃ¡ <miguel.coba(a)gmail.com> wrote: > What is the status of the Weak enhancements that were applied to Squeak > 4.2 (by Levente and Igor, mainly) and were targeted for inclusion in > Pharo? Is there a list of them somewhere? which ones are integrated and > which ones are not yet? > Yes, they are already in Pharo. To check if you running VM which supports new finalization, use: WeakFinalizationList hasNewFinalization > Other question, is the plan to take the enhancements as they are and > apply them on Pharo, that is, the versions in Squeak are the reference > or there are conflicting versions in Pharo that are to be keep instead. > I remember that some changes were made to Pharo in this regard. > Do not worry about it. We reviewed the code with Stephane, before integrating it. It was back in Dec 2010 (if i remember). > > Cheers > -- > Miguel CobÃ¡ > http://twitter.com/MiguelCobaMtz > http://miguel.leugim.com.mx > > -- Best regards, Igor Stasenko AKA sig.

April 5, 2011

[Pharo-project] Issue 3962 in pharo: More cleanup of PasteUpMorph

by pharo＠googlecode.com

Status: FixProposed Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3962 by marcus.d...(a)gmail.com: More cleanup of PasteUpMorph http://code.google.com/p/pharo/issues/detail?id=3962 ... related to World-In-World support and general dead code Attachments: CleanPasteUpM.1.cs 4.4 KB

April 5, 2011

[Pharo-project] Issue 3961 in pharo: Fix order of worlmenu

by pharo＠googlecode.com

Status: FixToInclude Owner: marcus.d...(a)gmail.com Labels: Milestone-1.3 New issue 3961 by marcus.d...(a)gmail.com: Fix order of worlmenu http://code.google.com/p/pharo/issues/detail?id=3961 ... System was wrong Attachments: fixMenu.1.cs 3.1 KB

April 5, 2011

Re: [Pharo-project] Draft Pharo 1.2.1 Release Announcement

by Sven Van Caekenberghe

On 05 Apr 2011, at 07:09, laurent laffont wrote: > Remarks: > - group changed by categories: Morphic/Polymorph, Tools, Under the hood, ... > - Mocketry is not included in Pharo 1.2 Thanks for the feedback, I applied your suggestions. And uploaded a newer version. More comments ? Sven

April 5, 2011

Re: [Pharo-project] Issue 3960 in pharo: Catch all: Remove experimental + ancient backward compatibility code

by pharo＠googlecode.com

Comment #1 on issue 3960 by marcus.d...(a)gmail.com: Catch all: Remove experimental + ancient backward compatibility code http://code.google.com/p/pharo/issues/detail?id=3960 remove #fileOutChangeSet:andObject: reason "An experimental version to fileout a changeSet first so that a project can contain its own classes" Attachments: RemoveExperimental.1.cs 158 bytes

April 5, 2011