[ANN] Pharo 7.0 released!
Pharo 7.0 released! =============== Dear World and dynamic language lovers: The time has come for Pharo 7.0! Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. This is our most significant release yet. Here are the key highlights of this release: ⢠Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability. The 64-bit version is now recommended for Linux and Mac, and is provided as technical preview for Windows. ⢠Pharo comes with a new version of the PharoLauncher (https://pharo.org/download): THE tool to manage your distributions (access to regular versions, jenkins builds, and older versions). ⢠Pharo build has a fully new build process that supports its full bootstrap from sources. This will enable the production to specific (micro) images. ⢠Iceberg, the git client for Pharo has been significantly improved, and is the default CMS. ⢠Calypso, the angular stone of PharoThings, is the new system Pharo browser. It replaces Nautilus and brings better remote working and more advanced browsing capabilities. ⢠IoT is now an important part of Pharo. Installing PharoThings (https://github.com/pharo-iot/PharoThings) provides an impressive amount of tools to develop applications in small devices. ⢠The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved to work properly on Windows 64-bit. Pharo 70âs new infrastructure and process set the stage for a new generation of version. The visibility of GitHub combined with the powerful tools that have been validated with more than one year of beta testing is massively pay off. These are just the more prominent highlights, but the details are just as important. We have closed a massive amount of issues: 2142 issues! (A comprehensive changelog can be found at: https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo70ChangeL...). While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 7.0 image was contributed by more than 75 people. Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release: Gabriel Omar Cotelli, Gustavo Santos, Marcus Denker, Torsten Bergmann, Esteban Lorenzano, Bernardo Ezequiel Contreras, Guille Polito, Pablo Tesone, Yoan Geran, Stéphane Ducasse, Cyril Ferlicot, Vincent Blondeau, Denis Kudriashov, Julien Delplanque, Tim Mackinnon, Max Leske, Andrew P. Black, Tomohiro Oda, Clément Béra, Ben Coman, Eric Gade, Yuriy Tymchuk, Nicolas Cellier, Biyalou-Sama Asbath, Myroslava, Sean DeNigris, Juraj Kubelka, Noury Bouraqadi, Holger Freyther, Geoff Reedy, Norbert Hartl, Paul DeBruicker, Alain Plantec, MartÃn Dias, Peter Uhnak, Tomohiro Oda, Benoît Verhaeghe, Santiago Bragagnolo, Wouter van Zuilen, Bernhard Pieber, Damien Pollet, Geoff Hill, Hans-Martin Mosner, Ronie Salgado, Philippe Back, Aliaksei Syrel, Dayne Guerra, Rafael Luque, Serge Stinckwich, Vincent Aranega, Hernán Morales Durand, Petr Fischer, Rajula Vineet Reddy, Alexandre Bergel, Esteban A. Maringolo, Jan BlizniÄenko, Johan Brichau, Luc Fabresse, Quentin Ducasse, Sébastien Roccaserra, Stephan Eggermont, Sven Van Caekenberghe, Takano Mitsuhiro, Pavel Krivanek, Allex Oliveira, Christophe Demarey, Lionel Akue, Nicolai Hess, Martin McClure, Alistair Grant, Pierre Tsapliayev, Milton Mamani, Matteo Marra, Thomas Dupriez, Asbathou Biyalou-Sama. (If you contributed with Pharo 7.0 development in any way and we missed your name, please send us a mail and we will add you). Enjoy! The Pharo Team Try Pharo: http://pharo.org/download Learn Pharo: http://pharo.org/documentation
Upvote links: https://www.reddit.com/r/programming/comments/aimwlh/pharo_70_released/ <https://www.reddit.com/r/programming/comments/aimwlh/pharo_70_released/> https://news.ycombinator.com/item?id=18968116 <https://news.ycombinator.com/item?id=18968116> Cheers! Esteban
On 22 Jan 2019, at 14:36, Esteban Lorenzano <estebanlm@gmail.com> wrote:
Pharo 7.0 released! ===============
Dear World and dynamic language lovers:
The time has come for Pharo 7.0!
Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback.
<pastedGraphic.png>
This is our most significant release yet. Here are the key highlights of this release:
⢠Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability. The 64-bit version is now recommended for Linux and Mac, and is provided as technical preview for Windows. ⢠Pharo comes with a new version of the PharoLauncher (https://pharo.org/download <https://pharo.org/download>): THE tool to manage your distributions (access to regular versions, jenkins builds, and older versions). ⢠Pharo build has a fully new build process that supports its full bootstrap from sources. This will enable the production to specific (micro) images. ⢠Iceberg, the git client for Pharo has been significantly improved, and is the default CMS. ⢠Calypso, the angular stone of PharoThings, is the new system Pharo browser. It replaces Nautilus and brings better remote working and more advanced browsing capabilities. ⢠IoT is now an important part of Pharo. Installing PharoThings (https://github.com/pharo-iot/PharoThings <https://github.com/pharo-iot/PharoThings>) provides an impressive amount of tools to develop applications in small devices. ⢠The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved to work properly on Windows 64-bit.
Pharo 70âs new infrastructure and process set the stage for a new generation of version. The visibility of GitHub combined with the powerful tools that have been validated with more than one year of beta testing is massively pay off.
These are just the more prominent highlights, but the details are just as important.
We have closed a massive amount of issues: 2142 issues! (A comprehensive changelog can be found at: https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo70ChangeL... <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo70ChangeL...>).
While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 7.0 image was contributed by more than 75 people.
Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release:
Gabriel Omar Cotelli, Gustavo Santos, Marcus Denker, Torsten Bergmann, Esteban Lorenzano, Bernardo Ezequiel Contreras, Guille Polito, Pablo Tesone, Yoan Geran, Stéphane Ducasse, Cyril Ferlicot, Vincent Blondeau, Denis Kudriashov, Julien Delplanque, Tim Mackinnon, Max Leske, Andrew P. Black, Tomohiro Oda, Clément Béra, Ben Coman, Eric Gade, Yuriy Tymchuk, Nicolas Cellier, Biyalou-Sama Asbath, Myroslava, Sean DeNigris, Juraj Kubelka, Noury Bouraqadi, Holger Freyther, Geoff Reedy, Norbert Hartl, Paul DeBruicker, Alain Plantec, MartÃn Dias, Peter Uhnak, Tomohiro Oda, Benoît Verhaeghe, Santiago Bragagnolo, Wouter van Zuilen, Bernhard Pieber, Damien Pollet, Geoff Hill, Hans-Martin Mosner, Ronie Salgado, Philippe Back, Aliaksei Syrel, Dayne Guerra, Rafael Luque, Serge Stinckwich, Vincent Aranega, Hernán Morales Durand, Petr Fischer, Rajula Vineet Reddy, Alexandre Bergel, Esteban A. Maringolo, Jan BlizniÄenko, Johan Brichau, Luc Fabresse, Quentin Ducasse, Sébastien Roccaserra, Stephan Eggermont, Sven Van Caekenberghe, Takano Mitsuhiro, Pavel Krivanek, Allex Oliveira, Christophe Demarey, Lionel Akue, Nicolai Hess, Martin McClure, Alistair Grant, Pierre Tsapliayev, Milton Mamani, Matteo Marra, Thomas Dupriez, Asbathou Biyalou-Sama. (If you contributed with Pharo 7.0 development in any way and we missed your name, please send us a mail and we will add you).
Enjoy! The Pharo Team
Try Pharo: http://pharo.org/download <http://pharo.org/download> Learn Pharo: http://pharo.org/documentation
On 22 Jan 2019, at 14:39, Esteban Lorenzano <estebanlm@gmail.com> wrote:
Please join, this is going really well: 100+ upvotes, 60+ comments (both are important). Let's keep the momentum going (this is a unique chance to get some publicity).
The Discord channel could use some human replies as well, some newcomers are coming with basic questions about getting started with Pharo (and Pharo Launcher), so basic that I don't have a canonical answer (because I work around these issues using my shenanigans). Esteban A. Maringolo El mar., 22 ene. 2019 a las 13:03, Sven Van Caekenberghe (<sven@stfx.eu>) escribió:
On 22 Jan 2019, at 14:39, Esteban Lorenzano <estebanlm@gmail.com> wrote:
Please join, this is going really well: 100+ upvotes, 60+ comments (both are important). Let's keep the momentum going (this is a unique chance to get some publicity).
Hi, On HackerNews, people are trying to run the factorial example from the main page and that does not work. It currently looks like this: $ curl https://get.pharo.org | bash $ ./pharo Pharo.image eval "42 factorialâ But, the path is incorrect. It should probably be more like: $ wget -O- https://get.pharo.org/64/stable | bash $ ./pharo Pharo.image eval "42 factorialâ Somehow curl did not work on my machine. It says: $ https://get.pharo.org/64/stable | bash bash: https://get.pharo.org/64/stable: No such file or directory bash-3.2$ curl https://get.pharo.org/64/stable | bash % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Couldn't connect to server Cheers, Doru
On Jan 22, 2019, at 6:59 PM, Esteban Maringolo <emaringolo@gmail.com> wrote:
The Discord channel could use some human replies as well, some newcomers are coming with basic questions about getting started with Pharo (and Pharo Launcher), so basic that I don't have a canonical answer (because I work around these issues using my shenanigans).
Esteban A. Maringolo
El mar., 22 ene. 2019 a las 13:03, Sven Van Caekenberghe (<sven@stfx.eu>) escribió:
On 22 Jan 2019, at 14:39, Esteban Lorenzano <estebanlm@gmail.com> wrote:
Please join, this is going really well: 100+ upvotes, 60+ comments (both are important). Let's keep the momentum going (this is a unique chance to get some publicity).
-- www.feenk.com "Things happen when they happen, not when you talk about them happening."
On 22 Jan 2019, at 21:26, Tudor Girba <tudor@tudorgirba.com> wrote:
Hi,
On HackerNews, people are trying to run the factorial example from the main page and that does not work. It currently looks like this:
$ curl https://get.pharo.org | bash $ ./pharo Pharo.image eval "42 factorialâ
But, the path is incorrect. It should probably be more like:
$ wget -O- https://get.pharo.org/64/stable | bash $ ./pharo Pharo.image eval "42 factorialâ
Somehow curl did not work on my machine. It says: $ https://get.pharo.org/64/stable | bash bash: https://get.pharo.org/64/stable: No such file or directory bash-3.2$ curl https://get.pharo.org/64/stable | bash % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Couldn't connect to server
Damn it. I fixed it (and made it point to 64bit which will work better on linux in general) Esteban
Cheers, Doru
On Jan 22, 2019, at 6:59 PM, Esteban Maringolo <emaringolo@gmail.com> wrote:
The Discord channel could use some human replies as well, some newcomers are coming with basic questions about getting started with Pharo (and Pharo Launcher), so basic that I don't have a canonical answer (because I work around these issues using my shenanigans).
Esteban A. Maringolo
El mar., 22 ene. 2019 a las 13:03, Sven Van Caekenberghe (<sven@stfx.eu>) escribió:
On 22 Jan 2019, at 14:39, Esteban Lorenzano <estebanlm@gmail.com> wrote:
Please join, this is going really well: 100+ upvotes, 60+ comments (both are important). Let's keep the momentum going (this is a unique chance to get some publicity).
-- www.feenk.com
"Things happen when they happen, not when you talk about them happening."
Great. I confirm that it works now :) Doru
On Jan 22, 2019, at 9:49 PM, Esteban Lorenzano <estebanlm@gmail.com> wrote:
On 22 Jan 2019, at 21:26, Tudor Girba <tudor@tudorgirba.com> wrote:
Hi,
On HackerNews, people are trying to run the factorial example from the main page and that does not work. It currently looks like this:
$ curl https://get.pharo.org | bash $ ./pharo Pharo.image eval "42 factorialâ
But, the path is incorrect. It should probably be more like:
$ wget -O- https://get.pharo.org/64/stable | bash $ ./pharo Pharo.image eval "42 factorialâ
Somehow curl did not work on my machine. It says: $ https://get.pharo.org/64/stable | bash bash: https://get.pharo.org/64/stable: No such file or directory bash-3.2$ curl https://get.pharo.org/64/stable | bash % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (7) Couldn't connect to server
Damn it. I fixed it (and made it point to 64bit which will work better on linux in general)
Esteban
Cheers, Doru
On Jan 22, 2019, at 6:59 PM, Esteban Maringolo <emaringolo@gmail.com> wrote:
The Discord channel could use some human replies as well, some newcomers are coming with basic questions about getting started with Pharo (and Pharo Launcher), so basic that I don't have a canonical answer (because I work around these issues using my shenanigans).
Esteban A. Maringolo
El mar., 22 ene. 2019 a las 13:03, Sven Van Caekenberghe (<sven@stfx.eu>) escribió:
On 22 Jan 2019, at 14:39, Esteban Lorenzano <estebanlm@gmail.com> wrote:
Please join, this is going really well: 100+ upvotes, 60+ comments (both are important). Let's keep the momentum going (this is a unique chance to get some publicity).
-- www.feenk.com
"Things happen when they happen, not when you talk about them happening."
-- www.feenk.com "Innovation comes in the least expected form. That is, if it is expected, it already happened."
On 23/01/19 2:19 AM, Esteban Lorenzano wrote:
$ curl https://get.pharo.org | bash $ ./pharo Pharo.image eval "42 factorialâ
This should be "curl -L" so that redirects are followed automatically. Regards .. Subbu
EstebanLM wrote
Wow! 13 hours without any hardcore flame wars. We are improving ;-) EstebanLM wrote
https://www.reddit.com/r/programming/comments/aimwlh/pharo_70_released/
Ew, not as warm and fuzzy here ha ha ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
Am 23.01.2019 um 04:13 schrieb Sean P. DeNigris <sean@clipperadams.com>:
EstebanLM wrote
Wow! 13 hours without any hardcore flame wars. We are improving ;-)
EstebanLM wrote
https://www.reddit.com/r/programming/comments/aimwlh/pharo_70_released/
Ew, not as warm and fuzzy here ha ha
Well, Iâm always amazed how negative people are. But on the other hand there is some truth in there. If we donât focus on how people encounter pharo the first time it is not getting easier. And we should professionalize our environment. That there was a gateway timeout when people tried to access it is just not good. I donât mind if it is a ridiculous setting in Inria or if it is a prototypical, not maintained CMS that is the root of trouble. Norbert
----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
El mié., 23 ene. 2019 a las 4:50, Norbert Hartl (<norbert@hartl.name>) escribió:
Am 23.01.2019 um 04:13 schrieb Sean P. DeNigris <sean@clipperadams.com>:
https://www.reddit.com/r/programming/comments/aimwlh/pharo_70_released/ Ew, not as warm and fuzzy here ha ha
Well, Iâm always amazed how negative people are. But on the other hand there is some truth in there.
Internet comments are mean, but if somebody wants to try something and it doesn't work or is too cumbersome (for his standards), then they never get to experience the good part and just rant about what they went through. Thing is, we're not the test group to measure whether it's cumbersome or not, unless it is somebody who does UX a lot, and even so, it is better to check with "foreigners".
If we donât focus on how people encounter pharo the first time it is not getting easier.
"Make easy things easy, and hard things possible." Considering the huge version change log I believe we started from the last part :) In any case, I think Pharo 7 is a huge milestone so let's celebrate and thank to all who contributed. We can improve the above described issues in the next major release. Regards.
NorbertHartl wrote
But on the other hand there is some truth in there
True. I thought most of the suggestions I read on Hacker News were particularly constructive. ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
I don't understand why the mooc is pushed when people want documentation. Some people just want to read. I kept pushing on http://books.pharo.org - I think we don't push that enough. Tons of great info there.
On Jan 23, 2019, at 5:35 PM, Sean P. DeNigris <sean@clipperadams.com> wrote:
I thought most of the suggestions I read on Hacker News were particularly constructive.
It can't be more clearly articulated. Negative feedbacks are more valuable than positive feedbacks. Hilaire Le 23/01/2019 à 08:49, Norbert Hartl a écrit :
Well, Iâm always amazed how negative people are. But on the other hand there is some truth in there. If we donât focus on how people encounter pharo the first time it is not getting easier.
-- Dr. Geo http://drgeo.eu
Great work! Thanks everyone for all the effort! Doru
On Jan 22, 2019, at 2:36 PM, Esteban Lorenzano <estebanlm@gmail.com> wrote:
Pharo 7.0 released! ===============
Dear World and dynamic language lovers:
The time has come for Pharo 7.0!
Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback.
<pastedGraphic.png>
This is our most significant release yet. Here are the key highlights of this release:
⢠Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability. The 64-bit version is now recommended for Linux and Mac, and is provided as technical preview for Windows. ⢠Pharo comes with a new version of the PharoLauncher (https://pharo.org/download): THE tool to manage your distributions (access to regular versions, jenkins builds, and older versions). ⢠Pharo build has a fully new build process that supports its full bootstrap from sources. This will enable the production to specific (micro) images. ⢠Iceberg, the git client for Pharo has been significantly improved, and is the default CMS. ⢠Calypso, the angular stone of PharoThings, is the new system Pharo browser. It replaces Nautilus and brings better remote working and more advanced browsing capabilities. ⢠IoT is now an important part of Pharo. Installing PharoThings (https://github.com/pharo-iot/PharoThings) provides an impressive amount of tools to develop applications in small devices. ⢠The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved to work properly on Windows 64-bit.
Pharo 70âs new infrastructure and process set the stage for a new generation of version. The visibility of GitHub combined with the powerful tools that have been validated with more than one year of beta testing is massively pay off.
These are just the more prominent highlights, but the details are just as important.
We have closed a massive amount of issues: 2142 issues! (A comprehensive changelog can be found at: https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo70ChangeL...).
While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 7.0 image was contributed by more than 75 people.
Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release:
Gabriel Omar Cotelli, Gustavo Santos, Marcus Denker, Torsten Bergmann, Esteban Lorenzano, Bernardo Ezequiel Contreras, Guille Polito, Pablo Tesone, Yoan Geran, Stéphane Ducasse, Cyril Ferlicot, Vincent Blondeau, Denis Kudriashov, Julien Delplanque, Tim Mackinnon, Max Leske, Andrew P. Black, Tomohiro Oda, Clément Béra, Ben Coman, Eric Gade, Yuriy Tymchuk, Nicolas Cellier, Biyalou-Sama Asbath, Myroslava, Sean DeNigris, Juraj Kubelka, Noury Bouraqadi, Holger Freyther, Geoff Reedy, Norbert Hartl, Paul DeBruicker, Alain Plantec, MartÃn Dias, Peter Uhnak, Tomohiro Oda, Benoît Verhaeghe, Santiago Bragagnolo, Wouter van Zuilen, Bernhard Pieber, Damien Pollet, Geoff Hill, Hans-Martin Mosner, Ronie Salgado, Philippe Back, Aliaksei Syrel, Dayne Guerra, Rafael Luque, Serge Stinckwich, Vincent Aranega, Hernán Morales Durand, Petr Fischer, Rajula Vineet Reddy, Alexandre Bergel, Esteban A. Maringolo, Jan BlizniÄenko, Johan Brichau, Luc Fabresse, Quentin Ducasse, Sébastien Roccaserra, Stephan Eggermont, Sven Van Caekenberghe, Takano Mitsuhiro, Pavel Krivanek, Allex Oliveira, Christophe Demarey, Lionel Akue, Nicolai Hess, Martin McClure, Alistair Grant, Pierre Tsapliayev, Milton Mamani, Matteo Marra, Thomas Dupriez, Asbathou Biyalou-Sama. (If you contributed with Pharo 7.0 development in any way and we missed your name, please send us a mail and we will add you).
Enjoy! The Pharo Team
Try Pharo: http://pharo.org/download Learn Pharo: http://pharo.org/documentation
-- www.feenk.com "What is more important: To be happy, or to make happy?"
Great work! And I want to say that with the new process and iceberg version is so much simple to contribute! On Tue, Jan 22, 2019 at 10:37 AM Esteban Lorenzano <estebanlm@gmail.com> wrote:
Pharo 7.0 released! ===============
Dear World and dynamic language lovers:
The time has come for Pharo 7.0!
Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback.
[image: pastedGraphic.png]
This is our most significant release yet. Here are the key highlights of this release:
⢠Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability. The 64-bit version is now recommended for Linux and Mac, and is provided as technical preview for Windows. ⢠Pharo comes with a new version of the PharoLauncher ( https://pharo.org/download): THE tool to manage your distributions (access to regular versions, jenkins builds, and older versions). ⢠Pharo build has a fully new build process that supports its full bootstrap from sources. This will enable the production to specific (micro) images. ⢠Iceberg, the git client for Pharo has been significantly improved, and is the default CMS. ⢠Calypso, the angular stone of PharoThings, is the new system Pharo browser. It replaces Nautilus and brings better remote working and more advanced browsing capabilities. ⢠IoT is now an important part of Pharo. Installing PharoThings ( https://github.com/pharo-iot/PharoThings) provides an impressive amount of tools to develop applications in small devices. ⢠The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved to work properly on Windows 64-bit.
Pharo 70âs new infrastructure and process set the stage for a new generation of version. The visibility of GitHub combined with the powerful tools that have been validated with more than one year of beta testing is massively pay off.
These are just the more prominent highlights, but the details are just as important.
We have closed a massive amount of issues: 2142 issues! (A comprehensive changelog can be found at: https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo70ChangeL... ).
While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 7.0 image was contributed by more than 75 people.
Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release:
Gabriel Omar Cotelli, Gustavo Santos, Marcus Denker, Torsten Bergmann, Esteban Lorenzano, Bernardo Ezequiel Contreras, Guille Polito, Pablo Tesone, Yoan Geran, Stéphane Ducasse, Cyril Ferlicot, Vincent Blondeau, Denis Kudriashov, Julien Delplanque, Tim Mackinnon, Max Leske, Andrew P. Black, Tomohiro Oda, Clément Béra, Ben Coman, Eric Gade, Yuriy Tymchuk, Nicolas Cellier, Biyalou-Sama Asbath, Myroslava, Sean DeNigris, Juraj Kubelka, Noury Bouraqadi, Holger Freyther, Geoff Reedy, Norbert Hartl, Paul DeBruicker, Alain Plantec, MartÃn Dias, Peter Uhnak, Tomohiro Oda, Benoît Verhaeghe, Santiago Bragagnolo, Wouter van Zuilen, Bernhard Pieber, Damien Pollet, Geoff Hill, Hans-Martin Mosner, Ronie Salgado, Philippe Back, Aliaksei Syrel, Dayne Guerra, Rafael Luque, Serge Stinckwich, Vincent Aranega, Hernán Morales Durand, Petr Fischer, Rajula Vineet Reddy, Alexandre Bergel, Esteban A. Maringolo, Jan BlizniÄenko, Johan Brichau, Luc Fabresse, Quentin Ducasse, Sébastien Roccaserra, Stephan Eggermont, Sven Van Caekenberghe, Takano Mitsuhiro, Pavel Krivanek, Allex Oliveira, Christophe Demarey, Lionel Akue, Nicolai Hess, Martin McClure, Alistair Grant, Pierre Tsapliayev, Milton Mamani, Matteo Marra, Thomas Dupriez, Asbathou Biyalou-Sama. (If you contributed with Pharo 7.0 development in any way and we missed your name, please send us a mail and we will add you).
Enjoy! The Pharo Team
Try Pharo: http://pharo.org/download Learn Pharo: http://pharo.org/documentation
Thank you, everybody, this is a massive collaborative effort, something to be proud of.
On 22 Jan 2019, at 14:36, Esteban Lorenzano <estebanlm@gmail.com> wrote:
Pharo 7.0 released! ===============
Dear World and dynamic language lovers:
The time has come for Pharo 7.0!
Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback.
<pastedGraphic.png>
This is our most significant release yet. Here are the key highlights of this release:
⢠Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability. The 64-bit version is now recommended for Linux and Mac, and is provided as technical preview for Windows. ⢠Pharo comes with a new version of the PharoLauncher (https://pharo.org/download): THE tool to manage your distributions (access to regular versions, jenkins builds, and older versions). ⢠Pharo build has a fully new build process that supports its full bootstrap from sources. This will enable the production to specific (micro) images. ⢠Iceberg, the git client for Pharo has been significantly improved, and is the default CMS. ⢠Calypso, the angular stone of PharoThings, is the new system Pharo browser. It replaces Nautilus and brings better remote working and more advanced browsing capabilities. ⢠IoT is now an important part of Pharo. Installing PharoThings (https://github.com/pharo-iot/PharoThings) provides an impressive amount of tools to develop applications in small devices. ⢠The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved to work properly on Windows 64-bit.
Pharo 70âs new infrastructure and process set the stage for a new generation of version. The visibility of GitHub combined with the powerful tools that have been validated with more than one year of beta testing is massively pay off.
These are just the more prominent highlights, but the details are just as important.
We have closed a massive amount of issues: 2142 issues! (A comprehensive changelog can be found at: https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo70ChangeL...).
While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 7.0 image was contributed by more than 75 people.
Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release:
Gabriel Omar Cotelli, Gustavo Santos, Marcus Denker, Torsten Bergmann, Esteban Lorenzano, Bernardo Ezequiel Contreras, Guille Polito, Pablo Tesone, Yoan Geran, Stéphane Ducasse, Cyril Ferlicot, Vincent Blondeau, Denis Kudriashov, Julien Delplanque, Tim Mackinnon, Max Leske, Andrew P. Black, Tomohiro Oda, Clément Béra, Ben Coman, Eric Gade, Yuriy Tymchuk, Nicolas Cellier, Biyalou-Sama Asbath, Myroslava, Sean DeNigris, Juraj Kubelka, Noury Bouraqadi, Holger Freyther, Geoff Reedy, Norbert Hartl, Paul DeBruicker, Alain Plantec, MartÃn Dias, Peter Uhnak, Tomohiro Oda, Benoît Verhaeghe, Santiago Bragagnolo, Wouter van Zuilen, Bernhard Pieber, Damien Pollet, Geoff Hill, Hans-Martin Mosner, Ronie Salgado, Philippe Back, Aliaksei Syrel, Dayne Guerra, Rafael Luque, Serge Stinckwich, Vincent Aranega, Hernán Morales Durand, Petr Fischer, Rajula Vineet Reddy, Alexandre Bergel, Esteban A. Maringolo, Jan BlizniÄenko, Johan Brichau, Luc Fabresse, Quentin Ducasse, Sébastien Roccaserra, Stephan Eggermont, Sven Van Caekenberghe, Takano Mitsuhiro, Pavel Krivanek, Allex Oliveira, Christophe Demarey, Lionel Akue, Nicolai Hess, Martin McClure, Alistair Grant, Pierre Tsapliayev, Milton Mamani, Matteo Marra, Thomas Dupriez, Asbathou Biyalou-Sama. (If you contributed with Pharo 7.0 development in any way and we missed your name, please send us a mail and we will add you).
Enjoy! The Pharo Team
Try Pharo: http://pharo.org/download Learn Pharo: http://pharo.org/documentation
Congratulations to you all! It has been a hard piece of work which was postponed 9 months. But the changes to collaboration process, build process, 64 bit maturing and huge list of things was worth it. Hopefully the next version is less huge. Happy to be able to take part!!! Norbert
Am 22.01.2019 um 14:36 schrieb Esteban Lorenzano <estebanlm@gmail.com>:
Pharo 7.0 released! ===============
Dear World and dynamic language lovers:
The time has come for Pharo 7.0!
Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback.
<pastedGraphic.png>
This is our most significant release yet. Here are the key highlights of this release:
⢠Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability. The 64-bit version is now recommended for Linux and Mac, and is provided as technical preview for Windows. ⢠Pharo comes with a new version of the PharoLauncher (https://pharo.org/download): THE tool to manage your distributions (access to regular versions, jenkins builds, and older versions). ⢠Pharo build has a fully new build process that supports its full bootstrap from sources. This will enable the production to specific (micro) images. ⢠Iceberg, the git client for Pharo has been significantly improved, and is the default CMS. ⢠Calypso, the angular stone of PharoThings, is the new system Pharo browser. It replaces Nautilus and brings better remote working and more advanced browsing capabilities. ⢠IoT is now an important part of Pharo. Installing PharoThings (https://github.com/pharo-iot/PharoThings) provides an impressive amount of tools to develop applications in small devices. ⢠The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved to work properly on Windows 64-bit.
Pharo 70âs new infrastructure and process set the stage for a new generation of version. The visibility of GitHub combined with the powerful tools that have been validated with more than one year of beta testing is massively pay off.
These are just the more prominent highlights, but the details are just as important.
We have closed a massive amount of issues: 2142 issues! (A comprehensive changelog can be found at: https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo70ChangeL...).
While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 7.0 image was contributed by more than 75 people.
Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release:
Gabriel Omar Cotelli, Gustavo Santos, Marcus Denker, Torsten Bergmann, Esteban Lorenzano, Bernardo Ezequiel Contreras, Guille Polito, Pablo Tesone, Yoan Geran, Stéphane Ducasse, Cyril Ferlicot, Vincent Blondeau, Denis Kudriashov, Julien Delplanque, Tim Mackinnon, Max Leske, Andrew P. Black, Tomohiro Oda, Clément Béra, Ben Coman, Eric Gade, Yuriy Tymchuk, Nicolas Cellier, Biyalou-Sama Asbath, Myroslava, Sean DeNigris, Juraj Kubelka, Noury Bouraqadi, Holger Freyther, Geoff Reedy, Norbert Hartl, Paul DeBruicker, Alain Plantec, MartÃn Dias, Peter Uhnak, Tomohiro Oda, Benoît Verhaeghe, Santiago Bragagnolo, Wouter van Zuilen, Bernhard Pieber, Damien Pollet, Geoff Hill, Hans-Martin Mosner, Ronie Salgado, Philippe Back, Aliaksei Syrel, Dayne Guerra, Rafael Luque, Serge Stinckwich, Vincent Aranega, Hernán Morales Durand, Petr Fischer, Rajula Vineet Reddy, Alexandre Bergel, Esteban A. Maringolo, Jan BlizniÄenko, Johan Brichau, Luc Fabresse, Quentin Ducasse, Sébastien Roccaserra, Stephan Eggermont, Sven Van Caekenberghe, Takano Mitsuhiro, Pavel Krivanek, Allex Oliveira, Christophe Demarey, Lionel Akue, Nicolai Hess, Martin McClure, Alistair Grant, Pierre Tsapliayev, Milton Mamani, Matteo Marra, Thomas Dupriez, Asbathou Biyalou-Sama. (If you contributed with Pharo 7.0 development in any way and we missed your name, please send us a mail and we will add you).
Enjoy! The Pharo Team
Try Pharo: http://pharo.org/download Learn Pharo: http://pharo.org/documentation
Congrats guys. Wish you hard party in Lille :) вÑ, 22 Ñнв. 2019 г. в 13:37, Esteban Lorenzano <estebanlm@gmail.com>:
Pharo 7.0 released! ===============
Dear World and dynamic language lovers:
The time has come for Pharo 7.0!
Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback.
[image: pastedGraphic.png]
This is our most significant release yet. Here are the key highlights of this release:
⢠Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability. The 64-bit version is now recommended for Linux and Mac, and is provided as technical preview for Windows. ⢠Pharo comes with a new version of the PharoLauncher ( https://pharo.org/download): THE tool to manage your distributions (access to regular versions, jenkins builds, and older versions). ⢠Pharo build has a fully new build process that supports its full bootstrap from sources. This will enable the production to specific (micro) images. ⢠Iceberg, the git client for Pharo has been significantly improved, and is the default CMS. ⢠Calypso, the angular stone of PharoThings, is the new system Pharo browser. It replaces Nautilus and brings better remote working and more advanced browsing capabilities. ⢠IoT is now an important part of Pharo. Installing PharoThings ( https://github.com/pharo-iot/PharoThings) provides an impressive amount of tools to develop applications in small devices. ⢠The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved to work properly on Windows 64-bit.
Pharo 70âs new infrastructure and process set the stage for a new generation of version. The visibility of GitHub combined with the powerful tools that have been validated with more than one year of beta testing is massively pay off.
These are just the more prominent highlights, but the details are just as important.
We have closed a massive amount of issues: 2142 issues! (A comprehensive changelog can be found at: https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo70ChangeL... ).
While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 7.0 image was contributed by more than 75 people.
Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release:
Gabriel Omar Cotelli, Gustavo Santos, Marcus Denker, Torsten Bergmann, Esteban Lorenzano, Bernardo Ezequiel Contreras, Guille Polito, Pablo Tesone, Yoan Geran, Stéphane Ducasse, Cyril Ferlicot, Vincent Blondeau, Denis Kudriashov, Julien Delplanque, Tim Mackinnon, Max Leske, Andrew P. Black, Tomohiro Oda, Clément Béra, Ben Coman, Eric Gade, Yuriy Tymchuk, Nicolas Cellier, Biyalou-Sama Asbath, Myroslava, Sean DeNigris, Juraj Kubelka, Noury Bouraqadi, Holger Freyther, Geoff Reedy, Norbert Hartl, Paul DeBruicker, Alain Plantec, MartÃn Dias, Peter Uhnak, Tomohiro Oda, Benoît Verhaeghe, Santiago Bragagnolo, Wouter van Zuilen, Bernhard Pieber, Damien Pollet, Geoff Hill, Hans-Martin Mosner, Ronie Salgado, Philippe Back, Aliaksei Syrel, Dayne Guerra, Rafael Luque, Serge Stinckwich, Vincent Aranega, Hernán Morales Durand, Petr Fischer, Rajula Vineet Reddy, Alexandre Bergel, Esteban A. Maringolo, Jan BlizniÄenko, Johan Brichau, Luc Fabresse, Quentin Ducasse, Sébastien Roccaserra, Stephan Eggermont, Sven Van Caekenberghe, Takano Mitsuhiro, Pavel Krivanek, Allex Oliveira, Christophe Demarey, Lionel Akue, Nicolai Hess, Martin McClure, Alistair Grant, Pierre Tsapliayev, Milton Mamani, Matteo Marra, Thomas Dupriez, Asbathou Biyalou-Sama. (If you contributed with Pharo 7.0 development in any way and we missed your name, please send us a mail and we will add you).
Enjoy! The Pharo Team
Try Pharo: http://pharo.org/download Learn Pharo: http://pharo.org/documentation
Just want to congratulate for the big achievements in this new release. I am trying it right now and it looks very stable! Great work guys! Cheers, Hernán El mar., 22 ene. 2019 a las 10:37, Esteban Lorenzano (<estebanlm@gmail.com>) escribió:
Pharo 7.0 released! ===============
Dear World and dynamic language lovers:
The time has come for Pharo 7.0!
Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback.
[image: pastedGraphic.png]
This is our most significant release yet. Here are the key highlights of this release:
⢠Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability. The 64-bit version is now recommended for Linux and Mac, and is provided as technical preview for Windows. ⢠Pharo comes with a new version of the PharoLauncher ( https://pharo.org/download): THE tool to manage your distributions (access to regular versions, jenkins builds, and older versions). ⢠Pharo build has a fully new build process that supports its full bootstrap from sources. This will enable the production to specific (micro) images. ⢠Iceberg, the git client for Pharo has been significantly improved, and is the default CMS. ⢠Calypso, the angular stone of PharoThings, is the new system Pharo browser. It replaces Nautilus and brings better remote working and more advanced browsing capabilities. ⢠IoT is now an important part of Pharo. Installing PharoThings ( https://github.com/pharo-iot/PharoThings) provides an impressive amount of tools to develop applications in small devices. ⢠The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved to work properly on Windows 64-bit.
Pharo 70âs new infrastructure and process set the stage for a new generation of version. The visibility of GitHub combined with the powerful tools that have been validated with more than one year of beta testing is massively pay off.
These are just the more prominent highlights, but the details are just as important.
We have closed a massive amount of issues: 2142 issues! (A comprehensive changelog can be found at: https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo70ChangeL... ).
While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 7.0 image was contributed by more than 75 people.
Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release:
Gabriel Omar Cotelli, Gustavo Santos, Marcus Denker, Torsten Bergmann, Esteban Lorenzano, Bernardo Ezequiel Contreras, Guille Polito, Pablo Tesone, Yoan Geran, Stéphane Ducasse, Cyril Ferlicot, Vincent Blondeau, Denis Kudriashov, Julien Delplanque, Tim Mackinnon, Max Leske, Andrew P. Black, Tomohiro Oda, Clément Béra, Ben Coman, Eric Gade, Yuriy Tymchuk, Nicolas Cellier, Biyalou-Sama Asbath, Myroslava, Sean DeNigris, Juraj Kubelka, Noury Bouraqadi, Holger Freyther, Geoff Reedy, Norbert Hartl, Paul DeBruicker, Alain Plantec, MartÃn Dias, Peter Uhnak, Tomohiro Oda, Benoît Verhaeghe, Santiago Bragagnolo, Wouter van Zuilen, Bernhard Pieber, Damien Pollet, Geoff Hill, Hans-Martin Mosner, Ronie Salgado, Philippe Back, Aliaksei Syrel, Dayne Guerra, Rafael Luque, Serge Stinckwich, Vincent Aranega, Hernán Morales Durand, Petr Fischer, Rajula Vineet Reddy, Alexandre Bergel, Esteban A. Maringolo, Jan BlizniÄenko, Johan Brichau, Luc Fabresse, Quentin Ducasse, Sébastien Roccaserra, Stephan Eggermont, Sven Van Caekenberghe, Takano Mitsuhiro, Pavel Krivanek, Allex Oliveira, Christophe Demarey, Lionel Akue, Nicolai Hess, Martin McClure, Alistair Grant, Pierre Tsapliayev, Milton Mamani, Matteo Marra, Thomas Dupriez, Asbathou Biyalou-Sama. (If you contributed with Pharo 7.0 development in any way and we missed your name, please send us a mail and we will add you).
Enjoy! The Pharo Team
Try Pharo: http://pharo.org/download Learn Pharo: http://pharo.org/documentation
On 24 Jan 2019, at 09:23, Hernán Morales Durand <hernan.morales@gmail.com> wrote:
Just want to congratulate for the big achievements in this new release. I am trying it right now and it looks very stable! Great work guys!
:) Just for the record, Iâm using same image since 3 monts (and to do some very heavy work). And image has not grown more than normal, and everything still works smooth. So yes, bugs and limitations aside (there will always be one and the other), this may be the most stable version we have made since P3 :P Esteban
Cheers,
Hernán
El mar., 22 ene. 2019 a las 10:37, Esteban Lorenzano (<estebanlm@gmail.com <mailto:estebanlm@gmail.com>>) escribió: Pharo 7.0 released! ===============
Dear World and dynamic language lovers:
The time has come for Pharo 7.0!
Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback.
<pastedGraphic.png>
This is our most significant release yet. Here are the key highlights of this release:
⢠Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability. The 64-bit version is now recommended for Linux and Mac, and is provided as technical preview for Windows. ⢠Pharo comes with a new version of the PharoLauncher (https://pharo.org/download <https://pharo.org/download>): THE tool to manage your distributions (access to regular versions, jenkins builds, and older versions). ⢠Pharo build has a fully new build process that supports its full bootstrap from sources. This will enable the production to specific (micro) images. ⢠Iceberg, the git client for Pharo has been significantly improved, and is the default CMS. ⢠Calypso, the angular stone of PharoThings, is the new system Pharo browser. It replaces Nautilus and brings better remote working and more advanced browsing capabilities. ⢠IoT is now an important part of Pharo. Installing PharoThings (https://github.com/pharo-iot/PharoThings <https://github.com/pharo-iot/PharoThings>) provides an impressive amount of tools to develop applications in small devices. ⢠The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved to work properly on Windows 64-bit.
Pharo 70âs new infrastructure and process set the stage for a new generation of version. The visibility of GitHub combined with the powerful tools that have been validated with more than one year of beta testing is massively pay off.
These are just the more prominent highlights, but the details are just as important.
We have closed a massive amount of issues: 2142 issues! (A comprehensive changelog can be found at: https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo70ChangeL... <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo70ChangeL...>).
While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 7.0 image was contributed by more than 75 people.
Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release:
Gabriel Omar Cotelli, Gustavo Santos, Marcus Denker, Torsten Bergmann, Esteban Lorenzano, Bernardo Ezequiel Contreras, Guille Polito, Pablo Tesone, Yoan Geran, Stéphane Ducasse, Cyril Ferlicot, Vincent Blondeau, Denis Kudriashov, Julien Delplanque, Tim Mackinnon, Max Leske, Andrew P. Black, Tomohiro Oda, Clément Béra, Ben Coman, Eric Gade, Yuriy Tymchuk, Nicolas Cellier, Biyalou-Sama Asbath, Myroslava, Sean DeNigris, Juraj Kubelka, Noury Bouraqadi, Holger Freyther, Geoff Reedy, Norbert Hartl, Paul DeBruicker, Alain Plantec, MartÃn Dias, Peter Uhnak, Tomohiro Oda, Benoît Verhaeghe, Santiago Bragagnolo, Wouter van Zuilen, Bernhard Pieber, Damien Pollet, Geoff Hill, Hans-Martin Mosner, Ronie Salgado, Philippe Back, Aliaksei Syrel, Dayne Guerra, Rafael Luque, Serge Stinckwich, Vincent Aranega, Hernán Morales Durand, Petr Fischer, Rajula Vineet Reddy, Alexandre Bergel, Esteban A. Maringolo, Jan BlizniÄenko, Johan Brichau, Luc Fabresse, Quentin Ducasse, Sébastien Roccaserra, Stephan Eggermont, Sven Van Caekenberghe, Takano Mitsuhiro, Pavel Krivanek, Allex Oliveira, Christophe Demarey, Lionel Akue, Nicolai Hess, Martin McClure, Alistair Grant, Pierre Tsapliayev, Milton Mamani, Matteo Marra, Thomas Dupriez, Asbathou Biyalou-Sama. (If you contributed with Pharo 7.0 development in any way and we missed your name, please send us a mail and we will add you).
Enjoy! The Pharo Team
Try Pharo: http://pharo.org/download <http://pharo.org/download> Learn Pharo: http://pharo.org/documentation <http://pharo.org/documentation>
On Thu, Jan 24, 2019 at 11:17 AM Esteban Lorenzano <estebanlm@gmail.com> wrote:
On 24 Jan 2019, at 09:23, Hernán Morales Durand <hernan.morales@gmail.com> wrote:
Just want to congratulate for the big achievements in this new release. I am trying it right now and it looks very stable! Great work guys!
:) Just for the record, Iâm using same image since 3 monts (and to do some very heavy work). And image has not grown more than normal, and everything still works smooth.
So yes, bugs and limitations aside (there will always be one and the other), this may be the most stable version we have made since P3 :P
Wonderful. Really. Stability is key indeed. Now, how do you deal with freezing images? Because let's be honest, this happens and is super frustrating. As the lead engineer on Pharo, you have for sure interesting tricks on that front. I have been also frustrated by Epica and code recovery because things happened that were "weird" (for the lack of a better factual word). Tricks on that as well? Phil
Esteban
Cheers,
Hernán
El mar., 22 ene. 2019 a las 10:37, Esteban Lorenzano (<estebanlm@gmail.com>) escribió:
Pharo 7.0 released! ===============
Dear World and dynamic language lovers:
The time has come for Pharo 7.0!
Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback.
<pastedGraphic.png>
This is our most significant release yet. Here are the key highlights of this release:
⢠Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability. The 64-bit version is now recommended for Linux and Mac, and is provided as technical preview for Windows. ⢠Pharo comes with a new version of the PharoLauncher ( https://pharo.org/download): THE tool to manage your distributions (access to regular versions, jenkins builds, and older versions). ⢠Pharo build has a fully new build process that supports its full bootstrap from sources. This will enable the production to specific (micro) images. ⢠Iceberg, the git client for Pharo has been significantly improved, and is the default CMS. ⢠Calypso, the angular stone of PharoThings, is the new system Pharo browser. It replaces Nautilus and brings better remote working and more advanced browsing capabilities. ⢠IoT is now an important part of Pharo. Installing PharoThings ( https://github.com/pharo-iot/PharoThings) provides an impressive amount of tools to develop applications in small devices. ⢠The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved to work properly on Windows 64-bit.
Pharo 70âs new infrastructure and process set the stage for a new generation of version. The visibility of GitHub combined with the powerful tools that have been validated with more than one year of beta testing is massively pay off.
These are just the more prominent highlights, but the details are just as important.
We have closed a massive amount of issues: 2142 issues! (A comprehensive changelog can be found at: https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo70ChangeL... ).
While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 7.0 image was contributed by more than 75 people.
Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release:
Gabriel Omar Cotelli, Gustavo Santos, Marcus Denker, Torsten Bergmann, Esteban Lorenzano, Bernardo Ezequiel Contreras, Guille Polito, Pablo Tesone, Yoan Geran, Stéphane Ducasse, Cyril Ferlicot, Vincent Blondeau, Denis Kudriashov, Julien Delplanque, Tim Mackinnon, Max Leske, Andrew P. Black, Tomohiro Oda, Clément Béra, Ben Coman, Eric Gade, Yuriy Tymchuk, Nicolas Cellier, Biyalou-Sama Asbath, Myroslava, Sean DeNigris, Juraj Kubelka, Noury Bouraqadi, Holger Freyther, Geoff Reedy, Norbert Hartl, Paul DeBruicker, Alain Plantec, MartÃn Dias, Peter Uhnak, Tomohiro Oda, Benoît Verhaeghe, Santiago Bragagnolo, Wouter van Zuilen, Bernhard Pieber, Damien Pollet, Geoff Hill, Hans-Martin Mosner, Ronie Salgado, Philippe Back, Aliaksei Syrel, Dayne Guerra, Rafael Luque, Serge Stinckwich, Vincent Aranega, Hernán Morales Durand, Petr Fischer, Rajula Vineet Reddy, Alexandre Bergel, Esteban A. Maringolo, Jan BlizniÄenko, Johan Brichau, Luc Fabresse, Quentin Ducasse, Sébastien Roccaserra, Stephan Eggermont, Sven Van Caekenberghe, Takano Mitsuhiro, Pavel Krivanek, Allex Oliveira, Christophe Demarey, Lionel Akue, Nicolai Hess, Martin McClure, Alistair Grant, Pierre Tsapliayev, Milton Mamani, Matteo Marra, Thomas Dupriez, Asbathou Biyalou-Sama. (If you contributed with Pharo 7.0 development in any way and we missed your name, please send us a mail and we will add you).
Enjoy! The Pharo Team
Try Pharo: http://pharo.org/download Learn Pharo: http://pharo.org/documentation
On 24 Jan 2019, at 12:26, phil@highoctane.be wrote:
On Thu, Jan 24, 2019 at 11:17 AM Esteban Lorenzano <estebanlm@gmail.com> wrote:
On 24 Jan 2019, at 09:23, Hernán Morales Durand <hernan.morales@gmail.com> wrote:
Just want to congratulate for the big achievements in this new release. I am trying it right now and it looks very stable! Great work guys!
:) Just for the record, Iâm using same image since 3 monts (and to do some very heavy work). And image has not grown more than normal, and everything still works smooth.
So yes, bugs and limitations aside (there will always be one and the other), this may be the most stable version we have made since P3 :P
Wonderful. Really.
Stability is key indeed.
Now, how do you deal with freezing images? Because let's be honest, this happens and is super frustrating.
As the lead engineer on Pharo, you have for sure interesting tricks on that front.
I have been also frustrated by Epica and code recovery because things happened that were "weird" (for the lack of a better factual word). Tricks on that as well?
Problems do happen for sure. But when Esteban or most Pharo developers are talking about 'Pharo' we usually mean the latest version (P7 right now). Epicea most probably improved quite a bit since it first appeared several versions ago, same for Iceberg, same for Calypso.
Phil
Esteban
Cheers,
Hernán
El mar., 22 ene. 2019 a las 10:37, Esteban Lorenzano (<estebanlm@gmail.com>) escribió: Pharo 7.0 released! ===============
Dear World and dynamic language lovers:
The time has come for Pharo 7.0!
Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback.
<pastedGraphic.png>
This is our most significant release yet. Here are the key highlights of this release:
⢠Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability. The 64-bit version is now recommended for Linux and Mac, and is provided as technical preview for Windows. ⢠Pharo comes with a new version of the PharoLauncher (https://pharo.org/download): THE tool to manage your distributions (access to regular versions, jenkins builds, and older versions). ⢠Pharo build has a fully new build process that supports its full bootstrap from sources. This will enable the production to specific (micro) images. ⢠Iceberg, the git client for Pharo has been significantly improved, and is the default CMS. ⢠Calypso, the angular stone of PharoThings, is the new system Pharo browser. It replaces Nautilus and brings better remote working and more advanced browsing capabilities. ⢠IoT is now an important part of Pharo. Installing PharoThings (https://github.com/pharo-iot/PharoThings) provides an impressive amount of tools to develop applications in small devices. ⢠The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved to work properly on Windows 64-bit.
Pharo 70âs new infrastructure and process set the stage for a new generation of version. The visibility of GitHub combined with the powerful tools that have been validated with more than one year of beta testing is massively pay off.
These are just the more prominent highlights, but the details are just as important.
We have closed a massive amount of issues: 2142 issues! (A comprehensive changelog can be found at: https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo70ChangeL...).
While the technical improvements are significant, still the most impressive fact is that the new code that got in the main Pharo 7.0 image was contributed by more than 75 people.
Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release:
Gabriel Omar Cotelli, Gustavo Santos, Marcus Denker, Torsten Bergmann, Esteban Lorenzano, Bernardo Ezequiel Contreras, Guille Polito, Pablo Tesone, Yoan Geran, Stéphane Ducasse, Cyril Ferlicot, Vincent Blondeau, Denis Kudriashov, Julien Delplanque, Tim Mackinnon, Max Leske, Andrew P. Black, Tomohiro Oda, Clément Béra, Ben Coman, Eric Gade, Yuriy Tymchuk, Nicolas Cellier, Biyalou-Sama Asbath, Myroslava, Sean DeNigris, Juraj Kubelka, Noury Bouraqadi, Holger Freyther, Geoff Reedy, Norbert Hartl, Paul DeBruicker, Alain Plantec, MartÃn Dias, Peter Uhnak, Tomohiro Oda, Benoît Verhaeghe, Santiago Bragagnolo, Wouter van Zuilen, Bernhard Pieber, Damien Pollet, Geoff Hill, Hans-Martin Mosner, Ronie Salgado, Philippe Back, Aliaksei Syrel, Dayne Guerra, Rafael Luque, Serge Stinckwich, Vincent Aranega, Hernán Morales Durand, Petr Fischer, Rajula Vineet Reddy, Alexandre Bergel, Esteban A. Maringolo, Jan BlizniÄenko, Johan Brichau, Luc Fabresse, Quentin Ducasse, Sébastien Roccaserra, Stephan Eggermont, Sven Van Caekenberghe, Takano Mitsuhiro, Pavel Krivanek, Allex Oliveira, Christophe Demarey, Lionel Akue, Nicolai Hess, Martin McClure, Alistair Grant, Pierre Tsapliayev, Milton Mamani, Matteo Marra, Thomas Dupriez, Asbathou Biyalou-Sama. (If you contributed with Pharo 7.0 development in any way and we missed your name, please send us a mail and we will add you).
Enjoy! The Pharo Team
Try Pharo: http://pharo.org/download Learn Pharo: http://pharo.org/documentation
Hi, it's a nice release yes - and the best we ever provided indeed. I'm really happy too that P7 image is an official release now. But still: ========== In a post [1] in November 2017 I brought up the topic again to "increase the quality level in Pharo 7 and onwards". With 762 commits [2] for Pharo 7 I devoted a lot of time in fixing often simple and trivial things just to clean up comments, code, typos, packages, manifests, tests and so on. Many others did the same and supported these cleaning efforts. This helped adding a few more release tests to keep the quality bar on the level reached. Special thanks to Marcus, Esteban, and many others who helped reviewing, fighting a shaky CI server, integrating quickly and so on ... Still THIS IS NOT FINISHED ... and it would be really help if more people would participate in the cleaning or fixing bugs. Also many external packages now need some love to work with Pharo 7. We have a large community with many, many users - but still only a few contribute to the core system. I wonder why and would like to know: - Is it due to the switch to git ? - Is is due to the new contribution process? - Is it for other reasons? Remember: Pharo is yours and even small steps could make a difference. So please join! Thanks T. [1] http://forum.world.st/Pharo-Quality-raising-the-quality-level-in-Pharo-7-and... [2] https://github.com/pharo-project/pharo/graphs/contributors
Which is now the canonical place to seek out these issues/bugs: manuscript or GitHub? On Thu, Jan 24, 2019, 14:37 Torsten Bergmann <astares@gmx.de wrote:
Hi,
it's a nice release yes - and the best we ever provided indeed. I'm really happy too that P7 image is an official release now.
But still: ==========
In a post [1] in November 2017 I brought up the topic again to "increase the quality level in Pharo 7 and onwards".
With 762 commits [2] for Pharo 7 I devoted a lot of time in fixing often simple and trivial things just to clean up comments, code, typos, packages, manifests, tests and so on.
Many others did the same and supported these cleaning efforts. This helped adding a few more release tests to keep the quality bar on the level reached. Special thanks to Marcus, Esteban, and many others who helped reviewing, fighting a shaky CI server, integrating quickly and so on ...
Still THIS IS NOT FINISHED ... and it would be really help if more people would participate in the cleaning or fixing bugs. Also many external packages now need some love to work with Pharo 7.
We have a large community with many, many users - but still only a few contribute to the core system.
I wonder why and would like to know: - Is it due to the switch to git ? - Is is due to the new contribution process? - Is it for other reasons?
Remember: Pharo is yours and even small steps could make a difference. So please join!
Thanks T.
[1] http://forum.world.st/Pharo-Quality-raising-the-quality-level-in-Pharo-7-and... [2] https://github.com/pharo-project/pharo/graphs/contributors
Now github. Stef
On 24 Jan 2019, at 20:44, Eric Gade <eric.gade@gmail.com> wrote:
Which is now the canonical place to seek out these issues/bugs: manuscript or GitHub?
On Thu, Jan 24, 2019, 14:37 Torsten Bergmann <astares@gmx.de <mailto:astares@gmx.de> wrote: Hi,
it's a nice release yes - and the best we ever provided indeed. I'm really happy too that P7 image is an official release now.
But still: ==========
In a post [1] in November 2017 I brought up the topic again to "increase the quality level in Pharo 7 and onwards".
With 762 commits [2] for Pharo 7 I devoted a lot of time in fixing often simple and trivial things just to clean up comments, code, typos, packages, manifests, tests and so on.
Many others did the same and supported these cleaning efforts. This helped adding a few more release tests to keep the quality bar on the level reached. Special thanks to Marcus, Esteban, and many others who helped reviewing, fighting a shaky CI server, integrating quickly and so on ...
Still THIS IS NOT FINISHED ... and it would be really help if more people would participate in the cleaning or fixing bugs. Also many external packages now need some love to work with Pharo 7.
We have a large community with many, many users - but still only a few contribute to the core system.
I wonder why and would like to know: - Is it due to the switch to git ? - Is is due to the new contribution process? - Is it for other reasons?
Remember: Pharo is yours and even small steps could make a difference. So please join!
Thanks T.
[1] http://forum.world.st/Pharo-Quality-raising-the-quality-level-in-Pharo-7-and... <http://forum.world.st/Pharo-Quality-raising-the-quality-level-in-Pharo-7-and...> [2] https://github.com/pharo-project/pharo/graphs/contributors <https://github.com/pharo-project/pharo/graphs/contributors>
Congrats on the release, a major leap forward! Torsten Bergmann wrote
We have a large community with many, many users - but still only a few contribute to the core system.
I wonder why and would like to know: - Is it due to the switch to git ? - Is is due to the new contribution process? - Is it for other reasons?
For me; a combination of 1 and 2. I've done work in Pharo 6.1 during the Pharo7 process, but had no idea how to easily forward-port any base fixes to Pharo 7. The times I tried (after a good old-fashioned file-out), I failed to get Iceberg check out Pharo7 on Windows. IIRC, I believe I resorted to posting an .st in the issues (which then timed out after a year of being stuck in for review status with no automatical validation) As such, I'm absent from the contributor list for the first time since... Pharo 1.1? ;) I hope switching to Pharo8 branch and commiting fixes while working in Pharo7 will be easier? Cheers, Henry -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
Hello
Torsten Bergmann wrote
We have a large community with many, many users - but still only a few contribute to the core system.
I wonder why and would like to know: - Is it due to the switch to git ? - Is is due to the new contribution process? - Is it for other reasons?
For me; a combination of 1 and 2. I've done work in Pharo 6.1 during the Pharo7 process, but had no idea how to easily forward-port any base fixes to Pharo 7. The times I tried (after a good old-fashioned file-out), I failed to get Iceberg check out Pharo7 on Windows. IIRC, I believe I resorted to posting an .st in the issues (which then timed out after a year of being stuck in for review status with no automatical validation) As such, I'm absent from the contributor list for the first time since... Pharo 1.1? ;)
I hope switching to Pharo8 branch and commiting fixes while working in Pharo7 will be easier?
I can tell you. It is a **lot** easier can you tell us if the following is understandable for you https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo <https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo>
Cheers, Henry
-- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
Hi everybody
On 24 Jan 2019, at 20:36, Torsten Bergmann <astares@gmx.de> wrote:
Hi,
it's a nice release yes - and the best we ever provided indeed. I'm really happy too that P7 image is an official release now.
But still: ==========
In a post [1] in November 2017 I brought up the topic again to "increase the quality level in Pharo 7 and onwards".
With 762 commits [2] for Pharo 7 I devoted a lot of time in fixing often simple and trivial things just to clean up comments, code, typos, packages, manifests, tests and so on.
Thanks for it.
Many others did the same and supported these cleaning efforts. This helped adding a few more release tests to keep the quality bar on the level reached. Special thanks to Marcus, Esteban, and many others who helped reviewing, fighting a shaky CI server, integrating quickly and so on â¦
Yes. I think that with Iceberg and git we can now be a lot faster to integrate simple fixes.
Still THIS IS NOT FINISHED ... and it would be really help if more people would participate in the cleaning or fixing bugs. Also many external packages now need some love to work with Pharo 7.
Definitively. What is important is that when we have to deal with little issues this is difficult to work on larger ones. Iâm resurrecting the code of the classParser and UndefinedClasses right now (checking/adding tests).
We have a large community with many, many users - but still only a few contribute to the core system.
I wonder why and would like to know: - Is it due to the switch to git ? - Is is due to the new contribution process? - Is it for other reasons?
Remember: Pharo is yours and even small steps could make a difference. So please join!
Thanks this is a good message. We will produce a video during the next techTalk showing how easy it is to contribute.
Thanks T.
[1] http://forum.world.st/Pharo-Quality-raising-the-quality-level-in-Pharo-7-and... [2] https://github.com/pharo-project/pharo/graphs/contributors
participants (17)
-
Denis Kudriashov -
ducasse -
Eric Gade -
Esteban Lorenzano -
Esteban Maringolo -
Gabriel Cotelli -
Henrik Sperre Johansen -
Hernán Morales Durand -
Hilaire -
K K Subbu -
Norbert Hartl -
phil＠highoctane.be -
Sean P. DeNigris -
Sven Van Caekenberghe -
Todd Blanchard -
Torsten Bergmann -
Tudor Girba