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

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

by Tudor Girba

Hi, Indeed. Something went amiss in this email exchange. But, I really do not think that you are in disagreement. Cheers, Doru > On Jun 19, 2018, at 4:09 PM, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > > Hi Norbert, > >> Le 19 juin 2018 Ã 14:06, Norbert Hartl <norbert(a)hartl.name> a Ã©crit : >> >> I have no use for an environment where people only care about coding new cool stuff. If it would be like this I would quit all my pharo businesses, move to mainstream and would use pharo only for hobbyist projects because that would be the level that can be met. > > I do not think Guille has this state of mind. He spends time to write lot of tests for code other people wrote (not the funniest part), to clean code in the image (old code, bad dependencies, better API), to improve existing stuff, answering questions on the ML, and so on. > He is one of the few people that really tries to push semantic versioning. He could have made some errors (like everyone) but I find your sentence not fair for him. > > Regards, > Christophe -- www.tudorgirba.com www.feenk.com "We are all great at making mistakes."

June 19, 2018

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

by Christophe Demarey

Hi Norbert, > Le 19 juin 2018 Ã 14:06, Norbert Hartl <norbert(a)hartl.name> a Ã©crit : > > I have no use for an environment where people only care about coding new cool stuff. If it would be like this I would quit all my pharo businesses, move to mainstream and would use pharo only for hobbyist projects because that would be the level that can be met. I do not think Guille has this state of mind. He spends time to write lot of tests for code other people wrote (not the funniest part), to clean code in the image (old code, bad dependencies, better API), to improve existing stuff, answering questions on the ML, and so on. He is one of the few people that really tries to push semantic versioning. He could have made some errors (like everyone) but I find your sentence not fair for him. Regards, Christophe

June 19, 2018

Re: [Pharo-dev] [Pharo-users] [ANN] Pharo Launcher v1.2 release

by Tudor Girba

