Smalltalk › Pharo › Pharo Smalltalk Developers

Should we updated UpdatedPharoByExample for Pharo 5?

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

5 messages Options

CyrilFerlicot

Should we updated UpdatedPharoByExample for Pharo 5?

Currently all issues are opened to update PBE for Pharo4. Since Pharo5
is out should we give up on Pharo4 version and focus on Pharo5?

Since we don't have enough man power to do both I think we should just
tag the current version with a Pharo4 tag even if everything is not up
to date and begin to adapt it for Pharo5.

--
Cyril Ferlicot

http://www.synectique.eu

165 Avenue Bretagne
Lille 59000 France

signature.asc (836 bytes) Download Attachment

kilon.alios

Re: Should we updated UpdatedPharoByExample for Pharo 5?

UPBE always targets the current stable version of Pharo. In this case is Pharo 5 , a year ago was Pharo 4 and in a year Pharo 6. The tag is an idea I also promoted. We do have more than enough man power unfortunately a tiny fraction of it contributes to UPBE. I am not complaining, its free software people should choose what they like doing .

On Sat, May 21, 2016 at 4:02 PM Cyril Ferlicot D. <[hidden email]> wrote:

Currently all issues are opened to update PBE for Pharo4. Since Pharo5
is out should we give up on Pharo4 version and focus on Pharo5?

Since we don't have enough man power to do both I think we should just
tag the current version with a Pharo4 tag even if everything is not up
to date and begin to adapt it for Pharo5.

--
Cyril Ferlicot

http://www.synectique.eu

165 Avenue Bretagne
Lille 59000 France

stepharo

Re: Should we updated UpdatedPharoByExample for Pharo 5?

In reply to this post by CyrilFerlicot

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

Le 21/5/16 à 15:00, Cyril Ferlicot D. a écrit :
> Currently all issues are opened to update PBE for Pharo4. Since Pharo5
> is out should we give up on Pharo4 version and focus on Pharo5?
>
> Since we don't have enough man power to do both I think we should just
> tag the current version with a Pharo4 tag even if everything is not up
> to date and begin to adapt it for Pharo5.
>

CyrilFerlicot

Re: Should we updated UpdatedPharoByExample for Pharo 5?

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.

--
Cyril Ferlicot

http://www.synectique.eu

165 Avenue Bretagne
Lille 59000 France

signature.asc (836 bytes) Download Attachment

stepharo

Re: 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.
>