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

Re: [Pharo-dev] proposal - contribution workflow - PR-only for pre-fixed Issues

by Cyril Ferlicot

On Sun, Jul 14, 2019 at 10:31 AM Ben Coman <btc(a)openinworld.com> wrote: > Some improvements are often discovered, fixed and submitted all in the > same moment - prior to their being an existing Issue logged. > When we were using MCZ files that had no facility to hang a discussion on > them, > it was a good policy that **every** contribution required an Issue as a > place for discussion and approval. > However we are now using Pull Requests that provide such a facility for > discussion and approval. > > There is not much difference between an "Issue" and a "PR" - indeed their > index numbers are interleaved. > So when we already have a PR ready to go, it seems redundant to first > create an matching Issue just to have something to close. > It seems particularly redundant when an Issues is created and closed > within the same hour a PR is submitted and unnecessary double-handling. > > So I propose that pre-fixed-issues that a submitted with a code > contribution require a PR-only > and "Issues" are left for reports without an immediate fix that require > longer term visibility. > > I agree! > cheers -ben > > P.S. Thank you Torsten for your stream of small fixes. > > > [image: x.png] > -- Cyril Ferlicot https://ferlicot.fr

July 15, 2019

Re: [Pharo-dev] Testing "Weekly Digest" for GitHub

by Marcus Denker

Somehow it did not make a report this sundayâ¦ to debug. > On 8 Jul 2019, at 10:49, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > There is a ProBot that creates an issue with a weekly summary. > > By installing it for testing, we got the first report: > > Weekly Digest (1 July, 2019 - 8 July, 2019) > https://github.com/pharo-project/pharo/issues/381 > > > I will do some fine-tuning (e.g. disable commits and star-gazers) later. > We then can let it run for some weeks and see if it is useful or not. > > Marcus

July 15, 2019

[ANN] Pharo Newsletter June 2019

by Marcus Denker

The Pharo Newsletter for June 2019 was send to subscribers. It is now available online: https://mailchi.mp/pharo/pharo-newsletter-june-2019 Find all the older newsletters in the archive: http://newsletter.pharo.org. You can subscribe to get the newsletter to get it as soon as is released. The July newsletter will be out soon (this week) Marcus

July 15, 2019

[Pharo 8.0] Build #493: 3897-unify-name-of-RGMethodDefinition-and-CompiledMethod

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

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

July 15, 2019

[Pharo 8.0] Build #492: FAILURE

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

There is a new Pharo build available! The status of the build #492 was: FAILURE. Could not extract further issue information from commit message: Update weekly-digest.yml Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 15, 2019

[Pharo 8.0] Build #491: Cleanups in WorldMorph

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

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

July 14, 2019

Re: [Pharo-dev] proposal - contribution workflow - PR-only for pre-fixed Issues

by Esteban Lorenzano

Hi, +1 > On 14 Jul 2019, at 11:26, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Hi Ben, > > I agree. > > In general, I too do see that this artificial separation is adding little/no value. > This would also simplify a bit the build scripts: instead of having to parse the PR name to get the issue number, we could just use the available PR number. > >> El 14 jul 2019, a las 10:30, Ben Coman <btc(a)openinworld.com> escribiÃ³: >> >> Some improvements are often discovered, fixed and submitted all in the same moment - prior to their being an existing Issue logged. >> When we were using MCZ files that had no facility to hang a discussion on them, >> it was a good policy that **every** contribution required an Issue as a place for discussion and approval. >> However we are now using Pull Requests that provide such a facility for discussion and approval. >> >> There is not much difference between an "Issue" and a "PR" - indeed their index numbers are interleaved. >> So when we already have a PR ready to go, it seems redundant to first create an matching Issue just to have something to close. >> It seems particularly redundant when an Issues is created and closed within the same hour a PR is submitted and unnecessary double-handling. >> >> So I propose that pre-fixed-issues that a submitted with a code contribution require a PR-only >> and "Issues" are left for reports without an immediate fix that require longer term visibility. >> >> cheers -ben >> >> P.S. Thank you Torsten for your stream of small fixes. >> >> >> <x.png> > >

July 14, 2019

Re: [Pharo-dev] proposal - contribution workflow - PR-only for pre-fixed Issues

by Guillermo Polito

Hi Ben, I agree. In general, I too do see that this artificial separation is adding little/no value. This would also simplify a bit the build scripts: instead of having to parse the PR name to get the issue number, we could just use the available PR number. > El 14 jul 2019, a las 10:30, Ben Coman <btc(a)openinworld.com> escribiÃ³: > > Some improvements are often discovered, fixed and submitted all in the same moment - prior to their being an existing Issue logged. > When we were using MCZ files that had no facility to hang a discussion on them, > it was a good policy that **every** contribution required an Issue as a place for discussion and approval. > However we are now using Pull Requests that provide such a facility for discussion and approval. > > There is not much difference between an "Issue" and a "PR" - indeed their index numbers are interleaved. > So when we already have a PR ready to go, it seems redundant to first create an matching Issue just to have something to close. > It seems particularly redundant when an Issues is created and closed within the same hour a PR is submitted and unnecessary double-handling. > > So I propose that pre-fixed-issues that a submitted with a code contribution require a PR-only > and "Issues" are left for reports without an immediate fix that require longer term visibility. > > cheers -ben > > P.S. Thank you Torsten for your stream of small fixes. > > > <x.png>

July 14, 2019

proposal - contribution workflow - PR-only for pre-fixed Issues

by Ben Coman

Some improvements are often discovered, fixed and submitted all in the same moment - prior to their being an existing Issue logged. When we were using MCZ files that had no facility to hang a discussion on them, it was a good policy that **every** contribution required an Issue as a place for discussion and approval. However we are now using Pull Requests that provide such a facility for discussion and approval. There is not much difference between an "Issue" and a "PR" - indeed their index numbers are interleaved. So when we already have a PR ready to go, it seems redundant to first create an matching Issue just to have something to close. It seems particularly redundant when an Issues is created and closed within the same hour a PR is submitted and unnecessary double-handling. So I propose that pre-fixed-issues that a submitted with a code contribution require a PR-only and "Issues" are left for reports without an immediate fix that require longer term visibility. cheers -ben P.S. Thank you Torsten for your stream of small fixes. [image: x.png]

July 14, 2019

[Pharo 8.0] Build #490: Move registerAsExternalResource from UFFI to Deprecated80

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

There is a new Pharo build available! The status of the build #490 was: FAILURE. The Pull Request #3918 was integrated: "Move registerAsExternalResource from UFFI to Deprecated80" Pull request url: https://github.com/pharo-project/pharo/pull/3918 Issue Url: https://github.com/pharo-project/pharo/issues/3917 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

July 14, 2019