- Pharo-dev - lists.pharo.org

[Pharo 8.0] Build #268: Fixes #3115
by ci-pharo-ci-jenkins2＠inria.fr May 12, 2019

May 12, 2019

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

1 0

consortium engineers
by Ben Coman May 12, 2019

May 12, 2019

I hadn't heard before... four consortium engineers for a year, very cool... slides 3 & 4... https://www.slideshare.net/pharoproject/pharo-70-and-80-alpha thanks Schmidt & LIfeware, and all consortium partners. cheers -ben

2 1

[Pharo 8.0] Build #267: 3320-Improve-HistorySlot-and-other-small-fixes
by ci-pharo-ci-jenkins2＠inria.fr May 12, 2019

May 12, 2019

There is a new Pharo build available! The status of the build #267 was: FAILURE. The Pull Request #3321 was integrated: "3320-Improve-HistorySlot-and-other-small-fixes" Pull request url: https://github.com/pharo-project/pharo/pull/3321 Issue Url: https://github.com/pharo-project/pharo/issues/3320 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #266: Fix wording typo
by ci-pharo-ci-jenkins2＠inria.fr May 11, 2019

May 11, 2019

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

1 0

[Pharo 8.0] Build #265: 3312-KMKeymapnotifyPartialMatchTo-leads-to-an-error
by ci-pharo-ci-jenkins2＠inria.fr May 10, 2019

May 10, 2019

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

1 0

[Pharo 8.0] Build #264: 3328-SubclassResponsibility-error-when-running-RBParserparseFaultyMethod
by ci-pharo-ci-jenkins2＠inria.fr May 10, 2019

May 10, 2019

There is a new Pharo build available! The status of the build #264 was: SUCCESS. The Pull Request #3329 was integrated: "3328-SubclassResponsibility-error-when-running-RBParserparseFaultyMethod" Pull request url: https://github.com/pharo-project/pharo/pull/3329 Issue Url: https://github.com/pharo-project/pharo/issues/3328 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

introducing my GSoC project - Improving Code Completion
by Myroslava Romaniuk May 9, 2019

May 9, 2019

Hi everyone, My name is Myroslava, I'm a 3rd year CS student in Ukraine, and my project Improving Code Completion has been selected for this year's GSoC. Some of you might know me from the 2 ESUGs I was at or maybe remember me previously doing GSoC in 2017, in any case I'm very happy to have been given this opportunity and I look forward to working with you! I started working on code completion last year during my internship at RMoD with Marcus and Stef, and I really want to make even more progress with code completion this summer and properly implement it inside Pharo as one of the options to use. You can read more about what has been done last summer and what is yet to be done this summer in my proposal (see attached). If you have any feedback or questions, don't hesitate to email me. Help and suggestions throughout my work on the project will be incredibly welcome too, as there's a lot to figure out how to do best. If you are interested in updates or want to keep in touch, I'm also on twitter <https://twitter.com/myroslavarm>, and I have a blog <https://medium.com/@myroslavarm> where I used to post about my progress in the last GSoC and about my internship at RMoD, and I will be writing there this summer, too. I'll also try to be more active in the mailing list and on discord :) Cheers, Myroslava

1 0

[Pharo 8.0] Build #263: [Fork2]2938 - Fixing FFIConstantHandleType externalType wrong in 64 bit
by ci-pharo-ci-jenkins2＠inria.fr May 9, 2019

May 9, 2019

There is a new Pharo build available! The status of the build #263 was: SUCCESS. The Pull Request #3252 was integrated: "[Fork2]2938 - Fixing FFIConstantHandleType externalType wrong in 64 bit " Pull request url: https://github.com/pharo-project/pharo/pull/3252 Issue Url: https://github.com/pharo-project/pharo/issues/2938 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #262: 2261-DarkTheme-depends-on-Shout
by ci-pharo-ci-jenkins2＠inria.fr May 9, 2019

May 9, 2019

There is a new Pharo build available! The status of the build #262 was: SUCCESS. The Pull Request #3210 was integrated: "2261-DarkTheme-depends-on-Shout" Pull request url: https://github.com/pharo-project/pharo/pull/3210 Issue Url: https://github.com/pharo-project/pharo/issues/2261 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 8.0] Build #261: 2598-isSpecial-is-not-an-explicit-name-for-a-method
by ci-pharo-ci-jenkins2＠inria.fr May 9, 2019

May 9, 2019

There is a new Pharo build available! The status of the build #261 was: FAILURE. The Pull Request #3318 was integrated: "2598-isSpecial-is-not-an-explicit-name-for-a-method" Pull request url: https://github.com/pharo-project/pharo/pull/3318 Issue Url: https://github.com/pharo-project/pharo/issues/2598 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0