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

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

by Norbert Hartl

> Am 30.01.2019 um 16:13 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > > > >> On 3 Oct 2018, at 07:43, monty <monty2(a)programmer.net> wrote: >> >> I am the principal maintainer of those projects, but any PharoExtras dev can contribute. And the blog below (which I plan on updating) provides additional information on them. > > Has there been any progress in this area ? > > It would be really great if this important project moved to GitHub. > +100 Norbert

Jan. 30, 2019

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

by Sven Van Caekenberghe

> On 3 Oct 2018, at 07:43, monty <monty2(a)programmer.net> wrote: > > I am the principal maintainer of those projects, but any PharoExtras dev can contribute. And the blog below (which I plan on updating) provides additional information on them. Has there been any progress in this area ? It would be really great if this important project moved to GitHub. Sven

Jan. 30, 2019

[Pharo 8.0] Build #45: add g prefix to keep code compatible with git describes

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

There is a new Pharo build available! The status of the build #45 was: SUCCESS. The Pull Request #2417 was integrated: "add g prefix to keep code compatible with git describes" Pull request url: https://github.com/pharo-project/pharo/pull/2417 Issue Url: https://pharo.fogbugz.com/f/cases/2379 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 30, 2019

[ANN] Pharo open documentation

by Cyril Ferlicot

Hi everyone! With some other members of the community we are proud to announce a new effort on Pharo documentation. We launched an organization pharo-open-documentation which is a user-maintained documentation related to Pharo environment, language, and libraries. Currently it has three main projects: - pharo-wiki : Wiki related to the Pharo programming language and environment. - awesome-pharo : A collection of awesome Pharo libraries, tools, frameworks and software. We want to make this project a reference in https://github.com/sindresorhus/awesome - awesome-pharo-ml : List of projects, books, booklets, papers, and applications related to machine learning, AI, data science in Pharo. Contributions are welcomed! If you own a cool project in Pharo others could use in their own projects, send us a PR to awesome-pharo! If you have knowledge on Pharo or projects of Pharo, we would be glad if you could contribute to the pharo-wiki! Don't forget to read the contribution guidelines. ;) We opened a Twitter to announce new entries on the pharo-wiki. https://twitter.com/PharoOpen Have a nice day! -- Cyril Ferlicot https://ferlicot.fr

Jan. 30, 2019

[Pharo 8.0] Build #44: 2414-failing-testAndMakeSureSuperSetupIsCalledAsFirstMessageInSetupMethodsOfTestCases

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

There is a new Pharo build available! The status of the build #44 was: SUCCESS. The Pull Request #2415 was integrated: "2414-failing-testAndMakeSureSuperSetupIsCalledAsFirstMessageInSetupMethodsOfTestCases" Pull request url: https://github.com/pharo-project/pharo/pull/2415 Issue Url: https://pharo.fogbugz.com/f/cases/2414 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 30, 2019

Re: [Pharo-dev] Contribute to pharo8.0 ?

by Guillermo Polito

Hi, there is an issue for this problem, https://github.com/pharo-project/pharo/issues/2379 We have identified the cause, I'll propose a fix now On Wed, Jan 30, 2019 at 8:44 AM ducasse <stepharo(a)netcourrier.com> wrote: > > > > There is currently a bug eating one character of the commit hash. So > > Iceberg does not find the hash and thinks we need a fetch. So currently > > we need to checkout Pharo8.0 in order to be in a good state :( > > OOPs is there a bug entry? > > > >> I also don't understand how to make an issue branch for > >> > >> https://github.com/pharo-project/pharo/issues/2395 > >> > >> Is it Iceberg > Pharo > Create new branch for issue or Iceberg > Github > > Create new branch for issue ? > > > > Just create a branch and choose the option to create a branch from a > > Github option. > > > > The other one was for Manuscript and is now useless for Pharo 8. I > > opened an issue in Iceberg to remove it but I did not got the time to > > contribute the change. > > > >> What is the difference ? > >> What about the Remote ? > >> Can I work with only an issue on GitHub ? > >> > > > > Yes! > > > > What I am doing currently: > > > > - Open an issue XX > > - Sync my fork Pharo8.0 branch via command line (This is optional and > > can also be done in Pharo. I just do it via command line because I like > > it better that way) > > how do you do it? Pull? > > > - Download a Pharo 8 image > > - Checkout the Pharo8.0 branch to get in a clean state because of the > > hash eating bug I mentioned earlier > > - Create a new branch from a github issue of the pharo remote > > - Do the changes and commit. I add `Fixes #XX` in the commit message to > > close automatically the issue when the PR is merged. > > - Push to my remote > > - Open a PR against Pharo8.0 through Iceberg > GitHub > Create new pull > > request > > and checkout the pharo 8 branch to fix the next one. > > > >> Is the documentation > >> > >> https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo > >> > >> really up to date ? > >> > > > > No > > > > We should correct the hash eating bug before updating it I think. > > > >> Sven > >> > >> > > > > > > -- > > Cyril Ferlicot > > https://ferlicot.fr > > > > > > -- Guille Polito Research Engineer Centre de Recherche en Informatique, Signal et Automatique de Lille CRIStAL - UMR 9189 French National Center for Scientific Research - *http://www.cnrs.fr <http://www.cnrs.fr>* *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Jan. 30, 2019

