- Pharo-dev - lists.pharo.org

[ANN] Next Pharo Sprint: Aug 31
by Marcus Denker Aug. 22, 2018

Aug. 22, 2018

We will organize a Pharo sprint / Moose dojo Aug 31, starting at 10:00am. (Local Time Paris). Goals of this sprint: â¢ Pharo 7 issues Remote Sprint: Remotely, you can join us on Discord. During the sprint, we synchronize local and remote Pharo sprinters: http://pharo.org/contribute-events <http://pharo.org/contribute-events> Known Local Sprint meetings Lille/France: It will be at the Inria Lille, Building B, third floor (RMoD offices). As the building is not open to the public, please contact us before if you plan to come https://association.pharo.org/event-2973616 <https://association.pharo.org/event-2973616>

1 0

Reducing the cost of documentation
by Alistair Grant Aug. 21, 2018

Aug. 21, 2018

Hi Everyone, The topic of documentation recently came up again on the squeak list and it made me wonder about some of the blocks that currently prevent more contributions to in-image documentation. One of the things holding back the in-image documentation is that the cost of contributing is too high: apart from actually making the change we currently have to (maybe) open an issue, create a branch, commit and open a PR. Someone with commit privileges then has to review the PR enough and decide to merge it. We then need to manually delete the branch some time later. This is one of the reasons that wikis have been successful, they lower the cost of making changes. We could extend iceberg to automatically submit PRs for documentation only commits (it could be a separate option, so that the doco only requirement is enforced), and set up github to auto-accept the PR. Modifying in-image documentation would then become a few extra clicks, significantly lowering the cost. I'm not familiar with Jenkins, or any other CI system, but hunting around google it looks like it may be possible to directly implement this, if not there are services such as https://mergify.io/ which advertise being able to do this by using flags in the CI to determine whether the PR should be merged (disclaimer, I've never looked at mergify.io, just found it while thinking about this). Thoughts? Cheers, Alistair

2 2

[Pharo 7.0-dev] Build #1190: 22352 Better tagging in ReflectionMirrors-Primitives and related tests
by ci-pharo-ci-jenkins2＠inria.fr Aug. 21, 2018

Aug. 21, 2018

There is a new Pharo build available! The status of the build #1190 was: SUCCESS. The Pull Request #1708 was integrated: "22352 Better tagging in ReflectionMirrors-Primitives and related tests" Pull request url: https://github.com/pharo-project/pharo/pull/1708 Issue Url: https://pharo.fogbugz.com/f/cases/22352 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1189: 22293-Sendersimplementors-searching-can-cause-DNU-in-Rubric
by ci-pharo-ci-jenkins2＠inria.fr Aug. 21, 2018

Aug. 21, 2018

There is a new Pharo build available! The status of the build #1189 was: SUCCESS. The Pull Request #1668 was integrated: "22293-Sendersimplementors-searching-can-cause-DNU-in-Rubric" Pull request url: https://github.com/pharo-project/pharo/pull/1668 Issue Url: https://pharo.fogbugz.com/f/cases/22293 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[update 6.0] #60543
by Marcus Denker Aug. 21, 2018

Aug. 21, 2018

60543 ----- 22346 #mustBeBooleanDeOptimizeIn: needs to clean semantic annotation before recompile https://pharo.fogbugz.com/f/cases/22346 22356 CompiledMethod: #methodNode should reuse #parseTree https://pharo.fogbugz.com/f/cases/22356

1 0

[Pharo 7.0-dev] Build #1188: 22324-Wrong-implementation-of-stop-in-RBMethodNode
by ci-pharo-ci-jenkins2＠inria.fr Aug. 21, 2018

Aug. 21, 2018

There is a new Pharo build available! The status of the build #1188 was: FAILURE. The Pull Request #1713 was integrated: "22324-Wrong-implementation-of-stop-in-RBMethodNode" Pull request url: https://github.com/pharo-project/pharo/pull/1713 Issue Url: https://pharo.fogbugz.com/f/cases/22324 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1187: 22355-TestRunner-got-broken-because-baseClass-is-not-baseClass
by ci-pharo-ci-jenkins2＠inria.fr Aug. 21, 2018

Aug. 21, 2018

There is a new Pharo build available! The status of the build #1187 was: SUCCESS. The Pull Request #1710 was integrated: "22355-TestRunner-got-broken-because-baseClass-is-not-baseClass" Pull request url: https://github.com/pharo-project/pharo/pull/1710 Issue Url: https://pharo.fogbugz.com/f/cases/22355 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1186: 22340-Cleanup-String-new-comment
by ci-pharo-ci-jenkins2＠inria.fr Aug. 21, 2018

Aug. 21, 2018

There is a new Pharo build available! The status of the build #1186 was: FAILURE. The Pull Request #1712 was integrated: "22340-Cleanup-String-new-comment" Pull request url: https://github.com/pharo-project/pharo/pull/1712 Issue Url: https://pharo.fogbugz.com/f/cases/22340 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1185: 22347-Prama-ivar-keyword-should-be-selector
by ci-pharo-ci-jenkins2＠inria.fr Aug. 20, 2018

Aug. 20, 2018

There is a new Pharo build available! The status of the build #1185 was: SUCCESS. The Pull Request #1705 was integrated: "22347-Prama-ivar-keyword-should-be-selector" Pull request url: https://github.com/pharo-project/pharo/pull/1705 Issue Url: https://pharo.fogbugz.com/f/cases/22347 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0

[Pharo 7.0-dev] Build #1184: 22349-add-test-for-argsAsArray
by ci-pharo-ci-jenkins2＠inria.fr Aug. 20, 2018

Aug. 20, 2018

There is a new Pharo build available! The status of the build #1184 was: FAILURE. The Pull Request #1706 was integrated: "22349-add-test-for-argsAsArray" Pull request url: https://github.com/pharo-project/pharo/pull/1706 Issue Url: https://pharo.fogbugz.com/f/cases/22349 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

1 0