June 2018 - Pharo-dev - lists.pharo.org

[Pharo 7.0-dev] Build #1075: 22170-Improve-comment-of-Jobs-package

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1075 was: SUCCESS. The Pull Request #1571 was integrated: "22170-Improve-comment-of-Jobs-package" Pull request url: https://github.com/pharo-project/pharo/pull/1571 Issue Url: https://pharo.fogbugz.com/f/cases/22170 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 19, 2018

[Pharo 7.0-dev] Build #1074: 22092-Add-part-of-the-keyboard-suport-for-the-menubar

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1074 was: SUCCESS. The Pull Request #1509 was integrated: "22092-Add-part-of-the-keyboard-suport-for-the-menubar" Pull request url: https://github.com/pharo-project/pharo/pull/1509 Issue Url: https://pharo.fogbugz.com/f/cases/22092 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 19, 2018

[Pharo 7.0-dev] Build #1073: 22160-Improve-StringthreeWayCompareTo

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1073 was: SUCCESS. The Pull Request #1564 was integrated: "22160-Improve-StringthreeWayCompareTo" Pull request url: https://github.com/pharo-project/pharo/pull/1564 Issue Url: https://pharo.fogbugz.com/f/cases/22160 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 19, 2018

Re: [Pharo-dev] [Pharo-users] [Ann] Iceberg v1.1.1

by Guillermo Polito

Hi, About why 1.1.1 and not 1.2.0. It's not about cheap or not, but about semantics :) We can agree that there is no hard rule on versionning, do we? But I try to follow the following guidelines (delta my own interpretation that adds some subjectivity :P) - Major Version will change when we break backwards compatibility - Minor Version will change when new features are added - Otherwise, patch version will change. So I don't assign a new version number regarding the number of changes but about what they mean... Now, I considered myself this release as a patch because mostly little bugs here and there were fixed. Moreover, one of the changes done in the credentials manager was to *recover* some backwards compatibility for people setting up credentials in settings files. Of course, to this we add to this that my own interpretation saying that the changes do not break compatibility nor add features :) Now, this is the kind of subjective topic that starts a flamewar, but I'd prefer to use my time on somewhat else ^^. In any case, I think it is more important to discuss about the numbering as soon as we have a clear documentation on Iceberg's API... Regarding the bad links, I copy-pasted the text from the PR instead from the release page in Iceberg, which messes up links. Patch version containing the following cleanups and enhancements #864 <https://github.com/pharo-vcs/iceberg/issues/864> Repairing Missing repositories lead to wrong source directory #861 <https://github.com/pharo-vcs/iceberg/pull/861> update tonel to v1.0.9 #836 <https://github.com/pharo-vcs/iceberg/issues/836> DefaultBackendType class variable is unused #862 <https://github.com/pharo-vcs/iceberg/issues/862> Iceberg tests are not running in Pharo 7 #852 <https://github.com/pharo-vcs/iceberg/issues/852> Make error dialogs copy-pastable #858 <https://github.com/pharo-vcs/iceberg/issues/858> IceTipReadOnlyTextMorph does not allow select and copy anymore #850 <https://github.com/pharo-vcs/iceberg/issues/850> Change Detached head status from error to warning if we are on a tag #853 <https://github.com/pharo-vcs/iceberg/issues/853> Clone dialog "username" is confusing #860 <https://github.com/pharo-vcs/iceberg/pull/860> CredentialStore API #854 <https://github.com/pharo-vcs/iceberg/issues/854> Error in History window Guille On Mon, Jun 18, 2018 at 9:12 PM Torsten Bergmann <astares(a)gmx.de> wrote: > Great - thank you! Might be a small patch release - but nonetheless > important. > > BTW: the links in your mail are pointing to PR's of Pharo and not Iceberg. > If you used > a template you might want to consider changing it. > > > *Gesendet:* Montag, 18. Juni 2018 um 17:47 Uhr > *Von:* "Guillermo Polito" <guillermopolito(a)gmail.com> > *An:* "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org>, > "Discusses Development of Pharo" <pharo-dev(a)lists.pharo.org> > *Betreff:* [Pharo-dev] [Ann] Iceberg v1.1.1 > Hi everybody, > > This week we have a small patch release of Iceberg, version v1.1.1. > This version will be available in the next Pharo build. > > In summary, this release fixes two issues with the new credentials > manager, and introduces a couple of other enhancements/bugfixes. > > Below you will find the detailed changes log. > Enjoy, > Guille > > > Integrate Iceberg 1.1.1 > https://pharo.fogbugz.com/f/cases/22168/Integrate-Iceberg-1-1-1 > > https://github.com/pharo-vcs/iceberg/releases/tag/v1.1.1 > > #864 <https://github.com/pharo-project/pharo/pull/864> Repairing Missing > repositories lead to wrong source directory > #861 <https://github.com/pharo-project/pharo/pull/861> update tonel to > v1.0.9 > #836 <https://github.com/pharo-project/pharo/pull/836> DefaultBackendType > class variable is unused > #862 <https://github.com/pharo-project/pharo/pull/862> Iceberg tests are > not running in Pharo 7 > #852 <https://github.com/pharo-project/pharo/pull/852> Make error dialogs > copy-pastable > #858 <https://github.com/pharo-project/pharo/pull/858> IceTipReadOnlyTextMorph > does not allow select and copy anymore > #850 <https://github.com/pharo-project/pharo/pull/850> Change Detached > head status from error to warning if we are on a tag > #853 <https://github.com/pharo-project/pharo/pull/853> Clone dialog > "username" is confusing > #860 <https://github.com/pharo-project/pharo/pull/860> CredentialStore API > #854 <https://github.com/pharo-project/pharo/pull/854> Error in History > window > > > -- > > > > Guille Polito > > Research Engineer > > > > Centre de Recherche en Informatique, Signal et Automatique de Lille > > CRIStAL - UMR 9189 > > French National Center for Scientific Research - *http://www.cnrs.fr > <http://www.cnrs.fr>* > > > > *Web:* *http://guillep.github.io* <http://guillep.github.io> > > *Phone: *+33 06 52 70 66 13 > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

