Re: [Pharo-dev] Should we updated UpdatedPharoByExample for Pharo 5?

but the current version is not about pharo40 but 50. Le 21/5/16 à 18:29, Cyril Ferlicot D. a écrit :

Le 21/05/2016 15:56, stepharo a écrit :

...

Hi cyril

I think that we should find the right balance between details that are specific to a version and stable parts.

Now I target Pharo 50. I think that the focus of Pharo 60 should be on external (new tools) but on stabilisation, speed up and

cleanup (and internal things like bootstrap).

Stef

Ok, so if nobody disagree I think we should tag the current version as Pharo 4. Mark the current Jenkins build as "Always keep artefact" and publish a link on the book's page.

I can do the two first steps but not the last.