December 2018 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Happy new year!

by Stephane Ducasse

Thanks! I wish a lot of success and health to everybody. I like to think that because we are a community we are a lot more powerful than alone. So I wish you also a lot of fruitful collaborations. And I'm confident that 2019 will be even better than 2018. Stef On Mon, Dec 31, 2018 at 8:49 PM Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > > > On 31 Dec 2018, at 19:02, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > Hi list, > > > > Just that. > > I wish you all have a happy new year, and may it be even better than this one :) > > > > Esteban > > Yes, I wish everybody all the best for 2019 ! > > Sven

Dec. 31, 2018

Re: [Pharo-dev] Happy new year!

by Sven Van Caekenberghe

> On 31 Dec 2018, at 19:02, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi list, > > Just that. > I wish you all have a happy new year, and may it be even better than this one :) > > Esteban Yes, I wish everybody all the best for 2019 ! Sven

Dec. 31, 2018

Happy new year!

by Esteban Lorenzano

Hi list, Just that. I wish you all have a happy new year, and may it be even better than this one :) Esteban

Dec. 31, 2018

Re: [Pharo-dev] New book: Pharo with Style

by Benoit St-Jean

Besides, I forgot to add one comment : you should have guidelines for protocol naming.Â It's not critical per se but I find it quite annoying to look for stuff in "enumerating" when it's been put in "printing" !Â loll On 2018-12-31 03:51, Stephane Ducasse wrote: > Thanks! Thanks! > I will go over it (now laying on my back :(( stupid muscles strike back!) > > On Mon, Dec 31, 2018 at 2:18 AM Benoit St-Jean <bstjean(a)yahoo.com> wrote: >> On 2018-12-30 16:13, Stephane Ducasse wrote: >>> Hello Fellow Pharoers >>> >>> I'm happy to announce a new little book to improve the culture around Pharo. >>> I will revise it in the future so you can feel free to send feedback >>> and pull requests >>> to https://github.com/SquareBracketAssociates/Booklet-PharoWithStyle >>> >>> Stef >>> >>> "The best way to predict the future is to invent" so I do it. >> StÃ©phane, >> >> You'll find, attached, a revised PDF version with my comments. >> >> >> >> -- >> ----------------- >> BenoÃ®t St-Jean >> Yahoo! Messenger: bstjean >> Twitter: @BenLeChialeux >> Pinterest: benoitstjean >> Instagram: Chef_Benito >> IRC: lamneth >> Blogue: endormitoire.wordpress.com >> "A standpoint is an intellectual horizon of radius zero". (A. Einstein) >> -- ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero". (A. Einstein)

Dec. 31, 2018

Re: [Pharo-dev] New book: Pharo with Style

by Stephane Ducasse

Thanks! Thanks! I will go over it (now laying on my back :(( stupid muscles strike back!) On Mon, Dec 31, 2018 at 2:18 AM Benoit St-Jean <bstjean(a)yahoo.com> wrote: > > On 2018-12-30 16:13, Stephane Ducasse wrote: > > Hello Fellow Pharoers > > > > I'm happy to announce a new little book to improve the culture around Pharo. > > I will revise it in the future so you can feel free to send feedback > > and pull requests > > to https://github.com/SquareBracketAssociates/Booklet-PharoWithStyle > > > > Stef > > > > "The best way to predict the future is to invent" so I do it. > > StÃ©phane, > > You'll find, attached, a revised PDF version with my comments. > > > > -- > ----------------- > BenoÃ®t St-Jean > Yahoo! Messenger: bstjean > Twitter: @BenLeChialeux > Pinterest: benoitstjean > Instagram: Chef_Benito > IRC: lamneth > Blogue: endormitoire.wordpress.com > "A standpoint is an intellectual horizon of radius zero". (A. Einstein) >

Dec. 31, 2018

Esteban's ChangeLog week of 24 December 2018

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 24 December 2018 to 30 December 2018. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=24/12/2018&to=30/12/2018 ChangeLog ========= 27 December 2018: ----------------- * Opened Pharo8.0 development * branch was already opened by Stef :) * opened issue tracker * updated documents to point to it * sent mails to list TODO: Update videos (we needed new ones anyway) cheers! Esteban

Dec. 31, 2018

Re: [Pharo-dev] New book: Pharo with Style

by Benoit St-Jean

On 2018-12-30 16:13, Stephane Ducasse wrote: > Hello Fellow Pharoers > > I'm happy to announce a new little book to improve the culture around Pharo. > I will revise it in the future so you can feel free to send feedback > and pull requests > to https://github.com/SquareBracketAssociates/Booklet-PharoWithStyle > > Stef > > "The best way to predict the future is to invent" so I do it. StÃ©phane, You'll find, attached, a revised PDF version with my comments. -- ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean Instagram: Chef_Benito IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero". (A. Einstein)

Dec. 31, 2018

New book: Pharo with Style

by Stephane Ducasse

Hello Fellow Pharoers I'm happy to announce a new little book to improve the culture around Pharo. I will revise it in the future so you can feel free to send feedback and pull requests to https://github.com/SquareBracketAssociates/Booklet-PharoWithStyle Stef "The best way to predict the future is to invent" so I do it.

Dec. 30, 2018

[Pharo 7.0] Build #91: Revert "21876 Re-evaluating of class definition with slots cleans the class instance variables"

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

There is a new Pharo build available! The status of the build #91 was: FAILURE. The Pull Request #2145 was integrated: "Revert "21876 Re-evaluating of class definition with slots cleans the class instance variables"" Pull request url: https://github.com/pharo-project/pharo/pull/2145 Issue Url: https://pharo.fogbugz.com/f/cases/revert Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

Dec. 30, 2018

Re: [Pharo-dev] About contribution process, people participation and communication (WAS: Re: [ANN] Pharo 8.0 development started)

by Ben Coman

On Sun, 30 Dec 2018 at 23:28, Esteban Lorenzano via Pharo-dev < pharo-dev(a)lists.pharo.org> wrote: > > Now, while the general direction was explained, I think I failed to > communicate several things. > For what I can think at this moment (for sure there are a lot more): > > - I failed to communicate that opening Pharo 8.0 branch didnât mean > closing Pharo 7.0 development, just to allow people doing big changes to > merge them. > - I failed to communicate correctly that having a release candidate (rc1) > meant âcode freezeâ (and then forbidding new changes except bug fixing). > Thanks for acknowledging this Esteban. In spite of the communication issue, the point I'd make in support of this arrangement is that historically we've done poorly with code-freezes, or even the lesser strength feature-freezes leading up to a release. A code freeze can be discouraging when integration of new features are delayed and can weaken such the code freeze. Opening the next-version-dev branch when the current-version freezes for release-candidate seems to facilitate pre-release stability - though the risk though of mind-share drifting to the next-version-dev branch needs to be managed. cheers -ben

Dec. 30, 2018