June 19, 2018

Re: [Pharo-dev] Promote new Pharo 7 VM?

by Alistair Grant

Hi Esteban, On Mon, 18 Jun 2018 at 23:15, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > yes, why not :) Thanks! > but, remember the cycle: > > 1. two weeks in latest (that starts today) > 2. one month in stable 7.0 > 3. promote to stable 6.1 > > yes, is annoying, but is the scheme has worked the better to avoid problems. No problem. Thanks again, Alistair > > On 18 Jun 2018, at 14:20, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > > > Hi Esteban, > > > > Would you consider promoting a new Pharo 7 VM? > > > > 140ff02 should finally solve an issue I've had with time zones and DST > > on Windows in the FileAttributesPlugin. > > > > Testing I've done on this VM: > > > > - Loaded up and used my normal dev environment. > > - Run the full automated test suite on: > > -- Linux 64 bit > > -- Linux 32 bit > > -- Win 32 bit > > > > In each case the set of failures in my environment roughly aligns with > > the current stable VM and the proposed one. > > > > I guess if anyone else has any objections they'll reply to this. :-) > > > > Of course, if you've got any questions or concerns, please let me know. > > > > In case it is useful for anyone, download links are: > > > > Linux 64 bit: http://files.pharo.org/vm/pharo-spur64/linux/pharo-linux-x86_64threaded-201… > > Linux 32 bit: http://files.pharo.org/vm/pharo-spur32/linux/pharo-linux-i386threaded-20180… > > Mac 64 bit: > > - http://files.pharo.org/vm/pharo-spur64/mac/pharo-mac-x86_64-201806171702-14… > > - http://files.pharo.org/vm/pharo-spur64/mac/pharo-mac-x86_64-201806171702-14… > > Mac 32 bit: > > - http://files.pharo.org/vm/pharo-spur32/mac/pharo-mac-i386-201806171702-140f… > > - http://files.pharo.org/vm/pharo-spur32/mac/pharo-mac-i386-201806171702-140f… > > Win 32 bit: http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201806171702-140f… > > > > > > Thanks! > > Alistair > > > >

