[Pharo-project] [ANN 1.2.1a] towards 1.2.1
Hi, With people now finally actually looking at 1.2Core, we need to start to collect bugfixes and do a 1.2.1... So if you want to update 1.2Core, you need to SystemVersion newVersion: 'Pharo1.2.1a'. or download it from https://gforge.inria.fr/frs/download.php/28391/PharoCore-1.2.1a-12342.zip This is *not* linked as stable core... as it can break anytime. And 1.2Core does not update withour changing the version number (We might want to rethink that... but that can only be done in 1.3) Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
On Mar 18, 2011, at 9:13 PM, Marcus Denker wrote:
Hi,
With people now finally actually looking at 1.2Core, we need to start to collect bugfixes and do a 1.2.1...
So if you want to update 1.2Core, you need to
SystemVersion newVersion: 'Pharo1.2.1a'.
or download it from
https://gforge.inria.fr/frs/download.php/28391/PharoCore-1.2.1a-12342.zip
The integration server now builds 1.2.1a instead of 1.2 final: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/ Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
Am 20.03.2011 um 10:51 schrieb Marcus Denker:
On Mar 18, 2011, at 9:13 PM, Marcus Denker wrote:
Hi,
With people now finally actually looking at 1.2Core, we need to start to collect bugfixes and do a 1.2.1...
So if you want to update 1.2Core, you need to
SystemVersion newVersion: 'Pharo1.2.1a'.
or download it from
https://gforge.inria.fr/frs/download.php/28391/PharoCore-1.2.1a-12342.zip
The integration server now builds 1.2.1a instead of 1.2 final:
https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/
Probably you should rename the job to 1.2.1a. I tested it on my hudson server you can rename a job without breaking any dependencies to other jobs. I tested upstream trigger, copy artifacts. I don't know other dependencies. Norbert
Hi, a meta question... when i made changes to SystemVersion I put a comment in that method thinking it would not make sense to use it. You have published a use for it ;-) is there a reason you did not want to do SystemVersion current suffix: '1a' that was the main reason i made the changes so it was easy to adjust image versions without having to parse the string all the time. Did you want to remove the accumulated update set for some reason? I can perhaps re-comment the method if i understood the use case better. thanks, Mike On Fri, Mar 18, 2011 at 8:13 PM, Marcus Denker <marcus.denker@inria.fr> wrote:
Hi,
With people now finally actually looking at 1.2Core, we need to start to collect bugfixes and do a 1.2.1...
So if you want to update 1.2Core, you need to
    SystemVersion newVersion: 'Pharo1.2.1a'.
or download it from
    https://gforge.inria.fr/frs/download.php/28391/PharoCore-1.2.1a-12342.zip
This is *not* linked as stable core... as it can break anytime. And 1.2Core does not update withour changing the version number (We might want to rethink that... but that can only be done in 1.3)
    Marcus
-- Marcus Denker  -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
participants (3)
-
Marcus Denker -
Michael Roberts -
Norbert Hartl