Other than the fact that the last two builds for SqueakTrunk have hung - an issue I'm looking into, but wouldn't mind others trying their luck - are we happy enough with 4.4 that we'd want to ship it?
My gut feel is (and with my Release Manager hat on), judging by the low severity of the few reports we're seeing, that we're there. What do others think?
One thing we _don't_ have is an "All-in-one" one-click type installer for the various OSes. If someone can show me what to do, I can add a job to spit out such a thing.
frank
On Sat, Dec 29, 2012 at 11:06 AM, Frank Shearar frank.shearar@gmail.comwrote:
Other than the fact that the last two builds for SqueakTrunk have hung
- an issue I'm looking into, but wouldn't mind others trying their
luck - are we happy enough with 4.4 that we'd want to ship it?
My gut feel is (and with my Release Manager hat on), judging by the low severity of the few reports we're seeing, that we're there. What do others think
+1
+1
On 12/29/12, Colin Putney colin@wiresong.com wrote:
On Sat, Dec 29, 2012 at 11:06 AM, Frank Shearar frank.shearar@gmail.comwrote:
Other than the fact that the last two builds for SqueakTrunk have hung
- an issue I'm looking into, but wouldn't mind others trying their
luck - are we happy enough with 4.4 that we'd want to ship it?
My gut feel is (and with my Release Manager hat on), judging by the low severity of the few reports we're seeing, that we're there. What do others think
+1
+1
H. Hirzel wrote
+1
On 12/29/12, Colin Putney <
colin@
> wrote:
On Sat, Dec 29, 2012 at 11:06 AM, Frank Shearar <
frank.shearar@
>wrote:
Other than the fact that the last two builds for SqueakTrunk have hung
- an issue I'm looking into, but wouldn't mind others trying their
luck - are we happy enough with 4.4 that we'd want to ship it?
My gut feel is (and with my Release Manager hat on), judging by the low severity of the few reports we're seeing, that we're there. What do others think
+1
-- View this message in context: http://forum.world.st/4-4-ready-tp4661267p4661279.html Sent from the Squeak - Dev mailing list archive at Nabble.com.
On Sat, 29 Dec 2012, Frank Shearar wrote:
Other than the fact that the last two builds for SqueakTrunk have hung
- an issue I'm looking into, but wouldn't mind others trying their
luck - are we happy enough with 4.4 that we'd want to ship it?
My gut feel is (and with my Release Manager hat on), judging by the low severity of the few reports we're seeing, that we're there. What do others think?
I think it's time to release it, even though SqueakSSL doesn't like the network changes.
Levente
One thing we _don't_ have is an "All-in-one" one-click type installer for the various OSes. If someone can show me what to do, I can add a job to spit out such a thing.
frank
On 29 December 2012 18:49, Levente Uzonyi leves@elte.hu wrote:
On Sat, 29 Dec 2012, Frank Shearar wrote:
Other than the fact that the last two builds for SqueakTrunk have hung
- an issue I'm looking into, but wouldn't mind others trying their
luck - are we happy enough with 4.4 that we'd want to ship it?
My gut feel is (and with my Release Manager hat on), judging by the low severity of the few reports we're seeing, that we're there. What do others think?
I think it's time to release it, even though SqueakSSL doesn't like the network changes.
OK. Once I uncover whatever's hanging the SqueakTrunk build I'll yell, and we can give the ReleaseSqueakTrunk artifact one more whirl and declare victory.
frank
Levente
One thing we _don't_ have is an "All-in-one" one-click type installer for the various OSes. If someone can show me what to do, I can add a job to spit out such a thing.
frank
On 29 December 2012 21:06, Frank Shearar frank.shearar@gmail.com wrote:
On 29 December 2012 18:49, Levente Uzonyi leves@elte.hu wrote:
On Sat, 29 Dec 2012, Frank Shearar wrote:
Other than the fact that the last two builds for SqueakTrunk have hung
- an issue I'm looking into, but wouldn't mind others trying their
luck - are we happy enough with 4.4 that we'd want to ship it?
My gut feel is (and with my Release Manager hat on), judging by the low severity of the few reports we're seeing, that we're there. What do others think?
I think it's time to release it, even though SqueakSSL doesn't like the network changes.
OK. Once I uncover whatever's hanging the SqueakTrunk build I'll yell, and we can give the ReleaseSqueakTrunk artifact one more whirl and declare victory.
It MAY be that there was an intermittent issue with source.squeak.org not accepting connections: I saw a ConnectionRefused while trying to reproduce the hung build locally. That could be because of my flakey home wifi, but then again (a) such an exception would raise a debugger and hang the build and (b) the builds have started not hanging [1]. At any rate, they do log a lot more: the update number, the tests they're running, and so on.
[1] http://squeakci.org/job/SqueakTrunk/83/console
frank
Levente
One thing we _don't_ have is an "All-in-one" one-click type installer for the various OSes. If someone can show me what to do, I can add a job to spit out such a thing.
frank
On 29 December 2012 22:15, Frank Shearar frank.shearar@gmail.com wrote:
On 29 December 2012 21:06, Frank Shearar frank.shearar@gmail.com wrote:
On 29 December 2012 18:49, Levente Uzonyi leves@elte.hu wrote:
On Sat, 29 Dec 2012, Frank Shearar wrote:
Other than the fact that the last two builds for SqueakTrunk have hung
- an issue I'm looking into, but wouldn't mind others trying their
luck - are we happy enough with 4.4 that we'd want to ship it?
My gut feel is (and with my Release Manager hat on), judging by the low severity of the few reports we're seeing, that we're there. What do others think?
I think it's time to release it, even though SqueakSSL doesn't like the network changes.
OK. Once I uncover whatever's hanging the SqueakTrunk build I'll yell, and we can give the ReleaseSqueakTrunk artifact one more whirl and declare victory.
It MAY be that there was an intermittent issue with source.squeak.org not accepting connections: I saw a ConnectionRefused while trying to reproduce the hung build locally. That could be because of my flakey home wifi, but then again (a) such an exception would raise a debugger and hang the build and (b) the builds have started not hanging [1]. At any rate, they do log a lot more: the update number, the tests they're running, and so on.
SqueakTrunk looks like it's back in business. ReleaseSqueakTrunk still has issues, because it looks like it's confused (or I've confused it) as to the artifacts it's supposed to use: it's consistently releasing 12324-based images instead of 12326-based ones. I shall hack on...
frank
[1] http://squeakci.org/job/SqueakTrunk/83/console
frank
Levente
One thing we _don't_ have is an "All-in-one" one-click type installer for the various OSes. If someone can show me what to do, I can add a job to spit out such a thing.
frank
I noticed the copyright stops at 2011, it should be at least 2012 (if you're fast enough...)
Nicolas
2012/12/31 Frank Shearar frank.shearar@gmail.com:
On 29 December 2012 22:15, Frank Shearar frank.shearar@gmail.com wrote:
On 29 December 2012 21:06, Frank Shearar frank.shearar@gmail.com wrote:
On 29 December 2012 18:49, Levente Uzonyi leves@elte.hu wrote:
On Sat, 29 Dec 2012, Frank Shearar wrote:
Other than the fact that the last two builds for SqueakTrunk have hung
- an issue I'm looking into, but wouldn't mind others trying their
luck - are we happy enough with 4.4 that we'd want to ship it?
My gut feel is (and with my Release Manager hat on), judging by the low severity of the few reports we're seeing, that we're there. What do others think?
I think it's time to release it, even though SqueakSSL doesn't like the network changes.
OK. Once I uncover whatever's hanging the SqueakTrunk build I'll yell, and we can give the ReleaseSqueakTrunk artifact one more whirl and declare victory.
It MAY be that there was an intermittent issue with source.squeak.org not accepting connections: I saw a ConnectionRefused while trying to reproduce the hung build locally. That could be because of my flakey home wifi, but then again (a) such an exception would raise a debugger and hang the build and (b) the builds have started not hanging [1]. At any rate, they do log a lot more: the update number, the tests they're running, and so on.
SqueakTrunk looks like it's back in business. ReleaseSqueakTrunk still has issues, because it looks like it's confused (or I've confused it) as to the artifacts it's supposed to use: it's consistently releasing 12324-based images instead of 12326-based ones. I shall hack on...
frank
[1] http://squeakci.org/job/SqueakTrunk/83/console
frank
Levente
One thing we _don't_ have is an "All-in-one" one-click type installer for the various OSes. If someone can show me what to do, I can add a job to spit out such a thing.
frank
On 31 December 2012 14:03, Nicolas Cellier nicolas.cellier.aka.nice@gmail.com wrote:
I noticed the copyright stops at 2011, it should be at least 2012 (if you're fast enough...)
Where does that appear?
frank
Nicolas
2012/12/31 Frank Shearar frank.shearar@gmail.com:
On 29 December 2012 22:15, Frank Shearar frank.shearar@gmail.com wrote:
On 29 December 2012 21:06, Frank Shearar frank.shearar@gmail.com wrote:
On 29 December 2012 18:49, Levente Uzonyi leves@elte.hu wrote:
On Sat, 29 Dec 2012, Frank Shearar wrote:
Other than the fact that the last two builds for SqueakTrunk have hung
- an issue I'm looking into, but wouldn't mind others trying their
luck - are we happy enough with 4.4 that we'd want to ship it?
My gut feel is (and with my Release Manager hat on), judging by the low severity of the few reports we're seeing, that we're there. What do others think?
I think it's time to release it, even though SqueakSSL doesn't like the network changes.
OK. Once I uncover whatever's hanging the SqueakTrunk build I'll yell, and we can give the ReleaseSqueakTrunk artifact one more whirl and declare victory.
It MAY be that there was an intermittent issue with source.squeak.org not accepting connections: I saw a ConnectionRefused while trying to reproduce the hung build locally. That could be because of my flakey home wifi, but then again (a) such an exception would raise a debugger and hang the build and (b) the builds have started not hanging [1]. At any rate, they do log a lot more: the update number, the tests they're running, and so on.
SqueakTrunk looks like it's back in business. ReleaseSqueakTrunk still has issues, because it looks like it's confused (or I've confused it) as to the artifacts it's supposed to use: it's consistently releasing 12324-based images instead of 12326-based ones. I shall hack on...
frank
[1] http://squeakci.org/job/SqueakTrunk/83/console
frank
Levente
One thing we _don't_ have is an "All-in-one" one-click type installer for the various OSes. If someone can show me what to do, I can add a job to spit out such a thing.
frank
2012/12/31 Frank Shearar frank.shearar@gmail.com:
On 31 December 2012 14:03, Nicolas Cellier nicolas.cellier.aka.nice@gmail.com wrote:
I noticed the copyright stops at 2011, it should be at least 2012 (if you're fast enough...)
Where does that appear?
frank
The "Licence" workspace
Nicolas
2012/12/31 Frank Shearar frank.shearar@gmail.com:
On 29 December 2012 22:15, Frank Shearar frank.shearar@gmail.com wrote:
On 29 December 2012 21:06, Frank Shearar frank.shearar@gmail.com wrote:
On 29 December 2012 18:49, Levente Uzonyi leves@elte.hu wrote:
On Sat, 29 Dec 2012, Frank Shearar wrote:
> Other than the fact that the last two builds for SqueakTrunk have hung > - an issue I'm looking into, but wouldn't mind others trying their > luck - are we happy enough with 4.4 that we'd want to ship it? > > My gut feel is (and with my Release Manager hat on), judging by the > low severity of the few reports we're seeing, that we're there. What > do others think? >
I think it's time to release it, even though SqueakSSL doesn't like the network changes.
OK. Once I uncover whatever's hanging the SqueakTrunk build I'll yell, and we can give the ReleaseSqueakTrunk artifact one more whirl and declare victory.
It MAY be that there was an intermittent issue with source.squeak.org not accepting connections: I saw a ConnectionRefused while trying to reproduce the hung build locally. That could be because of my flakey home wifi, but then again (a) such an exception would raise a debugger and hang the build and (b) the builds have started not hanging [1]. At any rate, they do log a lot more: the update number, the tests they're running, and so on.
SqueakTrunk looks like it's back in business. ReleaseSqueakTrunk still has issues, because it looks like it's confused (or I've confused it) as to the artifacts it's supposed to use: it's consistently releasing 12324-based images instead of 12326-based ones. I shall hack on...
frank
[1] http://squeakci.org/job/SqueakTrunk/83/console
frank
Levente
> One thing we _don't_ have is an "All-in-one" one-click type installer > for the various OSes. If someone can show me what to do, I can add a > job to spit out such a thing. > > frank > >
On 31 December 2012 14:12, Nicolas Cellier nicolas.cellier.aka.nice@gmail.com wrote:
2012/12/31 Frank Shearar frank.shearar@gmail.com:
On 31 December 2012 14:03, Nicolas Cellier nicolas.cellier.aka.nice@gmail.com wrote:
I noticed the copyright stops at 2011, it should be at least 2012 (if you're fast enough...)
Where does that appear?
frank
The "Licence" workspace
Thanks! System-fbs.506 contains the fix. And I beat the ReleaseSqueakTrunk job into submission: http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ...
I'd really like to release this guy today, so if anyone has anything _urgent_ to get in, now's the time.
I still have to do two more things for this release: populate the 44 update stream, and then declare 4.4 finished. I don't think we need to do anything further to make trunk ready for 4.5, do we? 4.5 alpha just becomes the update after 4.4 splits off.
Regarding the All-in-One, is it sufficient to take the 4.3 one and replace the Cog and image/changes file in it to produce a new one?
frank
Nicolas
2012/12/31 Frank Shearar frank.shearar@gmail.com:
On 29 December 2012 22:15, Frank Shearar frank.shearar@gmail.com wrote:
On 29 December 2012 21:06, Frank Shearar frank.shearar@gmail.com wrote:
On 29 December 2012 18:49, Levente Uzonyi leves@elte.hu wrote: > On Sat, 29 Dec 2012, Frank Shearar wrote: > >> Other than the fact that the last two builds for SqueakTrunk have hung >> - an issue I'm looking into, but wouldn't mind others trying their >> luck - are we happy enough with 4.4 that we'd want to ship it? >> >> My gut feel is (and with my Release Manager hat on), judging by the >> low severity of the few reports we're seeing, that we're there. What >> do others think? >> > > I think it's time to release it, even though SqueakSSL doesn't like the > network changes.
OK. Once I uncover whatever's hanging the SqueakTrunk build I'll yell, and we can give the ReleaseSqueakTrunk artifact one more whirl and declare victory.
It MAY be that there was an intermittent issue with source.squeak.org not accepting connections: I saw a ConnectionRefused while trying to reproduce the hung build locally. That could be because of my flakey home wifi, but then again (a) such an exception would raise a debugger and hang the build and (b) the builds have started not hanging [1]. At any rate, they do log a lot more: the update number, the tests they're running, and so on.
SqueakTrunk looks like it's back in business. ReleaseSqueakTrunk still has issues, because it looks like it's confused (or I've confused it) as to the artifacts it's supposed to use: it's consistently releasing 12324-based images instead of 12326-based ones. I shall hack on...
frank
[1] http://squeakci.org/job/SqueakTrunk/83/console
frank
> Levente > > >> One thing we _don't_ have is an "All-in-one" one-click type installer >> for the various OSes. If someone can show me what to do, I can add a >> job to spit out such a thing. >> >> frank >> >> >
Frank Shearar-3 wrote
Regarding the All-in-One, is it sufficient to take the 4.3 one and replace the Cog and image/changes file in it to produce a new one?
That's what I've been doing. Just change the image name in: squeak.sh, squeak.ini and info.plist for Unix, Windows and OSX respectively. Set the "WindowTitle" to something appropriate in squeak.ini too. Oh, and don't let your text editor muck up the line endings. ;)
-- View this message in context: http://forum.world.st/4-4-ready-tp4661267p4661535.html Sent from the Squeak - Dev mailing list archive at Nabble.com.
Am 31.12.2012 15:30, schrieb Frank Shearar:
Regarding the All-in-One, is it sufficient to take the 4.3 one and replace the Cog and image/changes file in it to produce a new one? frank
yes, at least that's what I always do. Replacing all Cog VM's needs some extra care in Linux as to remove all scripts which still point to the old VM. At least from a Windows point of view this is complicated.
Cheers,
Herbert
On 31 December 2012 15:22, Herbert König herbertkoenig@gmx.net wrote:
Am 31.12.2012 15:30, schrieb Frank Shearar:
Regarding the All-in-One, is it sufficient to take the 4.3 one and replace the Cog and image/changes file in it to produce a new one? frank
yes, at least that's what I always do. Replacing all Cog VM's needs some extra care in Linux as to remove all scripts which still point to the old VM. At least from a Windows point of view this is complicated.
Mm, it's not just that: there are bits of VM and plugins scattered all over the place.
frank
Cheers,
Herbert
On Mon, Dec 31, 2012 at 04:08:29PM +0000, Frank Shearar wrote:
On 31 December 2012 15:22, Herbert K?nig herbertkoenig@gmx.net wrote:
Am 31.12.2012 15:30, schrieb Frank Shearar:
Regarding the All-in-One, is it sufficient to take the 4.3 one and replace the Cog and image/changes file in it to produce a new one? frank
yes, at least that's what I always do. Replacing all Cog VM's needs some extra care in Linux as to remove all scripts which still point to the old VM. At least from a Windows point of view this is complicated.
Mm, it's not just that: there are bits of VM and plugins scattered all over the place.
The 4.3 All-in-One package is using a standard interpreter VM. I think we'll need some follow up discussion as to which VMs to include in the All-in-One package for 4.4.
My initial suggestion would be to do the package by replacing only the image and changes files, which should produce a known-working configuration for existing platforms.
There are newer intepreter VMs on squeakvm.org, but I am aware of one issue for the Linux build that might make it inappropriate for the All-in-One package. The VM is compiled on a relatively new Linux distribution, and will not run on some older distributions because of a Linux library compatibility issue.
We may also be able to use Cog VMs at this point, I'm not really sure which would be best.
Dave
On 12/31/12, David T. Lewis lewis@mail.msen.com wrote:
On Mon, Dec 31, 2012 at 04:08:29PM +0000, Frank Shearar wrote:
On 31 December 2012 15:22, Herbert K?nig herbertkoenig@gmx.net wrote:
Am 31.12.2012 15:30, schrieb Frank Shearar:
Regarding the All-in-One, is it sufficient to take the 4.3 one and replace the Cog and image/changes file in it to produce a new one? frank
yes, at least that's what I always do. Replacing all Cog VM's needs some extra care in Linux as to remove all scripts which still point to the old VM. At least from a Windows point of view this is complicated.
Mm, it's not just that: there are bits of VM and plugins scattered all over the place.
The 4.3 All-in-One package is using a standard interpreter VM. I think we'll need some follow up discussion as to which VMs to include in the All-in-One package for 4.4.
My initial suggestion would be to do the package by replacing only the image and changes files, which should produce a known-working configuration for existing platforms.
+1
There are newer intepreter VMs on squeakvm.org, but I am aware of one issue for the Linux build that might make it inappropriate for the All-in-One package. The VM is compiled on a relatively new Linux distribution, and will not run on some older distributions because of a Linux library compatibility issue.
We may also be able to use Cog VMs at this point, I'm not really sure which would be best.
Dave
Am 31.12.2012 17:28, schrieb David T. Lewis:
yes, at least that's what I always do. Replacing all Cog VM's needs some extra care in Linux as to remove all scripts which still point to the old VM. At least from a Windows point of view this is complicated.
Mm, it's not just that: there are bits of VM and plugins scattered all over the place.
I have an all in one derived image running on (not quite recent) Cog on Linux and Windows. I can replace the two VM's with current Cog but I usually neglect (delete) Mac as I don't have one. Not sure if I can do it before midnight though.
We may also be able to use Cog VMs at this point, I'm not really sure which would be best. Dave
Yes, I assumed that.
Herbert
On 31 December 2012 18:02, Herbert König herbertkoenig@gmx.net wrote:
Am 31.12.2012 17:28, schrieb David T. Lewis:
yes, at least that's what I always do. Replacing all Cog VM's needs some extra care in Linux as to remove all scripts which still point to the old VM. At least from a Windows point of view this is complicated.
Mm, it's not just that: there are bits of VM and plugins scattered all over the place.
I have an all in one derived image running on (not quite recent) Cog on Linux and Windows. I can replace the two VM's with current Cog but I usually neglect (delete) Mac as I don't have one. Not sure if I can do it before midnight though.
That's fine. I'm quite happy to declare victory with 12327 (now up on the ftp server) and wrap up 4.4 (populating its repository & such), leaving creating follow-on artifacts like the All-in-One for tomorrow.
frank
We may also be able to use Cog VMs at this point, I'm not really sure which would be best. Dave
Yes, I assumed that.
Herbert
Thanks for all you hard work Frank! Happy New Year.
Glen
-- View this message in context: http://forum.world.st/4-4-ready-tp4661267p4661552.html Sent from the Squeak - Dev mailing list archive at Nabble.com.
On 31 December 2012 20:36, David T. Lewis lewis@mail.msen.com wrote:
On Mon, Dec 31, 2012 at 12:13:46PM -0800, glenpaling wrote:
Thanks for all you hard work Frank! Happy New Year.
Glen
+1000
Well done Frank, and a happy new year to all!
Dave
Thank you very much. I'm rather happy with the automation work I've added. But mainly, it's thanks to the Squeak community for pitching in: loads of people have done loads of testing, both those advertising their contributions on list as well as folks approaching me off-list to help out.
Also, I should note I've just populated the squeak44 update stream so things SHOULD now be finished for 4.4 (except for the All-for-One).
frank
On 2012-12-31 3:42 PM, Frank Shearar wrote:
On 31 December 2012 20:36, David T. Lewis lewis@mail.msen.com wrote:
On Mon, Dec 31, 2012 at 12:13:46PM -0800, glenpaling wrote:
Thanks for all you hard work Frank! Happy New Year.
Glen
+1000
Well done Frank, and a happy new year to all!
+1
Dave
Thank you very much. I'm rather happy with the automation work I've added.
It's the automation work that really impresses me. I looked at the CI recently server and was happy to see a proliferation of scripts of depth. You've really set the template there for future Squeak releases. Great job. Have some scrumpy. :)
Chris
But mainly, it's thanks to the Squeak community for pitching in: loads of people have done loads of testing, both those advertising their contributions on list as well as folks approaching me off-list to help out.
Also, I should note I've just populated the squeak44 update stream so things SHOULD now be finished for 4.4 (except for the All-for-One).
frank
Happy New Year 2012 and thank you, in particular Frank Shearar for your immense work in 2012. The integration server is a big step forward and the automation of of producing releases. Maybe we can have two or three this year. (an 'unstable' 4.5 release with FileSystem, Minimal image and Environments and a 'stable' 4.6 release)
I now see the Squeak 4.4-12327 artifact in
http://ftp.squeak.org/4.4/Squeak4.4-12327.zip
This is the 4.4 release?
--Hannes
On 12/31/12, Chris Cunnington smalltalktelevision@gmail.com wrote:
On 2012-12-31 3:42 PM, Frank Shearar wrote:
On 31 December 2012 20:36, David T. Lewis lewis@mail.msen.com wrote:
On Mon, Dec 31, 2012 at 12:13:46PM -0800, glenpaling wrote:
Thanks for all you hard work Frank! Happy New Year.
Glen
+1000
Well done Frank, and a happy new year to all!
+1
Dave
Thank you very much. I'm rather happy with the automation work I've added.
It's the automation work that really impresses me. I looked at the CI recently server and was happy to see a proliferation of scripts of depth. You've really set the template there for future Squeak releases. Great job. Have some scrumpy. :)
Chris
But mainly, it's thanks to the Squeak community for pitching in: loads of people have done loads of testing, both those advertising their contributions on list as well as folks approaching me off-list to help out.
Also, I should note I've just populated the squeak44 update stream so things SHOULD now be finished for 4.4 (except for the All-for-One).
frank
Hi,
Thanks! System-fbs.506 contains the fix. And I beat the ReleaseSqueakTrunk job into submission: http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ...
wanted to start on an allInOne by replacing my images and changes and the above link doesn't work. All I can get from Jenkins is #12333.
OK I start with putting in the latest Cog VM's, 2640 0f 20-Dec-2012.
Cheers,
Herbert
On 1 January 2013 18:21, Herbert König herbertkoenig@gmx.net wrote:
Hi,
Thanks! System-fbs.506 contains the fix. And I beat the ReleaseSqueakTrunk job into submission:
http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ...
wanted to start on an allInOne by replacing my images and changes and the above link doesn't work. All I can get from Jenkins is #12333.
I see.... that's very weird, given that http://squeakci.org/job/ReleaseSqueakTrunk/30/ has in its artifact link a 12328.
Which reminds me... I need to bump the Squeak version now!
frank
OK I start with putting in the latest Cog VM's, 2640 0f 20-Dec-2012.
Cheers,
Herbert
On 1 January 2013 20:07, Frank Shearar frank.shearar@gmail.com wrote:
On 1 January 2013 18:21, Herbert König herbertkoenig@gmx.net wrote:
Hi,
Thanks! System-fbs.506 contains the fix. And I beat the ReleaseSqueakTrunk job into submission:
http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ...
wanted to start on an allInOne by replacing my images and changes and the above link doesn't work. All I can get from Jenkins is #12333.
I see.... that's very weird, given that http://squeakci.org/job/ReleaseSqueakTrunk/30/ has in its artifact link a 12328.
Oh dear. Last I checked, 12333 > 12328. The confusion here is that ReleaseSqueakTrunk should have released something called Squeak4.5-12333.zip. I'm busy fixing that.
frank
Which reminds me... I need to bump the Squeak version now!
frank
OK I start with putting in the latest Cog VM's, 2640 0f 20-Dec-2012.
Cheers,
Herbert
On 1 January 2013 20:28, Frank Shearar frank.shearar@gmail.com wrote:
On 1 January 2013 20:07, Frank Shearar frank.shearar@gmail.com wrote:
On 1 January 2013 18:21, Herbert König herbertkoenig@gmx.net wrote:
Hi,
Thanks! System-fbs.506 contains the fix. And I beat the ReleaseSqueakTrunk job into submission:
http://squeakci.org/job/ReleaseSqueakTrunk/lastSuccessfulBuild/artifact/targ...
wanted to start on an allInOne by replacing my images and changes and the above link doesn't work. All I can get from Jenkins is #12333.
I see.... that's very weird, given that http://squeakci.org/job/ReleaseSqueakTrunk/30/ has in its artifact link a 12328.
Oh dear. Last I checked, 12333 > 12328. The confusion here is that ReleaseSqueakTrunk should have released something called Squeak4.5-12333.zip. I'm busy fixing that.
http://squeakci.org/job/ReleaseSqueakTrunk/34/artifact/target/Squeak4.5-1233...
Thanks for the report!
frank
Which reminds me... I need to bump the Squeak version now!
frank
OK I start with putting in the latest Cog VM's, 2640 0f 20-Dec-2012.
Cheers,
Herbert
On 12/29/12 1:06 PM, "Frank Shearar" frank.shearar@gmail.com wrote:
Other than the fact that the last two builds for SqueakTrunk have hung
- an issue I'm looking into, but wouldn't mind others trying their
luck - are we happy enough with 4.4 that we'd want to ship it?
My gut feel is (and with my Release Manager hat on), judging by the low severity of the few reports we're seeing, that we're there. What do others think?
One thing we _don't_ have is an "All-in-one" one-click type installer for the various OSes. If someone can show me what to do, I can add a job to spit out such a thing.
frank
+1
Good job !!!
Edgar
squeak-dev@lists.squeakfoundation.org
-
Chris Cunnington -
Colin Putney -
David T. Lewis -
Edgar J. De Cleene -
Frank Shearar -
glenpaling -
H. Hirzel -
Herbert König -
Levente Uzonyi -
Nicolas Cellier