Help us to have really cool Pharo 3 release!

Hi guys,

As you know, we are now in beta for Pharo 3.
That means we are just fixing bugs and improving stability (they are some attempts from some very impatient people to add yet new features, but so far we are managing them with the ability of a goal keeper  :) )

What we need now is your help! How?

1) Is NOW the moment of porting your projects to Pharo 3. Yes… is not stable, but it improves everyday and if you help us catching bugs, it will in march, when the release should happen)
2) Report BUGS. Yep… we still have many of them. Best way to report a bug is: to add a bug entry and to open a discussion in dev mailing list. Just one of both does not works fine because we are in the run, and: if you just open the bug, we can miss his importance, if you just start a thread, we are for sure owing to be covered of work and we will forget your important change. .
3) If you feel in the mood, you can fix some of your annoying bugs by yourself. With the introduction of Komitter (thanks Ben!) you don’t even need to work in a separate image… it can be fixed in your working image and you can send a SLICE with just the changes you want.
4) or you can just help us reviewing fixes (usually in status “Fix Reviewed By The Monkey”, they need to be moved to “Fix To Include”, and that in some cases (when is UI related, for instance) requires human intervention.

Don’t wait until tomorrow!
Pharo needs you TODAY!

cheers,
Esteban

I’ve started two weeks ago porting my first project to pharo3. Well, I don’t know the real name for the action because it was not a real porting. It just loaded in pharo3 without any interaction by me. Ok, I think this is called „installation“ :) Very nice!

Norbert

Am 04.01.2014 um 11:17 schrieb Esteban Lorenzano <[hidden email]>:

On 04 Jan 2014, at 11:17, Esteban Lorenzano <[hidden email]> wrote:

> Hi guys,
>
> As you know, we are now in beta for Pharo 3.
> That means we are just fixing bugs and improving stability (they are some attempts from some very impatient people to add yet new features, but so far we are managing them with the ability of a goal keeper  :) )

nice metaphor! It made me think about maradona :) So from argentinian it means that we can also play football with our hands o:)


> What we need now is your help! How?
>
> 1) Is NOW the moment of porting your projects to Pharo 3. Yes… is not stable, but it improves everyday and if you help us catching bugs, it will in march, when the release should happen)
> 2) Report BUGS. Yep… we still have many of them. Best way to report a bug is: to add a bug entry and to open a discussion in dev mailing list. Just one of both does not works fine because we are in the run, and: if you just open the bug, we can miss his importance, if you just start a thread, we are for sure owing to be covered of work and we will forget your important change. .
> 3) If you feel in the mood, you can fix some of your annoying bugs by yourself. With the introduction of Komitter (thanks Ben!) you don’t even need to work in a separate image… it can be fixed in your working image and you can send a SLICE with just the changes you want.
> 4) or you can just help us reviewing fixes (usually in status “Fix Reviewed By The Monkey”, they need to be moved to “Fix To Include”, and that in some cases (when is UI related, for instance) requires human intervention.
>
> Don’t wait until tomorrow!
> Pharo needs you TODAY!

super!

>
> cheers,
> Esteban

>
> nice metaphor! It made me think about maradona :) So from argentinian it means that we can also play football with our hands o:)
>

And tons of cocaine :P

Ben

>
> Don’t wait until tomorrow!
> Pharo needs you TODAY!
>

I loaded my tools into Pharo 3.0 (Latest update: #30670). The Parts using NeoCSV and Roassal / RoassalProposals
are fine. But the tool has some dependencies to EyeSee which makes small problems. They are reproducible with
the ESExamples. The Diagrams are shown, but with an Exception "MessageNotUnderstood: MorphOpened>>diagramRenderer:".

BW,
Volkert

--
Volkert Barr
www.nivoba.de

"The more complex an object, the larger the investment in learning to use it, and the greater the resistance to abandon it."