[Pharo-project] [ANN] hard freeze 1.3 and (slow) start of 1.4
So 1.3 seems to get stable... we added some fixes over the week, but most of them are related to Pavel's kernel, so they are just refactorings and cleanups, no real fixes. I think we should continue to test 1.3 and end of the month announce it. TODO is quite short: -> harvest the two last Full related issues -> two more Pavel Kernel fixes for core -> check one-click on hudson for release. We configured the infrastructure last week for 1.4... to get it -> update an image before 13267 and say "yes" when asked if you want to progress to 1.4 -> or download the image https://gforge.inria.fr/frs/download.php/28660/PharoCore-1.4-14000.zip -> The 1.4 stream uses a new squeaksource project (pharo14) as the other one was too large (>4000 mcz files). -> the updates are just the same as in 1.3 for now, the only difference is that ToolBuilder was unloaded. For continuous integration, 1.4 is using the new Jenkins setup: https://ci.lille.inria.fr/pharo/ No one-click yet, that will follow... the idea is to move now slowly to the new jenkins, while letting 1.2 and 1.3 on the old server (and turn it off at some point in the future). Jenkins sends out tweets for every build: http://twitter.com/#!/pharoci Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
excellent On Jun 24, 2011, at 12:16 PM, Marcus Denker wrote:
So 1.3 seems to get stable... we added some fixes over the week, but most of them are related to Pavel's kernel, so they are just refactorings and cleanups, no real fixes.
I think we should continue to test 1.3 and end of the month announce it.
TODO is quite short: -> harvest the two last Full related issues -> two more Pavel Kernel fixes for core -> check one-click on hudson for release.
We configured the infrastructure last week for 1.4... to get it
-> update an image before 13267 and say "yes" when asked if you want to progress to 1.4 -> or download the image https://gforge.inria.fr/frs/download.php/28660/PharoCore-1.4-14000.zip
-> The 1.4 stream uses a new squeaksource project (pharo14) as the other one was too large (>4000 mcz files). -> the updates are just the same as in 1.3 for now, the only difference is that ToolBuilder was unloaded.
For continuous integration, 1.4 is using the new Jenkins setup:
https://ci.lille.inria.fr/pharo/
No one-click yet, that will follow... the idea is to move now slowly to the new jenkins, while letting 1.2 and 1.3 on the old server (and turn it off at some point in the future).
Jenkins sends out tweets for every build: http://twitter.com/#!/pharoci
Marcus
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
Very nice work, thank you very much Marcus. On Fri, Jun 24, 2011 at 12:16 PM, Marcus Denker <marcus.denker@inria.fr> wrote:
So 1.3 seems to get stable... we added some fixes over the week, but most of them are related to Pavel's kernel, so they are just refactorings and cleanups, no real fixes.
I think we should continue to test 1.3 and end of the month announce it.
TODO is quite short:     -> harvest the two last Full related issues     -> two more Pavel Kernel fixes for core     -> check one-click on hudson for release.
We configured the infrastructure last week for 1.4... to get it
    -> update an image before 13267 and say "yes" when asked if you want to progress to 1.4     -> or download the image                 https://gforge.inria.fr/frs/download.php/28660/PharoCore-1.4-14000.zip
-> The 1.4 stream uses a new squeaksource project (pharo14) as the other one was too large (>4000 mcz files). -> the updates are just the same as in 1.3 for now, the only difference is that ToolBuilder was unloaded.
For continuous integration, 1.4 is using the new Jenkins setup:
    https://ci.lille.inria.fr/pharo/
No one-click yet, that will follow... the idea is to move now slowly to the new jenkins, while letting 1.2 and 1.3 on the old server (and turn it off at some point in the future).
Jenkins sends out tweets for every build: http://twitter.com/#!/pharoci
    Marcus
-- Marcus Denker  -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
-- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry
Thanks a lot Marcus. Laurent. On Fri, Jun 24, 2011 at 12:16 PM, Marcus Denker <marcus.denker@inria.fr>wrote:
So 1.3 seems to get stable... we added some fixes over the week, but most of them are related to Pavel's kernel, so they are just refactorings and cleanups, no real fixes.
I think we should continue to test 1.3 and end of the month announce it.
TODO is quite short: -> harvest the two last Full related issues -> two more Pavel Kernel fixes for core -> check one-click on hudson for release.
We configured the infrastructure last week for 1.4... to get it
-> update an image before 13267 and say "yes" when asked if you want to progress to 1.4 -> or download the image
https://gforge.inria.fr/frs/download.php/28660/PharoCore-1.4-14000.zip
-> The 1.4 stream uses a new squeaksource project (pharo14) as the other one was too large (>4000 mcz files). -> the updates are just the same as in 1.3 for now, the only difference is that ToolBuilder was unloaded.
For continuous integration, 1.4 is using the new Jenkins setup:
https://ci.lille.inria.fr/pharo/
No one-click yet, that will follow... the idea is to move now slowly to the new jenkins, while letting 1.2 and 1.3 on the old server (and turn it off at some point in the future).
Jenkins sends out tweets for every build: http://twitter.com/#!/pharoci
Marcus
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
participants (4)
-
Damien Cassou -
laurent laffont -
Marcus Denker -
Stéphane Ducasse