[Pharo-project] Releasing 1.3: TODOs
TODOs to get 1.3 released: 1) store a 1.3Core on gforge build with an old vm. Double check it works with old VM. It is likely that, again, I did not think about this for some of the images on gforge... it might mean that we need to re-generate images and re-build the Full image based on that. I should again stress that this situation is sucking the live out of people (at least me) and we need to *simplify* our story *considerably*. This is *not* sustainable like this. 2) store a 1.3 on gforge (take form Hudson). double check with old vm 3) update the one-click with reasonable Vms. Which ones? I am confused wrt to VMs, so I need help here. 4) update the website. - especially regarding VMs For 1.4, we should *really* *really* make sure that we auto-generate the *final* *unchanged* release artefact... and *one* *defined* family of VMs, with the one-click (and just one one-click, not two) build from the latest VM. Marcus -- Marcus Denker -- http://marcusdenker.de
On Aug 8, 2011, at 8:51 AM, Marcus Denker wrote:
TODOs to get 1.3 released:
1) store a 1.3Core on gforge build with an old vm. Double check it works with old VM.
So the first question is: to which VMs exacly do we need to be compatibe? I just use the ones build by the build server... works fine for me, but I think we decided that these will be the official vms from 1.4 onwards. So what are the VMs for 1.3? Marcus -- Marcus Denker -- http://marcusdenker.de
Great! As soon as you release 1.3, we will release Moose 4.6 based on it, so I hope it will be soon :) Cheers, Doru On 8 Aug 2011, at 08:51, Marcus Denker wrote:
TODOs to get 1.3 released:
1) store a 1.3Core on gforge build with an old vm. Double check it works with old VM.
It is likely that, again, I did not think about this for some of the images on gforge... it might mean that we need to re-generate images and re-build the Full image based on that. I should again stress that this situation is sucking the live out of people (at least me) and we need to *simplify* our story *considerably*. This is *not* sustainable like this.
2) store a 1.3 on gforge (take form Hudson). double check with old vm
3) update the one-click with reasonable Vms. Which ones? I am confused wrt to VMs, so I need help here.
4) update the website. - especially regarding VMs
For 1.4, we should *really* *really* make sure that we auto-generate the *final* *unchanged* release artefact... and *one* *defined* family of VMs, with the one-click (and just one one-click, not two) build from the latest VM.
Marcus
-- Marcus Denker -- http://marcusdenker.de
-- www.tudorgirba.com "No matter how many recipes we know, we still value a chef."
participants (2)
-
Marcus Denker -
Tudor Girba