November 2019 - Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #1019: Fix spotter openning bug

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

There is a new Pharo build available! The status of the build #1019 was: FAILURE. The Pull Request #5251 was integrated: "Fix spotter openning bug" Pull request url: https://github.com/pharo-project/pharo/pull/5251 Issue Url: https://github.com/pharo-project/pharo/issues/fix_spotter_bug Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 27, 2019

[Pharo 8.0] Build #1018: Fix spotter openning bug

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

There is a new Pharo build available! The status of the build #1018 was: FAILURE. The Pull Request #5251 was integrated: "Fix spotter openning bug" Pull request url: https://github.com/pharo-project/pharo/pull/5251 Issue Url: https://github.com/pharo-project/pharo/issues/fix_spotter_bug Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 27, 2019

[Pharo 8.0] Build #1017: [easyReview] correcting a small typo

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

There is a new Pharo build available! The status of the build #1017 was: FAILURE. The Pull Request #5245 was integrated: "[easyReview] correcting a small typo" Pull request url: https://github.com/pharo-project/pharo/pull/5245 Issue Url: https://github.com/pharo-project/pharo/issues/typos Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 27, 2019

[Pharo 8.0] Build #1016: Completion: EntryCleanup

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

There is a new Pharo build available! The status of the build #1016 was: FAILURE. The Pull Request #5229 was integrated: "Completion: EntryCleanup" Pull request url: https://github.com/pharo-project/pharo/pull/5229 Issue Url: https://github.com/pharo-project/pharo/issues/CompletuonEntryCleanup Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 27, 2019

[Pharo 8.0] Build #1015: 5223-Remove-blueInk-packages-from-repository

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

There is a new Pharo build available! The status of the build #1015 was: FAILURE. The Pull Request #5243 was integrated: "5223-Remove-blueInk-packages-from-repository" Pull request url: https://github.com/pharo-project/pharo/pull/5243 Issue Url: https://github.com/pharo-project/pharo/issues/5223 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 27, 2019

[Pharo 8.0] Build #1014: fixSystemDependenciesTests

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

There is a new Pharo build available! The status of the build #1014 was: FAILURE. The Pull Request #5242 was integrated: "fixSystemDependenciesTests" Pull request url: https://github.com/pharo-project/pharo/pull/5242 Issue Url: https://github.com/pharo-project/pharo/issues/fixSystemDependenciesTests Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 27, 2019

[Pharo 8.0] Build #1013: 5238-Checking-a-checkbox-in-Enluminer-setting-crash

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

There is a new Pharo build available! The status of the build #1013 was: FAILURE. The Pull Request #5240 was integrated: "5238-Checking-a-checkbox-in-Enluminer-setting-crash" Pull request url: https://github.com/pharo-project/pharo/pull/5240 Issue Url: https://github.com/pharo-project/pharo/issues/5238 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 26, 2019

[Pharo 8.0] Build #1012: 5232-Remove-GTEventRecorder-

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

There is a new Pharo build available! The status of the build #1012 was: FAILURE. The Pull Request #5236 was integrated: "5232-Remove-GTEventRecorder-" Pull request url: https://github.com/pharo-project/pharo/pull/5236 Issue Url: https://github.com/pharo-project/pharo/issues/5232 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 26, 2019

Re: [Pharo-dev] BlueInk removal

by Torsten Bergmann

I guess most Pharo developers and user care more on RELIABILITY, STABILITY and REPRODUCABILITY. Unfortunately there was - no initial discussion on the mailinglist - no description what "Enlumineur" is or where to find it (had to google it and link issue to your repo) - PR was not reviewed nor commented from a second side although removal or switch to basic formatter is a more radical change - an integrator is merging his own PR, no additional look from a second side - all this from one day to the other - ending up in an image broken settings and a basic formatter (who is buggy and eating the comments when used) which will also affect future contributions We for sure all agree on the "WHY" and value that you take action to care on the topic. But you have to admit the "HOW" puts a guestion mark on the way the contribution/integration process works. We have broken settings now - which was clear when we just remove. This will also not be solved automagically when we are past alpha stage. Especially when proper deprecation would have been a single method in the package manifest, see [1]. Some community members had to repair local settings now and also this discussion pulls time (we all could have better invested). If the plate is full we will not empty it out by leaving our paths ... Thx T. [1] http://forum.world.st/Deprecation-guide-for-methods-classes-and-packages-td… > Gesendet: Dienstag, 26. November 2019 um 18:29 Uhr > Von: "ducasse" <stepharo(a)netcourrier.com> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] BlueInk removal > > Cyril > > We are crawling with too many things. > Pharo should start to lose fat FOR REAL. > I really hope that we will get rid of lot of old code in the future. > If Enlumineur does not work when we integrate it - I just issue a PR > then you will have a good case for reintegrating and having two formatter, two contexts classes, > two packages full of nearly the same but not quite tests. > > S. > > > On 26 Nov 2019, at 14:16, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > > > On Tue, Nov 26, 2019 at 2:07 PM ducasse <stepharo(a)netcourrier.com> wrote: > >> > >> Cyril can you wait until this evening? > >> We should remove old things and having the two side by side is a lot more painful > >> to work. > >> We are still in Pharo 80 alpha. > >> > >> Stef > >> > > > > Can't we deprecate it? It's 1200 LoC, if it's deprecated everything > > will be stricked and people will know they should not use it and it > > will help us migrate our settings without breaking everything. > > > > And deprecating it is just one method in the manifest. > > > >> > >> > > > > > > -- > > Cyril Ferlicot > > https://ferlicot.fr > > > > > >

Nov. 26, 2019

[Pharo 8.0] Build #1011: 5233-Integrate-EnlumineurFormatter

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

There is a new Pharo build available! The status of the build #1011 was: FAILURE. The Pull Request #5234 was integrated: "5233-Integrate-EnlumineurFormatter" Pull request url: https://github.com/pharo-project/pharo/pull/5234 Issue Url: https://github.com/pharo-project/pharo/issues/5233 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Nov. 26, 2019