Looks to me like 50000 branched from 40609... 40610 2015-04-23 50000 2015-04-16 40609 2015-04-15 40608 2015-04-14 40609 Log Message: * 15341 remove download sources setting https://pharo.fogbugz.com/f/cases/15341 * Deleted SmalltalkImage >> shouldDownloadSourcesFile 40608 shouldDownloadSourcesFile exists 40609 shouldDownloadSourcesFile does not exist 50000 shouldDownloadSourcesFile does not exist 40610 Log Message: * 15349 The menu in the PharoTutorial has an erroneous label https://pharo.fogbugz.com/f/cases/15349 * HelpBrowser>>menu "inspect it (p)" --> "inspect it (i)" 40609 has "(p)" 40610 has "(i)" 50000 has "(p)" cheers -ben On Tue, Sep 1, 2015 at 1:33 AM, Torsten Bergmann <astares@gmx.de> wrote:
Hi Stef, hi Mariano,
Yes, maybe it is a cleanup issue. But before we should deeper invest into this we must be sure if #40608 was the base for building #50000. Anyone able to confirm? Currently it is hard to reproduce from what 40xxx number the initial 5.0 image was built.
Also I thought #cleanupForRelease and #cleanupForProduction is always done on the CI images after applying each update. So any image is a production candidate/production release? Or is this only done for the backports? Havent checked yet - but maybe someone can answer this as well.
Thanks T.
Gesendet: Montag, 31. August 2015 um 14:08 Uhr Von: "Mariano Martinez Peck" <marianopeck@gmail.com> An: "Pharo Development List" <pharo-dev@lists.pharo.org> Betreff: Re: [Pharo-dev] Image used for 4.0 -> 5.0 (Build 50000) transition
Torsten, maybe it's related to ImageCleaner #cleanupForRelease and cleanupForProduction ?
On Mon, Aug 31, 2015 at 3:42 AM, stepharo <stepharo@free.fr> wrote: yes may be a cleanup.
Le 31/8/15 01:00, Nicolai Hess a écrit :
Oh, thats funny.Maybe this comes from the release buidling process, (condense changes / sources) anything thatresets some world state?
2015-08-30 22:29 GMT+02:00 Torsten Bergmann <astares@gmx.de[astares@gmx.de]>:Nicolai Hess wrote:
What does not work in 40608?
What Julien describes in [1] when he uses Pharo 4 with DesktopManager. I use Pharo 5 and did not have this effect.
To reproduce I used latest.zip from http://files.pharo.org/vm/pharo/win/[http://files.pharo.org/vm/pharo/win/] one time with #40608 and one time with #50000
Gofer new smalltalkhubUser: 'TorstenBergmann' project: 'DesktopManager'; configuration; loadDevelopment.
1. Hit CTRL + D and then CTRL + A (which is "D"esktop "A"dd) 2. Hit CTRL + D and then CTRL + P (which is "D"esktop "P"revious).
Now the windows on the first desktop are not usable anymore in 40608. They do not repaint.
In Pharo #50000 or any newer Pharo 5 image this works without a problem.
Bye T.
-- Mariano http://marianopeck.wordpress.com[http://marianopeck.wordpress.com]