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." |
In reply to this post by Marcus Denker-4
CONTENTS DELETED
The author has deleted this message.
|
In reply to this post by Marcus Denker-4
On Apr 3, 2011, at 9:41 AM, Tudor Girba wrote: > 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? > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. |
A pity that broken OB code is used, nevertheless it is quite usable.
Lukas On 3 April 2011 09:58, Marcus Denker <[hidden email]> wrote: > > On Apr 3, 2011, at 9:41 AM, Tudor Girba wrote: > >> 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? >> > Yes, you are right... > > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > -- Lukas Renggli www.lukas-renggli.ch |
In reply to this post by Marcus Denker-4
On Apr 3, 2011, at 10:22 AM, Lukas Renggli wrote: > A pity that broken OB code is used, nevertheless it is quite usable. > Yes, and I added a bug report on March 22: http://code.google.com/p/pharo/issues/detail?id=3842 But nobody cared to react. So how important can it be? There are two possibilities: -> Postponing the release because it's not perfect. (We are doing this for *3 Months* already) -> Not release and wait another 3 Months. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. |
In reply to this post by Marcus Denker-4
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." |
In reply to this post by Marcus Denker-4
On 3 April 2011 10:28, Marcus Denker <[hidden email]> wrote:
> > On Apr 3, 2011, at 10:22 AM, Lukas Renggli wrote: > >> A pity that broken OB code is used, nevertheless it is quite usable. >> > > Yes, and I added a bug report on March 22: > > http://code.google.com/p/pharo/issues/detail?id=3842 > > But nobody cared to react. So how important can it be? > One good feature i found on drupal site, that its automatically closing the issues if there is no activity after two weeks. Closed with label "unresolved" or "unattended" .. but the idea is that if nobody cared to fix it, then its not so important.. and there's always a way to reopen an issue later. > There are two possibilities: > > -> Postponing the release because it's not perfect. > (We are doing this for *3 Months* already) > > -> Not release and wait another 3 Months. > > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > -- Best regards, Igor Stasenko AKA sig. |
In reply to this post by Marcus Denker-4
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 <[hidden email]> 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/ |
In reply to this post by Sven Van Caekenberghe
On 4/4/11, Sven Van Caekenberghe <[hidden email]> 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 |
In reply to this post by Marcus Denker-4
On 4/3/11, Marcus Denker <[hidden email]> wrote:
> > On Apr 3, 2011, at 10:22 AM, Lukas Renggli wrote: > >> A pity that broken OB code is used, nevertheless it is quite usable. >> > > Yes, and I added a bug report on March 22: > > http://code.google.com/p/pharo/issues/detail?id=3842 > > But nobody cared to react. So how important can it be? > > There are two possibilities: > > -> Postponing the release because it's not perfect. > (We are doing this for *3 Months* already) > > -> Not release and wait another 3 Months. > > > Marcus There are _three_ possibilities: -> Postponing the release because it's not perfect. (We are doing this for *3 Months* already) -> Not release and wait another 3 Months. -> Mark the issues which are not resolved as 'Known bug', post this list some time before the release and ask people if they do not have objections. Take silence for agreement and then include the 'Known bug list' in the release announcement. --Hannes |
In reply to this post by Sven Van Caekenberghe
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 |
In reply to this post by Stéphane Ducasse
On Apr 4, 2011, at 4:09 PM, Sven Van Caekenberghe wrote: > > 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. > Mariano started a list: http://code.google.com/p/pharo/wiki/ActionsInPharoOneDotTwo All things done should have a tracker entry: http://code.google.com/p/pharo/issues/list?can=1&q=milestone=1.2 http://code.google.com/p/pharo/issues/list?can=1&q=Milestone%3D1.2-DevImage -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. |
On 04 Apr 2011, at 16:19, Marcus Denker wrote: > On Apr 4, 2011, at 4:09 PM, Sven Van Caekenberghe wrote: > >> >> 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. >> > > Mariano started a list: > > http://code.google.com/p/pharo/wiki/ActionsInPharoOneDotTwo > > All things done should have a tracker entry: > > http://code.google.com/p/pharo/issues/list?can=1&q=milestone=1.2 > http://code.google.com/p/pharo/issues/list?can=1&q=Milestone%3D1.2-DevImage OK, I will start reading through these lists and compare with what was written about the previous releases and see if I can come up with something by tomorrow. Sven |
On Mon, Apr 4, 2011 at 4:31 PM, Sven Van Caekenberghe <[hidden email]> wrote:
I will translate for the French announcement.
Laurent.
|
I started to try to release 1.2. Not only I did the list of changes but also:
1) I asked if people still wanted the background: http://forum.world.st/Do-you-want-to-add-the-background-picture-to-the-image-like-we-did-with-Pharo-1-1-td3350726.html#a3355332 results: negative. So, no backgrund. White as it is now. 2) I asked what people wanted that used to be in 1.1: http://forum.world.st/Do-we-want-this-for-Pharo-1-2-and-futures-td3350721.html guess how many replies? TWO. results: I would only nclude the installScript. I guess that Hudson could do that very easy, doesn't it ? marcus ? 3) I wrote down the pending lists: http://forum.world.st/Last-pending-things-for-Pharo-1-2-tp3350731p3350731.html Sorry, I cannot do more. Cheers Mariano On Mon, Apr 4, 2011 at 4:33 PM, laurent laffont <[hidden email]> wrote:
-- Mariano http://marianopeck.wordpress.com |
Free forum by Nabble | Edit this page |