[Pharo 7.0] Build #146: Revert "18764-Remove-external-dependencies-from-Kernel-Tests-"

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

There is a new Pharo build available! The status of the build #146 was: SUCCESS. The Pull Request #2411 was integrated: "Revert "18764-Remove-external-dependencies-from-Kernel-Tests-"" Pull request url: https://github.com/pharo-project/pharo/pull/2411 Issue Url: https://pharo.fogbugz.com/f/cases/revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Jan. 30, 2019

Re: [Pharo-dev] Contribute to pharo8.0 ?

by ducasse

> > There is currently a bug eating one character of the commit hash. So > Iceberg does not find the hash and thinks we need a fetch. So currently > we need to checkout Pharo8.0 in order to be in a good state :( OOPs is there a bug entry? > >> I also don't understand how to make an issue branch for >> >> https://github.com/pharo-project/pharo/issues/2395 >> >> Is it Iceberg > Pharo > Create new branch for issue or Iceberg > Github > Create new branch for issue ? > > Just create a branch and choose the option to create a branch from a > Github option. > > The other one was for Manuscript and is now useless for Pharo 8. I > opened an issue in Iceberg to remove it but I did not got the time to > contribute the change. > >> What is the difference ? >> What about the Remote ? >> Can I work with only an issue on GitHub ? >> > > Yes! > > What I am doing currently: > > - Open an issue XX > - Sync my fork Pharo8.0 branch via command line (This is optional and > can also be done in Pharo. I just do it via command line because I like > it better that way) how do you do it? Pull? > - Download a Pharo 8 image > - Checkout the Pharo8.0 branch to get in a clean state because of the > hash eating bug I mentioned earlier > - Create a new branch from a github issue of the pharo remote > - Do the changes and commit. I add `Fixes #XX` in the commit message to > close automatically the issue when the PR is merged. > - Push to my remote > - Open a PR against Pharo8.0 through Iceberg > GitHub > Create new pull > request and checkout the pharo 8 branch to fix the next one. > >> Is the documentation >> >> https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo >> >> really up to date ? >> > > No > > We should correct the hash eating bug before updating it I think. > >> Sven >> >> > > > -- > Cyril Ferlicot > https://ferlicot.fr >

Jan. 30, 2019

Re: [Pharo-dev] Contribute to pharo8.0 ?

by ducasse

Hi Sven > Hi, > > I am trying my first contribution / PR to pharo8.0 Excellent > I started with a latest zeroconfig 8.0 image/vm and I deleted my old fork and made a new one. > > But repairing the repository by fetching does not bring it to the detached state Often I do repair and I create a default branch. I call it bottom* > I also don't understand how to make an issue branch for > > https://github.com/pharo-project/pharo/issues/2395 > > Is it Iceberg > Pharo > Create new branch for issue or Iceberg > Github > Create new branch for issue ? > What is the difference ? I think that when you do a icebveg github then you you will query the published issues. with the other you just create a branch > What about the Remote ? you should point to the pharo remote and not your fork so that you do not get an invalid > Can I work with only an issue on GitHub ? No you can create a branch with your own name. > Is the documentation > > https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo > > really up to date ? probably not. > > Sven > >

Jan. 30, 2019

Re: [Pharo-dev] Contribute to pharo8.0 ?

by Cyril Ferlicot D.

Le 29/01/2019 Ã 23:47, Sven Van Caekenberghe a Ã©critÂ : > Hi, > > I am trying my first contribution / PR to pharo8.0 > > I started with a latest zeroconfig 8.0 image/vm and I deleted my old fork and made a new one. > > But repairing the repository by fetching does not bring it to the detached state > Hi, There is currently a bug eating one character of the commit hash. So Iceberg does not find the hash and thinks we need a fetch. So currently we need to checkout Pharo8.0 in order to be in a good state :( > I also don't understand how to make an issue branch for > > https://github.com/pharo-project/pharo/issues/2395 > > Is it Iceberg > Pharo > Create new branch for issue or Iceberg > Github > Create new branch for issue ? Just create a branch and choose the option to create a branch from a Github option. The other one was for Manuscript and is now useless for Pharo 8. I opened an issue in Iceberg to remove it but I did not got the time to contribute the change. > What is the difference ? > What about the Remote ? > Can I work with only an issue on GitHub ? > Yes! What I am doing currently: - Open an issue XX - Sync my fork Pharo8.0 branch via command line (This is optional and can also be done in Pharo. I just do it via command line because I like it better that way) - Download a Pharo 8 image - Checkout the Pharo8.0 branch to get in a clean state because of the hash eating bug I mentioned earlier - Create a new branch from a github issue of the pharo remote - Do the changes and commit. I add `Fixes #XX` in the commit message to close automatically the issue when the PR is merged. - Push to my remote - Open a PR against Pharo8.0 through Iceberg > GitHub > Create new pull request > Is the documentation > > https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo > > really up to date ? > No We should correct the hash eating bug before updating it I think. > Sven > > -- Cyril Ferlicot https://ferlicot.fr

Jan. 29, 2019