[Pharo-project] [ANN 1.2] 1.2.1 Full Release Image
https://gforge.inria.fr/frs/download.php/28435/Pharo-1.2.1-11.04.03.zip Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
On Apr 3, 2011, at 9:35 AM, Marcus Denker wrote:
https://gforge.inria.fr/frs/download.php/28435/Pharo-1.2.1-11.04.03.zip
.. the all green image of today from Hudson. Yes, this is not repeatable and tomorrow the hudson one might be different. But we need to move on. 1.1 was build just once, too. So we can continue to build the perfect fully automatic process for 1.3... Next: -> Make a one-click. -> Make a cog one-click. -> push all open reports in the tracker to 1.2.2 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
Excellent!
https://gforge.inria.fr/frs/download.php/28435/Pharo-1.2.1-11.04.03.zip
.. the all green image of today from Hudson. Yes, this is not repeatable and tomorrow the hudson one might be different. But we need to move on. 1.1 was build just once, too.
Exactly.
So we can continue to build the perfect fully automatic process for 1.3...
Next: -> Make a one-click. -> Make a cog one-click. -> push all open reports in the tracker to 1.2.2
Why still work on 1.2.2. Why not moving them to 1.3? Cheers, Doru -- www.tudorgirba.com "No matter how many recipes we know, we still value a chef."
tx! and yes we should continue On Apr 3, 2011, at 9:36 AM, Marcus Denker wrote:
On Apr 3, 2011, at 9:35 AM, Marcus Denker wrote:
https://gforge.inria.fr/frs/download.php/28435/Pharo-1.2.1-11.04.03.zip
.. the all green image of today from Hudson. Yes, this is not repeatable and tomorrow the hudson one might be different. But we need to move on. 1.1 was build just once, too. So we can continue to build the perfect fully automatic process for 1.3...
Next: -> Make a one-click. -> Make a cog one-click. -> push all open reports in the tracker to 1.2.2
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
Hi, The Moose build uses 1.2.1 now: http://hudson.moosetechnology.org/job/moose-latest-dev/ Cheers, Doru On 3 Apr 2011, at 10:45, Stéphane Ducasse wrote:
tx! and yes we should continue
On Apr 3, 2011, at 9:36 AM, Marcus Denker wrote:
On Apr 3, 2011, at 9:35 AM, Marcus Denker wrote:
https://gforge.inria.fr/frs/download.php/28435/Pharo-1.2.1-11.04.03.zip
.. the all green image of today from Hudson. Yes, this is not repeatable and tomorrow the hudson one might be different. But we need to move on. 1.1 was build just once, too. So we can continue to build the perfect fully automatic process for 1.3...
Next: -> Make a one-click. -> Make a cog one-click. -> push all open reports in the tracker to 1.2.2
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
-- www.tudorgirba.com "Problem solving should be focused on describing the problem in a way that makes the solution obvious."
Thanks Markus Hil Le 03/04/2011 09:35, Marcus Denker a écrit :
https://gforge.inria.fr/frs/download.php/28435/Pharo-1.2.1-11.04.03.zip
Marcus
-- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
-- Education 0.2 -- http://blog.ofset.org/hilaire
On 03 Apr 2011, at 09:35, Marcus Denker wrote:
https://gforge.inria.fr/frs/download.php/28435/Pharo-1.2.1-11.04.03.zip
Marcus
Marcus et al, I have to agree with Laurent: you and the rest of Pharo are being way too modest here. Like most users I have been waiting for 1.2.x to be announced with a big splash. I know and understand how it has been a long and boring process at the end. Like you said, a release is just a release: a group of developers deciding that the current state of the system is 'good enough'. I have been using a #12333 hudson/jenkins built Seaside 3.0.3 image for more than a month for development and server deployment and it has been a very nice experience (in other words, it worked perfectly). So, from my part: thank you for all the efforts, the results are fantastic! So please, organize some kind of splash! Regards, Sven
On Mon, Apr 4, 2011 at 4:16 PM, Sven Van Caekenberghe <sven@beta9.be> wrote:
On 03 Apr 2011, at 09:35, Marcus Denker wrote:
   https://gforge.inria.fr/frs/download.php/28435/Pharo-1.2.1-11.04.03.zip
   Marcus
Marcus et al,
I have to agree with Laurent: you and the rest of Pharo are being way too modest here. Like most users I have been waiting for 1.2.x to be announced with a big splash. I know and understand how it has been a long and boring process at the end.
Like you said, a release is just a release: a group of developers deciding that the current state of the system is 'good enough'. I have been using a #12333 hudson/jenkins built Seaside 3.0.3 image for more than a month for development and server deployment and it has been a very nice experience (in other words, it worked perfectly).
So, from my part: thank you for all the efforts, the results are fantastic!
So please, organize some kind of splash!
+1 Yes i agree, we need to release Pharo 1.2. This is not perfect but this is usuable without too much problems. The next release will be better ;-) A big applause for the Pharo core team !!! -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/
On 4/4/11, Sven Van Caekenberghe <sven@beta9.be> wrote:
On 03 Apr 2011, at 09:35, Marcus Denker wrote:
https://gforge.inria.fr/frs/download.php/28435/Pharo-1.2.1-11.04.03.zip
Marcus
Marcus et al,
I have to agree with Laurent: you and the rest of Pharo are being way too modest here. Like most users I have been waiting for 1.2.x to be announced with a big splash.
+1. It was just the download link. I would have expected some 'release notes'. I'm glad to download it and the moose-dev image which builds on it. --Hannes
Please help because we have not the steam for the splash organization.
Marcus et al,
I have to agree with Laurent: you and the rest of Pharo are being way too modest here. Like most users I have been waiting for 1.2.x to be announced with a big splash. I know and understand how it has been a long and boring process at the end.
Like you said, a release is just a release: a group of developers deciding that the current state of the system is 'good enough'. I have been using a #12333 hudson/jenkins built Seaside 3.0.3 image for more than a month for development and server deployment and it has been a very nice experience (in other words, it worked perfectly).
So, from my part: thank you for all the efforts, the results are fantastic!
So please, organize some kind of splash!
Regards,
Sven
On 04 Apr 2011, at 15:40, Stéphane Ducasse wrote:
Please help because we have not the steam for the splash organization.
So we poor users have to do all the work ?? Seriously, what is the easiest/fastest way to get to a rough list of the changes between 1.1.1 and 1.2.1 ?
From that list we could try to make a readable list for release notes and then we could try to make a list of bullet points / highlights.
Maybe we could also run metrics on both if that would yield something useful ? Sven
participants (7)
-
Hannes Hirzel -
Hilaire Fernandes -
Marcus Denker -
Serge Stinckwich -
Stéphane Ducasse -
Sven Van Caekenberghe -
Tudor Girba