Hi Sven,
On Fri., 11 Oct. 2019, 15:05 Sven Van Caekenberghe, <[email protected]> wrote: > > > > On 11 Oct 2019, at 14:49, Cyril Ferlicot <[email protected]> > wrote: > > > > On Fri, Oct 11, 2019 at 2:32 PM Sven Van Caekenberghe <[email protected]> > wrote: > >> > >> I also do not understand how this was done in Pharo 7 *before* it was > finalised/fully debugged in Pharo 8. > >> > >> Back-porting must be done very carefully. > >> > > > > Hi Sven, > > > > One thing that must be know is that everything going in the Pharo 7 > > branch is not released directly. > > The changes you talk about are in no release currently. A release is > > launched manually currently when important changes are backported and > > stabilized. > > Hmm, OK, the /64/70+vm zeroconf version is indeed Pharo 7.0.4 build: 168, > commit: ccd1f64 which does still load Zn correctly, I just tested that > again. > > But how come some users are reporting problems then ? Is there a way they > can access that unreleased version, maybe via the launcher ? > Exactly... The launcher appears to download the latest snapshot. Cheers, Alistair (on phone) > > >