Great work! Doru > On Jun 19, 2018, at 3:55 PM, Christophe Demarey <Christophe.Demarey(a)inria.fr> wrote: > > Hi all, > > I just released PharoLauncher 1.2. It includes a new windows installer that you can use without administrator privileges as well as binary signing for OS X and Windows. Also, Pharo Launcher is not anymore identified as âPharoâ application and comes with its own icon. > > Here is the changelog (details on https://github.com/pharo-project/pharo-launcher/issues) > New features: > #21 Bless the DMG > #46 sign pharo launcher app for windows > #103 No way to rename a local template > #107 Unable to add a description for the image using the Launcher UI > #121 You can't see/sort images by last modified date > Improvements: > #69 Import command should also import pharo-local directory > #70 Import command should delete origin folder if empty > #73 Managers of Download of VMs and images should be in their own packages > #76 Use https instead of http to requests the pharo file server > #82 Official Distributions loads 32bit versions on 64bit System (i.e. provide better information on templates architecture) > #86 Sort Existing Images Case-Insensitive > #98 Copy and subfolders problem (contents no copied) > #101 Templates from a local image are listed in "downloaded". "local" would be a better name > #102 Template Cleared at Startup setting is enabled, making it weird when trying to use the template feature > #106 Import could work if we select the parent folder of an image > #109 Use latest pre-Spur VM to determine the image version > #122 The Run without settings icon looks like a funny grey/which blob (missing alpha correction) > Bux fixes: > #41 #selectedMorphList was sent to nil > #67 bash is not a command usable under windows > #68 Does not launch images on Windows > #85 Double click on an existing image open a file selector > #88 Pharo Launcher on Windows > Failing > #104 GUI bug makes Launcher unusable > #110 Image launch not reliable on Windows > #119 MessageNotUnderstood exception on launch > #123 The status bar of the Launcher is broken, so can't easily show image descriptions > > > Big thanks to all contributors: code, issues report, comments, advices. > > You can get platform bundles from pharo download page or files.pharo.org: http://files.pharo.org/pharo-launcher/1.2/ > > Regards, > Christophe. -- www.tudorgirba.com www.feenk.com "The coherence of a trip is given by the clearness of the goal."

June 19, 2018

[ANN] Pharo Launcher v1.2 release

by Christophe Demarey

Hi all, I just released PharoLauncher 1.2. It includes a new windows installer that you can use without administrator privileges as well as binary signing for OS X and Windows. Also, Pharo Launcher is not anymore identified as âPharoâ application and comes with its own icon. Here is the changelog (details on https://github.com/pharo-project/pharo-launcher/issues <https://github.com/pharo-project/pharo-launcher/issues>): New features: #21 Bless the DMG #46 sign pharo launcher app for windows #103 No way to rename a local template #107 Unable to add a description for the image using the Launcher UI #121 You can't see/sort images by last modified date Improvements: #69 Import command should also import pharo-local directory #70 Import command should delete origin folder if empty #73 Managers of Download of VMs and images should be in their own packages #76 Use https instead of http to requests the pharo file server #82 Official Distributions loads 32bit versions on 64bit System (i.e. provide better information on templates architecture) #86 Sort Existing Images Case-Insensitive #98 Copy and subfolders problem (contents no copied) #101 Templates from a local image are listed in "downloaded". "local" would be a better name #102 Template Cleared at Startup setting is enabled, making it weird when trying to use the template feature #106 Import could work if we select the parent folder of an image #109 Use latest pre-Spur VM to determine the image version #122 The Run without settings icon looks like a funny grey/which blob (missing alpha correction) Bux fixes: #41 #selectedMorphList was sent to nil #67 bash is not a command usable under windows #68 Does not launch images on Windows #85 Double click on an existing image open a file selector #88 Pharo Launcher on Windows > Failing #104 GUI bug makes Launcher unusable #110 Image launch not reliable on Windows #119 MessageNotUnderstood exception on launch #123 The status bar of the Launcher is broken, so can't easily show image descriptions Big thanks to all contributors: code, issues report, comments, advices. You can get platform bundles from pharo download page or files.pharo.org <http://files.pharo.org/>: http://files.pharo.org/pharo-launcher/1.2/ <http://files.pharo.org/pharo-launcher/1.2/> Regards, Christophe.

June 19, 2018

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

by Guillermo Polito

On Tue, Jun 19, 2018 at 2:07 PM Norbert Hartl <norbert(a)hartl.name> wrote: > Hi, > > let me wear the project manager hat for a moment. > let me too, because the fact that I'm younger does not mean I don't know, right? :) > > Am 19.06.2018 um 10:59 schrieb Guillermo Polito <guillermopolito(a)gmail.com > >: > > Hi, > > About why 1.1.1 and not 1.2.0. Itâs not about cheap or not, but about > semantics :) > > > for me âcaring about semanticsâ is just one of the top ten justifications > developers use for the changes they did. > Maybe, and putting the hat of project manager is usually a justification for somebody that is not good at technical stuff. But I know that's not like it, so please let's not enter into this, I've felt a little insulted by this comment... > > 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. > > There is only one hard rule for me and that is knowing about the risk to > take. > That's a matter of conventions. We agree that version 1.1.x is compatible with 1.1.y. > So if we take the patch version it should only include important bug fixes > and nothing else. I would argue that only #864, #862, #858 and #854 qualify > for such a patch if at all. > So they are to my view. They should not introduce any compatibility issue. And if they do, that's an error, but we are too few helping here, doing our best... > Not sure about #860 because the title is not specific enough. > Please, I'll let you judge it for yourself https://github.com/pharo-vcs/iceberg/pull/860/files But to me that change applies to patch. It actually fixes a compatibility issue that was introduced in 1.1.0. > The point for me is that I want my project to rely on something like 1.1.x > because I donât want anything to change that breaks my software. And I can > tell you that most developers underestimate the side-effects of changes. > I'm well aware of this. But do you have a concrete issue? > > So I donât assign a new version number regarding the number of changes but > about what they mean... > > > To mean they mean it is a risk to use that version and you define how big > that is. > We are trying to do weekly releases, we could do better but again. I can count with my hand fingers people contributing with actual commits and issues in the issue tracker. > > 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 :) > > You see you said âmostly bugsâ and that is the error already. > I'm sorry for not being perfect... > I mean we come from an amateurish behaviour that we change released > artefacts. > I assure you I do my best on it, and I'm one of the first that cries aloud when there are versionning and dependencies problems. What I do not understand if this mail was meant as a lesson for the community or should I take it personally... > That is not discussable just a no-go. > I know and I'm against it. So we agree, right? > The reason was it would have wasted a huge amount of time to do a new > version. So ok it was a loose-loose situation. Now we can do it better and > I want something far less amateurish. So you can discuss your semantics > about what major and minor versions in pharo mean but patch needs to be the > definition of the combination: least risk - highest value. > Would you help us measuring the risk? > > Now, this is the kind of subjective topic that starts a flamewar, but Iâd > prefer to use my time on somewhat else ^^. > > > You may not like to talk about these things but I do. And you should > listen. > I mostly do [enjoy such discussions] but what I learn from this discussion is: - you think I'm stupid, or young, or both, so I don't know - we are all amateurs > I have no use for an environment where people only care about coding new > cool stuff. > I'm fu*** trying to make Iceberg as stable as possible, If I was just wanting to do new cool stuff I would not be doing this.

