On Wed, Jun 13, 2018 at 1:40 PM Tim Mackinnon <[email protected]> wrote:

> I have installed it fine now - I think the message is less ambiguous if
> the latest Pharo, is called the “latest Pharo 7” - thats where my confusion
> was.
>
> Is it worth reporting any bugs with this version in 6.1? I got an error
> dialog that was telling me about the project I was trying to load already
> existing on my disk - however the window is too small and so you don’t see
> that there is a Debug/Ignore button way off to the right (you have to
> stretch the dialog to see them).
>

Nope, that version is not maintained anymore...


>
> I also wonder if we are trying to be too clever with how you specify a
> Gitlab/Github project - both those sites have a little button you click to
> copy the full url of the project you want to clone - we are now asking
> people to not use that, but instead to copy the name of the project (which
> is typically the title Text above that url and copy button). This is very
> different from how every tool I use works and is a bit confusing.
>

Maybe... but for that you have the last option "Clone remote repository"
that allows you to just paste a url.


> Tim
>
> > On 13 Jun 2018, at 12:13, Cyril Ferlicot D. <[email protected]>
> wrote:
> >
> > On 13/06/2018 12:57, Tim Mackinnon wrote:
> >> Hi I’m a bit confused by what is described below - when it says "This is
> >> already in latest Pharo build. If you want to try it in a Pharo 6.1 ….”
> >> - does that mean its already in the latest Pharo 7 (emphasis on 7?)
> >> build (and I can see it in Pharo 7) - but the latest 6.1 build doesn’t
> >> have it and you must follow the steps you described?
> >>
> >
> > Hi!
> >
> > Each time an Iceberg stable version is released, it is integrated to
> > Pharo 7. (Usually, it's available the next day the time to do the PR,
> > test it, integrate it and build the new version)
> >
> > Pharo 6.1 is still at the v0.6 of Iceberg. IIUC, thi is mostly because
> > the new UI depends on a lot of changes from Pharo 7 and backporting it
> > would mean backport too many changes. The goal is to keep Pharo 6.1 as
> > stable as possible.
> >
> > So the steps to update yourself Iceberg to v1.? is for Pharo 6 only.
> >
> >> I initially read it to mean that new Pharo 6.1 builds would
> >> automatically get it - but that doesn’t seem to be the case?
> >>
> >> Tim
> >>
> >
> >
> > --
> > Cyril Ferlicot
> > https://ferlicot.fr
> >
>
>
>

-- 



Guille Polito

Research Engineer

Centre de Recherche en Informatique, Signal et Automatique de Lille

CRIStAL - UMR 9189

French National Center for Scientific Research - *http://www.cnrs.fr
<http://www.cnrs.fr>*


*Web:* *http://guillep.github.io* <http://guillep.github.io>

*Phone: *+33 06 52 70 66 13

Reply via email to