June 19, 2018

[Pharo 7.0-dev] Build #1072: 22167-Comment-Growl-package

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1072 was: SUCCESS. The Pull Request #1565 was integrated: "22167-Comment-Growl-package" Pull request url: https://github.com/pharo-project/pharo/pull/1565 Issue Url: https://pharo.fogbugz.com/f/cases/22167 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 19, 2018

Re: [Pharo-dev] SessionManager Questions

by Christophe Demarey

Hi Sean, > Le 17 juin 2018 Ã 20:20, Sean P. DeNigris <sean(a)clipperadams.com> a Ã©crit : > > What is the SessionManager equivalent to `Smalltalk addToStartupList: self > after: AnotherClass`? > To do it manually, I don't see an easy way to query the priority/category of > AnotherClass(edited) SessionManager was designed to avoid dependencies between classes / packages that have nothing in common. The best way is to find the best category to register your class in but in some cases, it s not enough. ex: you rely on a class registered in user category but you need that another class startup happens after. In this case, you need to use priorities. You can check dependent class category by inspection the session category but, indeed, there is no way to query the priority/category of a registered handler. It was not needed until now. Do you need to compute the priority dynamically? What is the use case? > Also, it seems that "higher" priority in SessionManager means a lower > number! This seems opposite of both logic and precedent (see Process), no? Youâre right. It simplifies sorting but indeed is counter-intuitive. Changing that now will probably break things for people relying on the current behavior. Cheers, Christophe

June 19, 2018

Re: [Pharo-dev] Promote new Pharo 7 VM?

by Esteban Lorenzano

yes, why not :) but, remember the cycle: 1. two weeks in latest (that starts today) 2. one month in stable 7.0 3. promote to stable 6.1 yes, is annoying, but is the scheme has worked the better to avoid problems. cheers, Esteban > On 18 Jun 2018, at 14:20, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Esteban, > > Would you consider promoting a new Pharo 7 VM? > > 140ff02 should finally solve an issue I've had with time zones and DST > on Windows in the FileAttributesPlugin. > > Testing I've done on this VM: > > - Loaded up and used my normal dev environment. > - Run the full automated test suite on: > -- Linux 64 bit > -- Linux 32 bit > -- Win 32 bit > > In each case the set of failures in my environment roughly aligns with > the current stable VM and the proposed one. > > I guess if anyone else has any objections they'll reply to this. :-) > > Of course, if you've got any questions or concerns, please let me know. > > In case it is useful for anyone, download links are: > > Linux 64 bit: http://files.pharo.org/vm/pharo-spur64/linux/pharo-linux-x86_64threaded-201… > Linux 32 bit: http://files.pharo.org/vm/pharo-spur32/linux/pharo-linux-i386threaded-20180… > Mac 64 bit: > - http://files.pharo.org/vm/pharo-spur64/mac/pharo-mac-x86_64-201806171702-14… > - http://files.pharo.org/vm/pharo-spur64/mac/pharo-mac-x86_64-201806171702-14… > Mac 32 bit: > - http://files.pharo.org/vm/pharo-spur32/mac/pharo-mac-i386-201806171702-140f… > - http://files.pharo.org/vm/pharo-spur32/mac/pharo-mac-i386-201806171702-140f… > Win 32 bit: http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201806171702-140f… > > > Thanks! > Alistair >

June 18, 2018

Re: [Pharo-dev] [Ann] Iceberg v1.1.1

by Torsten Bergmann

June 18, 2018

[Pharo 7.0-dev] Build #1071: 22161-Add-more-log-to-bootstrap

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #1071 was: FAILURE. The Pull Request #1570 was integrated: "22161-Add-more-log-to-bootstrap" Pull request url: https://github.com/pharo-project/pharo/pull/1570 Issue Url: https://pharo.fogbugz.com/f/cases/22161 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 18, 2018