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

[Pharo 8.0] Build #199: More debugger tests

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

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

March 29, 2019

[Pharo 8.0] Build #198: 2980-Rubric-setTextAndAccept-is-missing-to-RubPluggable

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

There is a new Pharo build available! The status of the build #198 was: SUCCESS. The Pull Request #3103 was integrated: "2980-Rubric-setTextAndAccept-is-missing-to-RubPluggable" Pull request url: https://github.com/pharo-project/pharo/pull/3103 Issue Url: https://github.com/pharo-project/pharo/issues/2980 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 29, 2019

[Pharo 8.0] Build #197: 2959-Epicea-doesnt-reload-events-in-the-correct-order

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

There is a new Pharo build available! The status of the build #197 was: FAILURE. The Pull Request #3097 was integrated: "2959-Epicea-doesnt-reload-events-in-the-correct-order" Pull request url: https://github.com/pharo-project/pharo/pull/3097 Issue Url: https://github.com/pharo-project/pharo/issues/2959 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 29, 2019

[Pharo 8.0] Build #196: 2685-Some-tests-for-FileReferences-use-a-publicTest-pragma

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

There is a new Pharo build available! The status of the build #196 was: SUCCESS. The Pull Request #3094 was integrated: "2685-Some-tests-for-FileReferences-use-a-publicTest-pragma" Pull request url: https://github.com/pharo-project/pharo/pull/3094 Issue Url: https://github.com/pharo-project/pharo/issues/2685 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 29, 2019

[Pharo 8.0] Build #195: 3038-Simplify-Slots-that-use-base-slot

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

There is a new Pharo build available! The status of the build #195 was: SUCCESS. The Pull Request #3043 was integrated: "3038-Simplify-Slots-that-use-base-slot" Pull request url: https://github.com/pharo-project/pharo/pull/3043 Issue Url: https://github.com/pharo-project/pharo/issues/3038 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 29, 2019

[Pharo 8.0] Build #194: Proper name for testisDefinedAsPackageOrSubPackageInMC

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

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

March 29, 2019

[Pharo 8.0] Build #193: 2141-Spotter-should-use-the-current-theme-instead-of-creating-its-own-theme-classes

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

There is a new Pharo build available! The status of the build #193 was: FAILURE. The Pull Request #3071 was integrated: "2141-Spotter-should-use-the-current-theme-instead-of-creating-its-own-theme-classes" Pull request url: https://github.com/pharo-project/pharo/pull/3071 Issue Url: https://github.com/pharo-project/pharo/issues/2141 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 29, 2019

[Pharo 8.0] Build #192: 3059-TestAsserterassertdescriptionresumable-should-be-refactored-to-use-guard-clause

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

There is a new Pharo build available! The status of the build #192 was: FAILURE. The Pull Request #3060 was integrated: "3059-TestAsserterassertdescriptionresumable-should-be-refactored-to-use-guard-clause" Pull request url: https://github.com/pharo-project/pharo/pull/3060 Issue Url: https://github.com/pharo-project/pharo/issues/3059 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 29, 2019

[Pharo 8.0] Build #191: 3044-tests-for-ComputedSlot

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

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

March 29, 2019

Re: [Pharo-dev] Issue Tracker: enabled Projects (Boards)

by Marcus Denker

I moved them all to the Project level https://github.com/orgs/pharo-project/projects <https://github.com/orgs/pharo-project/projects> >>> >>>> On 18 Mar 2019, at 08:27, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >>>> >>>> Hi, >>>> >>>> We enabled the GitHub âProjectsâ feature for the pharo repo: >>>> >>>> https://github.com/pharo-project/pharo/projects <https://github.com/pharo-project/pharo/projects> >>>> >>>> >>>> The idea is that one can add as many âKanbanâ style boards as one wants. >>>> issues and pull requests can be added, as well as simple cards that are not yet issues. >>>> >>>> This is quite nice as an issue tracker gets very confusing and overwhelming as soon as there >>>> are >500 issues. >>>> >>>> With these boards, we can create âviewsâ on this sea of issues. >>>> >>>> I created for now: >>>> >>>> -> some board related to specific parts of the system (e.g. Traits or Reflectivity) >>>> example: https://github.com/pharo-project/pharo/projects/11 <https://github.com/pharo-project/pharo/projects/11> >>>> -> "Pharo7 Backportingâ >>>> https://github.com/pharo-project/pharo/projects/12 <https://github.com/pharo-project/pharo/projects/12> >>>> -> "Simple Issues for Beginnersâ >>>> https://github.com/pharo-project/pharo/projects/14 <https://github.com/pharo-project/pharo/projects/14> >>>> Here the feature to be able to put things that are not yet issue tracker entries seems very useful >>>> >>>> >>>> I think this can be quite niceâ¦ we should add more Projects as soon as we find that they make sense >>>> and should move issues there. >>>> >>>> Marcus >>> >> >

March 29, 2019