Re: [Pharo-dev] [ANN] SmalltalkCI now supports Pharo 8

> Am 23.01.2019 um 08:20 schrieb Sven Van Caekenberghe : > > > >> On 23 Jan 2019, at 01:13, Ben Coman wrote: >> >> Only in the past week I became aware of that SmalltalkCI was integrated with >> Travis... >> https://docs.travis-ci.com/user/languages/smalltalk >> > > Shame on you ;-) >

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

> Am 23.01.2019 um 04:13 schrieb Sean P. DeNigris : > > EstebanLM wrote >> https://news.ycombinator.com/item?id=18968116 > > Wow! 13 hours without any hardcore flame wars. We are improving ;-) > > > EstebanLM wrote >> https://www.reddit.com/r/programming/comments/aimwlh/pharo_70_released/

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

Congratulations to you all! It has been a hard piece of work which was postponed 9 months. But the changes to collaboration process, build process, 64 bit maturing and huge list of things was worth it. Hopefully the next version is less huge. Happy to be able to take part!!! Norbert > Am

[Pharo-dev] [Pharo 8.0] Build #21: 2298-Rename-SugsBrowseVariableDefintion-into-SugsBrowseVariableDefinition

There is a new Pharo build available! The status of the build #21 was: FAILURE. The Pull Request #2300 was integrated: "2298-Rename-SugsBrowseVariableDefintion-into-SugsBrowseVariableDefinition" Pull request url: https://github.com/pharo-project/pharo/pull/2300 Issue Url:

Re: [Pharo-dev] [ANN] SmalltalkCI now supports Pharo 8

> On 23 Jan 2019, at 01:13, Ben Coman wrote: > > Only in the past week I became aware of that SmalltalkCI was integrated with > Travis... > https://docs.travis-ci.com/user/languages/smalltalk > Shame on you ;-) Seriously: I have it on all my projects, it works great

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

EstebanLM wrote > https://news.ycombinator.com/item?id=18968116 Wow! 13 hours without any hardcore flame wars. We are improving ;-) EstebanLM wrote > https://www.reddit.com/r/programming/comments/aimwlh/pharo_70_released/ Ew, not as warm and fuzzy here ha ha - Cheers, Sean -- Sent

Re: [Pharo-dev] [ANN] SmalltalkCI now supports Pharo 8

Only in the past week I became aware of that SmalltalkCI was integrated with Travis... https://docs.travis-ci.com/user/languages/smalltalk Now I'm really curious, how is it hooked into the back end of Travis? cheers -ben On Wed, 23 Jan 2019 at 07:16, Gabriel Cotelli wrote: > Now you can run

[Pharo-dev] [ANN] SmalltalkCI now supports Pharo 8

Now you can run your builds against Pharo 8: Check https://github.com/hpi-swa/smalltalkCI#list-of-supported-images Stable and Alpha versions were also updated, now pointing to Pharo 7 and 8 respectively. Please report any issue you found. Regards, Gabriel

[Pharo-dev] [Pharo 8.0] Build #20: Adding an "Inspect Debugger" command to the debugger UI.

There is a new Pharo build available! The status of the build #20 was: FAILURE. The Pull Request #2197 was integrated: "Adding an "Inspect Debugger" command to the debugger UI." Pull request url: https://github.com/pharo-project/pharo/pull/2197 Issue Url:

[Pharo-dev] [Pharo 8.0] Build #19: 2250-Enhance-RBParseTreeRewriter-class-comment-to-show-

There is a new Pharo build available! The status of the build #19 was: FAILURE. The Pull Request #2288 was integrated: "2250-Enhance-RBParseTreeRewriter-class-comment-to-show-" Pull request url: https://github.com/pharo-project/pharo/pull/2288 Issue Url:

[Pharo-dev] [Pharo 8.0] Build #18: 2154-Use-theme-colors-in-Rubric

There is a new Pharo build available! The status of the build #18 was: FAILURE. The Pull Request #2290 was integrated: "2154-Use-theme-colors-in-Rubric" Pull request url: https://github.com/pharo-project/pharo/pull/2290 Issue Url: https://pharo.fogbugz.com/f/cases/2154 Build Url:

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

Great. I confirm that it works now :) Doru > On Jan 22, 2019, at 9:49 PM, Esteban Lorenzano wrote: > > > >> On 22 Jan 2019, at 21:26, Tudor Girba wrote: >> >> Hi, >> >> On HackerNews, people are trying to run the factorial example from the main >> page and that does not work. It

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

> On 22 Jan 2019, at 21:26, Tudor Girba wrote: > > Hi, > > On HackerNews, people are trying to run the factorial example from the main > page and that does not work. It currently looks like this: > > $ curl https://get.pharo.org | bash > $ ./pharo Pharo.image eval "42 factorial” > > But,

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

Hi, On HackerNews, people are trying to run the factorial example from the main page and that does not work. It currently looks like this: $ curl https://get.pharo.org | bash $ ./pharo Pharo.image eval "42 factorial” But, the path is incorrect. It should probably be more like: $ wget -O-

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