June 19, 2018

Pharo Sprints second half 2018

by Marcus Denker

Pharo Sprints second half 2018 ==================== We organise one Pharo âSprintâ per month were we meet to work on boring issue tracker entries together. Goals of the next sprints: - Fix issues for Pharo7 - Backport important fixes to Pharo6 - Clean issue tracker to prepare for release Pharo7 Remotely, you can join us on Discord. During the sprint, we will try to synchronize local and remote Pharo sprinters. In the past people organised local sprints at the same time (e.g. Santiago/Chile). See here for more infos: http://pharo.org/contribute-events There will be an event on the association website for each sprint. The next dates are: Friday June 29 https://association.pharo.org/event-2789583 Friday 31 August https://association.pharo.org/event-2973616 Friday 28 September https://association.pharo.org/event-2973620 Friday 26 October https://association.pharo.org/event-2973622 Friday 30 November https://association.pharo.org/event-2973626 Friday 21 December (Christmas Sprint) https://association.pharo.org/event-2973628 https://association.pharo.org/news/6320747

June 19, 2018

Re: [Pharo-dev] SessionManager Questions

by James Foster

> On Jun 19, 2018, at 2:50 AM, Christophe Demarey <christophe.demarey(a)inria.fr> wrote: > >> Le 17 juin 2018 Ã 20:20, Sean P. DeNigris <sean(a)clipperadams.com> a Ã©crit : > >> 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. I guess it seems intuitive to me that 1st place is higher priority than 2nd place or that 1 comes before 2. But you could add a new API with a number that gets translated to/from an internal value. That is the beauty of encapsulation. James Foster

June 19, 2018

[Pharo 7.0-dev] Build #1077: 22131-Begin-to-add-requirement-in-Athens-baseline

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

There is a new Pharo build available! The status of the build #1077 was: FAILURE. The Pull Request #1533 was integrated: "22131-Begin-to-add-requirement-in-Athens-baseline" Pull request url: https://github.com/pharo-project/pharo/pull/1533 Issue Url: https://pharo.fogbugz.com/f/cases/22131 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 Norbert Hartl

Hi, let me wear the project manager hat for a moment. > Am 19.06.2018 um 10:59 schrieb Guillermo Polito <guillermopolito(a)gmail.com>: > > Hi, > > About why 1.1.1 and not 1.2.0. Itâs not about cheap or not, but about semantics :) for me âcaring about semanticsâ is just one of the top ten justifications developers use for the changes they did. > 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. > There is only one hard rule for me and that is knowing about the risk to take. So if we take the patch version it should only include important bug fixes and nothing else. I would argue that only #864, #862, #858 and #854 qualify for such a patch if at all. Not sure about #860 because the title is not specific enough. The point for me is that I want my project to rely on something like 1.1.x because I donât want anything to change that breaks my software. And I can tell you that most developers underestimate the side-effects of changes. > So I donât assign a new version number regarding the number of changes but about what they mean... To mean they mean it is a risk to use that version and you define how big that is. > 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 :) > You see you said âmostly bugsâ and that is the error already. I mean we come from an amateurish behaviour that we change released artefacts. That is not discussable just a no-go. The reason was it would have wasted a huge amount of time to do a new version. So ok it was a loose-loose situation. Now we can do it better and I want something far less amateurish. So you can discuss your semantics about what major and minor versions in pharo mean but patch needs to be the definition of the combination: least risk - highest value. > Now, this is the kind of subjective topic that starts a flamewar, but Iâd prefer to use my time on somewhat else ^^. You may not like to talk about these things but I do. And you should listen. I have no use for an environment where people only care about coding new cool stuff. If it would be like this I would quit all my pharo businesses, move to mainstream and would use pharo only for hobbyist projects because that would be the level that can be met. Norbert > 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 <mailto:astares@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 <mailto:guillermopolito@gmail.com>> > An: "Any question about pharo is welcome" <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>>, "Discusses Development of Pharo" <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@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://pharo.fogbugz.com/f/cases/22168/Integrate-Iceberg-1-1-1> > https://github.com/pharo-vcs/iceberg/releases/tag/v1.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

[Pharo 7.0-dev] Build #1076: 22173-Some-tests-are-rotten-in-OCContextTempMappingTest

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

There is a new Pharo build available! The status of the build #1076 was: FAILURE. The Pull Request #1572 was integrated: "22173-Some-tests-are-rotten-in-OCContextTempMappingTest" Pull request url: https://github.com/pharo-project/pharo/pull/1572 Issue Url: https://pharo.fogbugz.com/f/cases/22173 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

June 19, 2018