[Pharo-project] [ANN] PharoDev-1.3-13173
Hi. IMPORTANT: This is not the final 1.3 release, it just one simple snapshot and one point. We all want a rock-solid Pharo 1.3 release, but that doesn't happens automagically. We all need to start using and testing the image before they are release. It is for the better of all of us. The more we test the more stable will be the release. So...we need your help. What you can do? 1) test test test test test. Use it. Take this image and use it for your regular work. 2) report bugs: http://www.pharo-project.org/community/issue-tracking 3) propose fixes: http://code.google.com/p/pharo/wiki/HowToContribute 4) Fix errors/failures tests 5) Load your OWN packages and projects now. Don't wait until Pharo1.3 is released and then ask "uuhh what happened to XXX? you removed? ohhh but I use it". 6) Do you maintain Metacello configurations? ok, if you test your project and works correctly in Pharo 1.3, please update (or create if you don't yet have it) the #stable, 7) Do you maintain packages included in Pharo? please check we are using the correct versions 8) I would like to see people testing AidaWeb, Magma, Fuel, Moose, DBXTalk, Seaside and all its friends, Zinc, FileSystem, etc, etc, etc. Pharo-1.3-13173 should work with Interpreter VM and with Cog. For Cog I recommend to download the last one from Eliot's page: http://www.mirandabanda.org/files/Cog/VM/ Two little warnings: - The Transcript is read only....and it will probably be roll backed to the previous one - if text editing looks weird....it is Lukas's fault ;) http://www.youtube.com/watch?v=fTMX1f8Lu5w Ok, the image is here: https://gforge.inria.fr/frs/download.php/28517/Pharo-1.3-13173.zip<https://gforge.inria.fr/frs/download.php/28517/Pharo-1.3-13173.zip> And it was build by Hudson: https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.3/111/ Best regards, -- Mariano http://marianopeck.wordpress.com
Thanks, Mariano! We will move the latest Moose development build to this Pharo version next week. Cheers, Doru On 27 Apr 2011, at 10:21, Mariano Martinez Peck wrote:
Hi. IMPORTANT: This is not the final 1.3 release, it just one simple snapshot and one point. We all want a rock-solid Pharo 1.3 release, but that doesn't happens automagically. We all need to start using and testing the image before they are release. It is for the better of all of us. The more we test the more stable will be the release. So...we need your help. What you can do?
1) test test test test test. Use it. Take this image and use it for your regular work. 2) report bugs: http://www.pharo-project.org/community/issue-tracking 3) propose fixes: http://code.google.com/p/pharo/wiki/HowToContribute 4) Fix errors/failures tests 5) Load your OWN packages and projects now. Don't wait until Pharo1.3 is released and then ask "uuhh what happened to XXX? you removed? ohhh but I use it". 6) Do you maintain Metacello configurations? ok, if you test your project and works correctly in Pharo 1.3, please update (or create if you don't yet have it) the #stable, 7) Do you maintain packages included in Pharo? please check we are using the correct versions 8) I would like to see people testing AidaWeb, Magma, Fuel, Moose, DBXTalk, Seaside and all its friends, Zinc, FileSystem, etc, etc, etc.
Pharo-1.3-13173 should work with Interpreter VM and with Cog. For Cog I recommend to download the last one from Eliot's page: http://www.mirandabanda.org/files/Cog/VM/
Two little warnings: - The Transcript is read only....and it will probably be roll backed to the previous one - if text editing looks weird....it is Lukas's fault ;) http://www.youtube.com/watch?v=fTMX1f8Lu5w
Ok, the image is here: https://gforge.inria.fr/frs/download.php/28517/Pharo-1.3-13173.zip
And it was build by Hudson: https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.3/111/
Best regards,
-- Mariano http://marianopeck.wordpress.com
-- www.tudorgirba.com "Sometimes the best solution is not the best solution."
On Wed, Apr 27, 2011 at 10:36 AM, Tudor Girba <tudor.girba@gmail.com> wrote:
Thanks, Mariano!
We will move the latest Moose development build to this Pharo version next week.
Thanks Doru, Moose is always the best Pharo beta tester :) I don't know who do you expect to download Moose from Hudson, but be aware, as always that this image MIGHT be unstable, and that's exactly what you are trying to solve :) So...not only you, but everybody should now that. This is not perfect, it is just one milestone.
Cheers, Doru
On 27 Apr 2011, at 10:21, Mariano Martinez Peck wrote:
Hi. IMPORTANT: This is not the final 1.3 release, it just one simple snapshot and one point. We all want a rock-solid Pharo 1.3 release, but that doesn't happens automagically. We all need to start using and testing the image before they are release. It is for the better of all of us. The more we test the more stable will be the release. So...we need your help. What you can do?
1) test test test test test. Use it. Take this image and use it for your regular work. 2) report bugs: http://www.pharo-project.org/community/issue-tracking 3) propose fixes: http://code.google.com/p/pharo/wiki/HowToContribute 4) Fix errors/failures tests 5) Load your OWN packages and projects now. Don't wait until Pharo1.3 is released and then ask "uuhh what happened to XXX? you removed? ohhh but I use it". 6) Do you maintain Metacello configurations? ok, if you test your project and works correctly in Pharo 1.3, please update (or create if you don't yet have it) the #stable, 7) Do you maintain packages included in Pharo? please check we are using the correct versions 8) I would like to see people testing AidaWeb, Magma, Fuel, Moose, DBXTalk, Seaside and all its friends, Zinc, FileSystem, etc, etc, etc.
Pharo-1.3-13173 should work with Interpreter VM and with Cog. For Cog I recommend to download the last one from Eliot's page: http://www.mirandabanda.org/files/Cog/VM/
Two little warnings: - The Transcript is read only....and it will probably be roll backed to the previous one - if text editing looks weird....it is Lukas's fault ;) http://www.youtube.com/watch?v=fTMX1f8Lu5w
Ok, the image is here: https://gforge.inria.fr/frs/download.php/28517/Pharo-1.3-13173.zip
And it was build by Hudson: https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.3/111/
Best regards,
-- Mariano http://marianopeck.wordpress.com
-- www.tudorgirba.com
"Sometimes the best solution is not the best solution."
-- Mariano http://marianopeck.wordpress.com
Thanks for the initiative Mariano! Some things I have seen in the few minutes I have used it: - The zip includes the __MACOSX folder on the same level that the uncompressed Pharo-1.3-13173 - The browser is way to small I think. Most names aren't shown complete. The user has to resize it almost every time to be useful. - The System -> Update is activated. Is this correct for Pharo (not PharoCore) images? Currently testing the ConfigurationOfMagma in it. If something shows up I will report it also. Cheers El mié, 27-04-2011 a las 10:21 +0200, Mariano Martinez Peck escribió:
Hi. IMPORTANT: This is not the final 1.3 release, it just one simple snapshot and one point. We all want a rock-solid Pharo 1.3 release, but that doesn't happens automagically. We all need to start using and testing the image before they are release. It is for the better of all of us. The more we test the more stable will be the release. So...we need your help. What you can do?
1) test test test test test. Use it. Take this image and use it for your regular work. 2) report bugs: http://www.pharo-project.org/community/issue-tracking 3) propose fixes: http://code.google.com/p/pharo/wiki/HowToContribute 4) Fix errors/failures tests 5) Load your OWN packages and projects now. Don't wait until Pharo1.3 is released and then ask "uuhh what happened to XXX? you removed? ohhh but I use it". 6) Do you maintain Metacello configurations? ok, if you test your project and works correctly in Pharo 1.3, please update (or create if you don't yet have it) the #stable, 7) Do you maintain packages included in Pharo? please check we are using the correct versions 8) I would like to see people testing AidaWeb, Magma, Fuel, Moose, DBXTalk, Seaside and all its friends, Zinc, FileSystem, etc, etc, etc.
Pharo-1.3-13173 should work with Interpreter VM and with Cog. For Cog I recommend to download the last one from Eliot's page: http://www.mirandabanda.org/files/Cog/VM/
Two little warnings: - The Transcript is read only....and it will probably be roll backed to the previous one - if text editing looks weird....it is Lukas's fault ;) http://www.youtube.com/watch?v=fTMX1f8Lu5w
Ok, the image is here: https://gforge.inria.fr/frs/download.php/28517/Pharo-1.3-13173.zip
And it was build by Hudson: https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.3/111/
Best regards,
-- Mariano http://marianopeck.wordpress.com
-- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx
On Wed, Apr 27, 2011 at 5:32 PM, Miguel Cobá <miguel.coba@gmail.com> wrote:
Thanks for the initiative Mariano!
Some things I have seen in the few minutes I have used it:
- The zip includes the __MACOSX folder on the same level that the uncompressed Pharo-1.3-13173
uhh yes, I zip it ;) For official/hudson image I think that doesn't happens.
- The browser is way to small I think. Most names aren't shown complete. The user has to resize it almost every time to be useful.
The browser resizes automatically to the size of the OS windows. If the main windows is bigger, then the default size is bigger.
- The System -> Update is activated. Is this correct for Pharo (not PharoCore) images?
mmmm no :) Thanks for reporting, can you open a ticket ?
Currently testing the ConfigurationOfMagma in it. If something shows up I will report it also.
cool, thanks!
Cheers
El mié, 27-04-2011 a las 10:21 +0200, Mariano Martinez Peck escribió:
Hi. IMPORTANT: This is not the final 1.3 release, it just one simple snapshot and one point. We all want a rock-solid Pharo 1.3 release, but that doesn't happens automagically. We all need to start using and testing the image before they are release. It is for the better of all of us. The more we test the more stable will be the release. So...we need your help. What you can do?
1) test test test test test. Use it. Take this image and use it for your regular work. 2) report bugs: http://www.pharo-project.org/community/issue-tracking 3) propose fixes: http://code.google.com/p/pharo/wiki/HowToContribute 4) Fix errors/failures tests 5) Load your OWN packages and projects now. Don't wait until Pharo1.3 is released and then ask "uuhh what happened to XXX? you removed? ohhh but I use it". 6) Do you maintain Metacello configurations? ok, if you test your project and works correctly in Pharo 1.3, please update (or create if you don't yet have it) the #stable, 7) Do you maintain packages included in Pharo? please check we are using the correct versions 8) I would like to see people testing AidaWeb, Magma, Fuel, Moose, DBXTalk, Seaside and all its friends, Zinc, FileSystem, etc, etc, etc.
Pharo-1.3-13173 should work with Interpreter VM and with Cog. For Cog I recommend to download the last one from Eliot's page: http://www.mirandabanda.org/files/Cog/VM/
Two little warnings: - The Transcript is read only....and it will probably be roll backed to the previous one - if text editing looks weird....it is Lukas's fault ;) http://www.youtube.com/watch?v=fTMX1f8Lu5w
Ok, the image is here: https://gforge.inria.fr/frs/download.php/28517/Pharo-1.3-13173.zip
And it was build by Hudson: https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.3/111/
Best regards,
-- Mariano http://marianopeck.wordpress.com
-- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx
-- Mariano http://marianopeck.wordpress.com
El mié, 27-04-2011 a las 17:47 +0200, Mariano Martinez Peck escribió:
mmmm no :) Thanks for reporting, can you open a ticket ?
Done! http://code.google.com/p/pharo/issues/detail?id=4103 -- Miguel Cobá http://twitter.com/MiguelCobaMtz http://miguel.leugim.com.mx
On 27.04.2011 10:21, Mariano Martinez Peck wrote:
Hi. IMPORTANT: This is not the final 1.3 release, it just one simple snapshot and one point. We all want a rock-solid Pharo 1.3 release, but that doesn't happens automagically. We all need to start using and testing the image before they are release. It is for the better of all of us. The more we test the more stable will be the release. So...we need your help. What you can do?
1) test test test test test. Use it. Take this image and use it for your regular work. 2) report bugs: http://www.pharo-project.org/community/issue-tracking 3) propose fixes: http://code.google.com/p/pharo/wiki/HowToContribute 4) Fix errors/failures tests 5) Load your OWN packages and projects now. Don't wait until Pharo1.3 is released and then ask "uuhh what happened to XXX? you removed? ohhh but I use it". 6) Do you maintain Metacello configurations? ok, if you test your project and works correctly in Pharo 1.3, please update (or create if you don't yet have it) the #stable, 7) Do you maintain packages included in Pharo? please check we are using the correct versions 8) I would like to see people testing AidaWeb, Magma, Fuel, Moose, DBXTalk, Seaside and all its friends, Zinc, FileSystem, etc, etc, etc.
Pharo-1.3-13173 should work with Interpreter VM and with Cog. For Cog I recommend to download the last one from Eliot's page: http://www.mirandabanda.org/files/Cog/VM/
Two little warnings: - The Transcript is read only....and it will probably be roll backed to the previous one - if text editing looks weird....it is Lukas's fault ;) http://www.youtube.com/watch?v=fTMX1f8Lu5w
Ok, the image is here: https://gforge.inria.fr/frs/download.php/28517/Pharo-1.3-13173.zip <https://gforge.inria.fr/frs/download.php/28517/Pharo-1.3-13173.zip>
And it was build by Hudson: https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.3/111/
I did a short test with the latest Seaside against Core. Everything seems to be working so far. general impressions: - some way to clear the Transcript would be nice (other than Transcript clear) eg. a Button - some way to select stuff in the transcript would be nice - what happened to the backport button in Monticello? I found two undeclareds: - ZnServer class >> #initialize references AutoStart - OBDefinition >> #doItReceiver references FakeClassPool -> some small migration guide would be nice, maybe even a Lint rule that checks for removed globals ;-) Cheers Philippe
On 27 Apr 2011, at 18:27, Philippe Marschall wrote:
- ZnServer class >> #initialize references AutoStart
Zn is not a standard part of this image, so it must have come with Seaside ? If so, that would be cool, that is something that I want ! Anyway, ZnServer class>>initialize Smalltalk addToStartUpList: self after: AutoStart. Smalltalk addToShutDownList: self Indeed AutoStart seems to be gone. I just picked that code up somewhere, what should it have to be then ? Apart from that loading error, all Zn tests are green. Thx, Sven
On Wed, Apr 27, 2011 at 6:41 PM, Sven Van Caekenberghe <sven@beta9.be>wrote:
On 27 Apr 2011, at 18:27, Philippe Marschall wrote:
- ZnServer class >> #initialize references AutoStart
Zn is not a standard part of this image, so it must have come with Seaside ? If so, that would be cool, that is something that I want !
Anyway,
ZnServer class>>initialize Smalltalk addToStartUpList: self after: AutoStart.
Normally, Smalltalk addToStartUpList: self is enought. The #addToStartUpList:after: is ONLY when you depend on someone else starting first, which is not normally the case, Hence being at the end is fine. I don't know Zinc needs, thus.
Smalltalk addToShutDownList: self
Indeed AutoStart seems to be gone. I just picked that code up somewhere, what should it have to be then ?
Apart from that loading error, all Zn tests are green.
Thx,
Sven
-- Mariano http://marianopeck.wordpress.com
On 27.04.2011 18:41, Sven Van Caekenberghe wrote:
On 27 Apr 2011, at 18:27, Philippe Marschall wrote:
- ZnServer class >> #initialize references AutoStart
Zn is not a standard part of this image, so it must have come with Seaside ?
Yeah, I built from Core and ran some of the functional tests with: - AJP - Comanche Light - Swazoo - Zinc and found a bug in Zinc :-P Cheers Philippe
On 27 Apr 2011, at 19:19, Philippe Marschall wrote:
and found a bug in Zinc :-P
Name: Zinc-HTTP-SvenVanCaekenberghe.147 Author: SvenVanCaekenberghe Time: 27 April 2011, 7:42:51 pm UUID: b2b69990-95ff-40bc-9ff0-6cb11dc96a24 Ancestors: Zinc-HTTP-SvenVanCaekenberghe.146 changed ZnServer class>>#initialize not to do a Smalltalk #addToStartUpList:after: but just use the plain #addToStartUpList: (we only depend on networking and multi-processing but those will probably be OK) Thx, Philippe & Mariano! Sven PS: Hopefully, SS makes this a persistent change ;-)
In PharoDev-1.3.-13173 While loading Moose there's a 'Transcript open' in loadDefault. This image's Transcript does not understand #open. It's preventing clear installation of moose. Best regards, CdAB
Thanks for reporting. I guess it is because the new Transcript is not yet 100% compatible with the old one. If you still want to try Moose, please just comment the Transcript open part and let us know what happens. Cheers, Doru On 27 Apr 2011, at 21:56, Casimiro de Almeida Barreto wrote:
In PharoDev-1.3.-13173
While loading Moose there's a 'Transcript open' in loadDefault. This image's Transcript does not understand #open. It's preventing clear installation of moose.
Best regards,
CdAB
-- www.tudorgirba.com "Problem solving efficiency grows with the abstractness level of problem understanding."
Em 27-04-2011 17:13, Tudor Girba escreveu:
Thanks for reporting. I guess it is because the new Transcript is not yet 100% compatible with the old one. If you still want to try Moose, please just comment the Transcript open part and let us know what happens. That was what I did. Hence "not clean installation". But purpose of e-mail was to post a "trouble ticket"... That's why sometimes I put posts like this. Cheers, Doru
On 27 Apr 2011, at 21:56, Casimiro de Almeida Barreto wrote:
In PharoDev-1.3.-13173
While loading Moose there's a 'Transcript open' in loadDefault. This image's Transcript does not understand #open. It's preventing clear installation of moose.
Best regards,
CdAB
-- www.tudorgirba.com
"Problem solving efficiency grows with the abstractness level of problem understanding."
But Zinc will be soon part of core. Probably even later today :) On Apr 27, 2011, at 6:41 PM, Sven Van Caekenberghe wrote:
On 27 Apr 2011, at 18:27, Philippe Marschall wrote:
- ZnServer class >> #initialize references AutoStart
Zn is not a standard part of this image, so it must have come with Seaside ? If so, that would be cool, that is something that I want !
Anyway,
ZnServer class>>initialize Smalltalk addToStartUpList: self after: AutoStart. Smalltalk addToShutDownList: self
Indeed AutoStart seems to be gone. I just picked that code up somewhere, what should it have to be then ?
Apart from that loading error, all Zn tests are green.
Thx,
Sven
On Wed, Apr 27, 2011 at 3:21 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
Hi. IMPORTANT: This is not the final 1.3 release, it just one simple snapshot and one point. We all want a rock-solid Pharo 1.3 release, but that doesn't happens automagically. We all need to start using and testing the image before they are release. It is for the better of all of us. The more we test the more stable will be the release. So...we need your help. What you can do?
1) test test test test test. Use it. Take this image and use it for your regular work. 2) report bugs: http://www.pharo-project.org/community/issue-tracking 3) propose fixes: http://code.google.com/p/pharo/wiki/HowToContribute 4) Fix errors/failures tests 5) Load your OWN packages and projects now. Don't wait until Pharo1.3 is released and then ask "uuhh what happened to XXX? you removed? ohhh but I use it". 6) Do you maintain Metacello configurations? ok, if you test your project and works correctly in Pharo 1.3, please update (or create if you don't yet have it) the #stable, 7) Do you maintain packages included in Pharo? please check we are using the correct versions 8) I would like to see people testing AidaWeb, Magma, Fuel, Moose, DBXTalk, Seaside and all its friends, Zinc, FileSystem, etc, etc, etc.
Pharo-1.3-13173Â should work with Interpreter VM and with Cog. For Cog I recommend to download the last one from Eliot's page: http://www.mirandabanda.org/files/Cog/VM/
I try with VM Squeak 4.2.5beta1U on mac os x 10.6.7 but the image is not launch at all. No problem to launch the image with last cog VM. -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/
On Thu, Apr 28, 2011 at 5:56 AM, Serge Stinckwich < serge.stinckwich@gmail.com> wrote:
On Wed, Apr 27, 2011 at 3:21 PM, Mariano Martinez Peck <marianopeck@gmail.com> wrote:
Hi. IMPORTANT: This is not the final 1.3 release, it just one simple snapshot and one point. We all want a rock-solid Pharo 1.3 release, but that doesn't happens automagically. We all need to start using and testing the image before they are release. It is for the better of all of us. The more we test the more stable will be the release. So...we need your help. What you can do?
1) test test test test test. Use it. Take this image and use it for your regular work. 2) report bugs: http://www.pharo-project.org/community/issue-tracking 3) propose fixes: http://code.google.com/p/pharo/wiki/HowToContribute 4) Fix errors/failures tests 5) Load your OWN packages and projects now. Don't wait until Pharo1.3 is released and then ask "uuhh what happened to XXX? you removed? ohhh but I use it". 6) Do you maintain Metacello configurations? ok, if you test your project and works correctly in Pharo 1.3, please update (or create if you don't yet have it) the #stable, 7) Do you maintain packages included in Pharo? please check we are using the correct versions 8) I would like to see people testing AidaWeb, Magma, Fuel, Moose, DBXTalk, Seaside and all its friends, Zinc, FileSystem, etc, etc, etc.
Pharo-1.3-13173 should work with Interpreter VM and with Cog. For Cog I recommend to download the last one from Eliot's page: http://www.mirandabanda.org/files/Cog/VM/
I try with VM Squeak 4.2.5beta1U on mac os x 10.6.7 but the image is not launch at all. No problem to launch the image with last cog VM.
grrrr sorry my bad. I opeed the image (with cog) to re-save it with another name. If you take the one from hudson (same image) it should work: https://pharo-ic.lille.inria.fr/hudson/view/Pharo/job/Pharo%201.3/111/
-- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Every DSL ends up being Smalltalk http://doesnotunderstand.org/
-- Mariano http://marianopeck.wordpress.com
participants (8)
-
Casimiro de Almeida Barreto -
Mariano Martinez Peck -
Miguel Cobá -
Philippe Marschall -
Serge Stinckwich -
Stéphane Ducasse -
Sven Van Caekenberghe -
Tudor Girba