The Discord channel could use some human replies as well, some newcomers are coming with basic questions about getting started with Pharo (and Pharo Launcher), so basic that I don't have a canonical answer (because I work around these issues using my shenanigans). Esteban A. Maringolo El mar.,

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

> On 22 Jan 2019, at 14:39, Esteban Lorenzano wrote: > > https://news.ycombinator.com/item?id=18968116 Please join, this is going really well: 100+ upvotes, 60+ comments (both are important). Let's keep the momentum going (this is a unique chance to get some publicity).

[Pharo-dev] [Pharo 7.0] Build #142: 22901-Image-crash-on-commit-and-push-in-windows-64bit

There is a new Pharo build available! The status of the build #142 was: SUCCESS. The Pull Request #2295 was integrated: "22901-Image-crash-on-commit-and-push-in-windows-64bit" Pull request url: https://github.com/pharo-project/pharo/pull/2295 Issue Url:

[Pharo-dev] [Pharo 7.0] Build #141: 22901-Image-crash-on-commit-and-push-in-windows-64bit

There is a new Pharo build available! The status of the build #141 was: SUCCESS. The Pull Request #2295 was integrated: "22901-Image-crash-on-commit-and-push-in-windows-64bit" Pull request url: https://github.com/pharo-project/pharo/pull/2295 Issue Url:

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

Thank you, everybody, this is a massive collaborative effort, something to be proud of. > On 22 Jan 2019, at 14:36, Esteban Lorenzano wrote: > > Pharo 7.0 released! > === > > Dear World and dynamic language lovers: > > The time has come for Pharo 7.0! > > Pharo is a pure

Re: [Pharo-dev] Pharo 6.1 backport

Ok, and with this I will close pharo 6.0 for good :) Esteban > On 22 Jan 2019, at 15:08, Gabriel Cotelli wrote: > > Hi! > Now that release madness is over ;) can we get > https://pharo.manuscript.com/f/cases/22869/Backport-fix-of-MetacelloCypress-support > >

[Pharo-dev] Pharo 6.1 backport

Hi! Now that release madness is over ;) can we get https://pharo.manuscript.com/f/cases/22869/Backport-fix-of-MetacelloCypress-support merged? I'm holding back some releases waiting for this change to not break Pharo 6.1 support. Thank you!

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

Great work! Thanks everyone for all the effort! Doru > On Jan 22, 2019, at 2:36 PM, Esteban Lorenzano wrote: > > Pharo 7.0 released! > === > > Dear World and dynamic language lovers: > > The time has come for Pharo 7.0! > > Pharo is a pure object-oriented programming language

[Pharo-dev] [ANN] Pharo 8.0 development started!

Hi, As you know, after releasing a version of Pharo, a new cycle of development starts. There is no perfect release, and with Pharo we play an infinite game (see Marcus talk at ESUG). So, now Pharo 7.0 has entered maintenance mode and Pharo 8.0 is the new development branch. That means:

Re: [Pharo-dev] [ANN] Pharo 7.0 released!

Upvote links: https://www.reddit.com/r/programming/comments/aimwlh/pharo_70_released/ https://news.ycombinator.com/item?id=18968116 Cheers! Esteban > On 22 Jan 2019, at

[Pharo-dev] [Pharo 7.0] Build #140: SUCCESS

There is a new Pharo build available! The status of the build #140 was: SUCCESS. Could not extract further issue information from commit message: fix upload of release versions Build Url:

[Pharo-dev] [Pharo 7.0] Build #139: FAILURE

There is a new Pharo build available! The status of the build #139 was: FAILURE. Could not extract further issue information from commit message: fix upload of release versions Build Url:

[Pharo-dev] [Pharo 7.0] Build #138: FAILURE

There is a new Pharo build available! The status of the build #138 was: FAILURE. Could not extract further issue information from commit message: fix upload of release versions Build Url:

[Pharo-dev] [Pharo 8.0] Build #17: SUCCESS

There is a new Pharo build available! The status of the build #17 was: SUCCESS. Could not extract further issue information from commit message: Merge branch 'Pharo7.0' into Pharo8.0 Build Url:

[Pharo-dev] [Pharo 7.0] Build #136: SUCCESS

There is a new Pharo build available! The status of the build #136 was: SUCCESS. Could not extract further issue information from commit message: fix upload of release versions Build Url:

[Pharo-dev] [Pharo 7.0] Build #134: 22903-backport-to-P70fixes-on-bootstrap-scripts

There is a new Pharo build available! The status of the build #134 was: FAILURE. The Pull Request #2285 was integrated: "22903-backport-to-P70fixes-on-bootstrap-scripts" Pull request url: https://github.com/pharo-project/pharo/pull/2285 Issue Url: https://pharo.fogbugz.com/f/cases/22903

Re: [Pharo-dev] contribution workflow

Hi Ben, I'll just expand a bit on what Pavel said. On Mon, Jan 21, 2019 at 4:59 PM Ben Coman wrote: > I'm not sure how closely my contribution workflow matches the standard > advertised, so just wanted to share it for feedback. I may remember > wrongly, but my understanding of the advertised