Re: [Pharo-project] Integrating Changes in 1.4 that require a new VM
On Sep 22, 2011, at 12:07 PM, Luc Fabresse wrote:
2011/9/22 Marcus Denker <marcus.denker@inria.fr> Hi,
There are two changesets waiting for integrating in 1.4 that have serious consequences:
- Ephemerons. The VM level changes are in the Cog VMs build on Jenkins, but have not been integrated in the VMMaker codebase.
http://code.google.com/p/pharo/issues/detail?id=4265
- Finalization code checks for #hasNewFinalization This is true in the current VMs build in Jenkins, but in older VMs this is not in.
http://code.google.com/p/pharo/issues/detail?id=4483
There are two options:
a) integrate in b) not integrate it
a) means that the image runs on older VMs, too.
"runs" or "will not run"?
Not run.
In any case, I am in favor to go ahead and change. Moreover, I am not sure it is a big deal here, since it will not impact application code.
The problems are: - people have to use the VM from https://ci.lille.inria.fr/pharo/view/Cog/ So older Vms (with more or different plugins, for example) are not possible. - there is no way to double check if a bug is specific to the Jenkins build Marcus -- Marcus Denker -- http://marcusdenker.de
In any case, I am in favor to go ahead and change. Moreover, I am not sure it is a big deal here, since it will not impact application code.
The problems are:
- people have to use the VM from https://ci.lille.inria.fr/pharo/view/Cog/ So older Vms (with more or different plugins, for example) are not possible.
- there is no way to double check if a bug is specific to the Jenkins build
indeed this is the key question. Now it would be good to brand the vm first.
participants (2)
-
Marcus Denker -
Stéphane Ducasse