As already said several times. For me, we have to:

1) Put ALL our effort and or priority to release the 1.0 stable. This means,
try to fix the 1.0 opened fixes.

2) Tag the 1.1 as UNSTABLE.

3) Remove 1.1 dev link from website and even do not create dev images using
1.1 for the moment. Peope should use 1.0 for their development. (this was
not my idea, adrian i think).

Cheers,

Mariano

On Mon, Dec 21, 2009 at 5:48 PM, Stéphane Ducasse <[email protected]
> wrote:

> sure no problem. Lukas.
> I sent the mail because this is an important point.
> I think that we should also understand what is a good amount of time
> between two releases.
>
> On Dec 21, 2009, at 12:20 PM, Lukas Renggli wrote:
>
> >> Lukas, is there a particular reason why you want/need your stuff to
> >> work also with 1.1?
> >
> > The initial trigger for this discussion was Stef asking me to use
> > #chooseOrRequestFrom: for creating protocols in OB. This method was a
> > recently added to morphic in Pharo 1.1 and is used in the old ST-80
> > browser to create new method protocols with one click. I would love to
> > add it to OB, but since this requires Pharo 1.1 I cannot.
> >
> >> I don't think it makes sense to adapt and fix the external packages
> >> that are in Pharo (of which you maintain a few) as long as PharoCore
> >> is in alpha state.
> >
> > I do not complain, I completely agree with the Pharo development
> > process. It is great what you are doing.
> >
> > I was telling Stef that I cannot take advantage of the cool new
> > dialogs right now, but only when there is a release candidate for
> > Pharo 1.1. Also I was hoping that I could use Helvetia directly in
> > Pharo 1.1, maybe together with a proposal for making the compiler
> > tool-chain easier to plug-in. However since Helvetia depends on RB and
> > OB that would mean that I had to fork these two projects. Something I
> > cannot do right now.
> >
> > Lukas
> >
> > --
> > Lukas Renggli
> > http://www.lukas-renggli.ch
> >
> > _______________________________________________
> > Pharo-project mailing list
> > [email protected]
> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> [email protected]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Reply via email to