[ANN] Pharo 6.1 (summer) released!
Locked
12
12
 
|
Hi, We are releasing Pharo 6.1. Usually, between each major version we just apply bugfixes changing the build number and not announcing new versions but this time is different since the fixes applied required a new VM. The principal reason for the new version is to update Iceberg support, bringing it to macOS 64bits version. So, now Pharo 6.1 comes with Iceberg 0.5.5, which includes: - running on macOS 64bits - adds cherry pick - adds major improvements on performance for big repositories - adds pull request review plugin - repositories browser: group branches by remote - adds bitbucket and gitlab to recognised providers on metacello integration - uses libgit v0.25.1 as backend - several bugfixes Other important change: - linux vm by default is now vm threaded heartbeat. We still miss 64bits Windows (sorry for that), but we are getting there. I hope to have it running right after ESUG. To download 6.1 version, you can go to http://pharo.org/download page, or with zeroconf: wget -O- get.pharo.org | bash Enjoy! Esteban
|
Re: [ANN] Pharo 6.1 (summer) released!
|
Thanks guys.
I hope it includes the fixes for the bugs impacting Dr. Geo. Hilaire Le 24/07/2017 à 13:56, Esteban Lorenzano a écrit : > We are releasing Pharo -- Dr. Geo http://drgeo.eu |
Re: [Pharo-users] [ANN] Pharo 6.1 (summer) released!
|
|
In reply to this post by EstebanLM
Thank you! That is so cool.
Norbert
|
Re: [ANN] Pharo 6.1 (summer) released!
|
|
In reply to this post by EstebanLM
For Ubuntu users, the updated snap is also available:
sudo snap install pharo --classic --candidate Cheers, Alistair P.S. Should this message be sent to pharo-users as well? On Mon, Jul 24, 2017 at 01:56:20PM +0200, Esteban Lorenzano wrote: > Hi, > > We are releasing Pharo 6.1. > Usually, between each major version we just apply bugfixes changing the build > number and not announcing new versions but this time is different since the > fixes applied required a new VM. > The principal reason for the new version is to update Iceberg support, bringing > it to macOS 64bits version. > > So, now Pharo 6.1 comes with Iceberg 0.5.5, which includes: > > - running on macOS 64bits > - adds cherry pick > - adds major improvements on performance for big repositories > - adds pull request review plugin > - repositories browser: group branches by remote > - adds bitbucket and gitlab to recognised providers on metacello integration > - uses libgit v0.25.1 as backend > - several bugfixes > > Other important change: > > - linux vm by default is now vm threaded heartbeat. > > We still miss 64bits Windows (sorry for that), but we are getting there. I hope > to have it running right after ESUG. > > To download 6.1 version, you can go to http://pharo.org/download page, or with > zeroconf: > > wget -O- get.pharo.org | bash > > Enjoy! > Esteban |
Re: [ANN] Pharo 6.1 (summer) released!
|
|
In reply to this post by EstebanLM
This is a great step to show we have a stable consistent base for the year ahead - thanks for pulling this off!
One small caveat on the 64bit angle - there are still some known outstanding bugs with 64bits - meaning that Fuel is known not to work (which might be for more specialised things - but it does mean we have to careful about how 64bits its advertised : ) Tim
|
Re: [ANN] Pharo 6.1 (summer) released!
|
|
In reply to this post by alistairgrant
Hi Thierry,
On Mon, Jul 24, 2017 at 10:23:49PM +0200, Thierry Goubier wrote: > Le 24/07/2017 ?? 17:05, Alistair Grant a ??crit : > >For Ubuntu users, the updated snap is also available: > > > >sudo snap install pharo --classic --candidate > > Hi Alistair, > > how one update the pharo snap (from 6.0 to 6.1)? sudo snap refresh pharo --candidate Just FYI: My understanding is that if 6.1 had already been pushed to stable, it would update automatically (according to the schedule you have, either by default or set explicitly). Cheers, Alistair > Thierry > > > > >Cheers, > >Alistair > > > >P.S. Should this message be sent to pharo-users as well? |
Re: [ANN] Pharo 6.1 (summer) released!
|
|
In reply to this post by HilaireFernandes
Meaning these tow ones ? http://forum.world.st/Regression-with-PNGReaderWriter-in-P6-td4951796.html#a4952046 http://forum.world.st/WrapAthen-World-coordinate-td4951750.html#a4951966 Hilaire Le 24/07/2017 à 15:11, Hilaire a
écrit :
I hope it includes the fixes for the bugs impacting Dr. Geo. -- Dr. Geo http://drgeo.eu |
Re: [ANN] Pharo 6.1 (summer) released!
|
|
As the P6.1 change log is not complete enough I have to try out to discover: - fix for PNG regression is included - the Athen Wrap regression is still present :( Le 25/07/2017 à 08:59, Hilaire a
écrit :
-- Dr. Geo http://drgeo.eu |
|
|
is very complete. Is just that it does not has so many changes :) this was a version we told it was going to be made available to update iceberg (as we use iceberg for develop P7, we need to have recurrent updates even in Pharo 6). And since there was important modifications, we needed to change the backend library. And since we changed the backend library, we needed to change the vm. Finally, since we changed the VM, we were unable to apply this update as a “hot-fix” (what we do regularly, but version number does not change, just build number). So, Pharo 6.1 is exactly the same as before, but with: new iceberg, new vm, new backend library. cheers! Esteban ps: the other regressions, when fixed, can be applied as we usual apply backported hot-fixes.
|
Re: [ANN] Pharo 6.1 (summer) released!
|
|
Hi,
It is the other minor bugs fixes details which were missing. What is hot-fixes? Hilaire -- Dr. Geo http://drgeo.eu |
Re: [ANN] Pharo 6.1 (summer) released!
|
|
I imagine that hot-fixes means when we found a serious bug in the
alpha version and see that it is also in the previous version. Now Hilaire if you want a change to be integrated in Pharo and Pharo 60 for example. - we should have a bug entry on fogbugz (you see when I read the emails I do not see the bug entry so I have to look for it and lose time - because crawling the bug database is tedious, so this is a lot more efficient to send also bug entries). - we should have a fix. - it should be tagged for Pharo 60. - it should be validated (pass the tests). Each time we introduce a fix, we may break sometimes so we pay really attention to have limited fixes with limited impact. For the ones you mentioned: - I cannot find the PNGReader bug entry. I read all the mails of the thread. So this is not efficient. - https://pharo.fogbugz.com/f/cases/20166/ is there but there is no fix so we will have People are nice and trying to help now everybody has its own agenda and we set these "rules" to avoid that we all lose time. If you want that people help you then try to adhere to such best practices. Follow the Pharo process. Stef. On Tue, Jul 25, 2017 at 6:01 PM, Hilaire <[hidden email]> wrote: > Hi, > > It is the other minor bugs fixes details which were missing. > > What is hot-fixes? > > Hilaire > > > -- > Dr. Geo > http://drgeo.eu > > > |
Re: [ANN] Pharo 6.1 (summer) released!
|
|
2017-07-26 16:25 GMT+02:00 Stephane Ducasse <[hidden email]>: I imagine that hot-fixes means when we found a serious bug in the The problem with fixes for Athens is, that nobody could tell we what the current state is. http://forum.world.st/current-athens-configuration-td4914441.html#a4914488 the latest changes are from alexej and I guess they are important for sparta and the further development for bloc/sparte for pharo 7/8 We can not just take the latest version and put it in pharo 6, and hope that it will work. We need for this external package a good communication about changes and versions. This did not happen here. And I am not sure if we maybe already put some changes in pharo 6, that are not at the athens repository. I once considered athens as an important package for the new pharo ui, but the way it is handled now looks more like abandoned. that is the reason why I just put the fix for 20166 in the comment of the bug entry instead of providing a slice / or update the version on the repository. It is ok if we tell hilaire to not just put bugreports on the ml but create a bug report on fogbugz instead. So people can fix/provide a slice and run the validation. But this happend in this case. It is just that we do not get it right to handle this case because it depens on athens.
|
Re: [ANN] Pharo 6.1 (summer) released!
|
|
2017-07-26 16:42 GMT+02:00 Nicolai Hess <[hidden email]>:
whatever, put a slice for this case into the inbox SLICE-Issue-20166-wrong-cliprect-on-transformed-athens-canvas-NicolaiHess.1
|
Re: [ANN] Pharo 6.1 (summer) released!
|
|
In reply to this post by Nicolai Hess-3-2
Hi Nicolai
Athens is important for us too. Now none of us in the team has the experience in Cairo. Users of Athens usually do not want to invest understanding it either. I tried to create the conditions that Igor could stay in the communautee but it failed because alone I could not do it. Now Athens is what is in Pharo. I have no idea of the rest. Stef On Wed, Jul 26, 2017 at 4:42 PM, Nicolai Hess <[hidden email]> wrote: > > > 2017-07-26 16:25 GMT+02:00 Stephane Ducasse <[hidden email]>: >> >> I imagine that hot-fixes means when we found a serious bug in the >> alpha version and see that it is also in the previous version. >> >> Now Hilaire if you want a change to be integrated in Pharo and Pharo >> 60 for example. >> >> - we should have a bug entry on fogbugz (you see when I read the >> emails I do not see the bug entry >> so I have to look for it and lose time - because crawling the bug >> database is tedious, so this is a lot more efficient to send also bug >> entries). >> - we should have a fix. >> - it should be tagged for Pharo 60. >> - it should be validated (pass the tests). >> >> Each time we introduce a fix, we may break sometimes so we pay really >> attention to have >> limited fixes with limited impact. >> >> For the ones you mentioned: >> >> - I cannot find the PNGReader bug entry. I read all the mails of the >> thread. >> So this is not efficient. >> >> - https://pharo.fogbugz.com/f/cases/20166/ is there but there is no >> fix so we will have > > > The problem with fixes for Athens is, that nobody could tell we what the > current state is. > > http://forum.world.st/current-athens-configuration-td4914441.html#a4914488 > > the latest changes are from alexej and I guess they are important for sparta > and the further development for bloc/sparte for pharo 7/8 > We can not just take the latest version and put it in pharo 6, and hope that > it will work. > We need for this external package a good communication about changes and > versions. > This did not happen here. And I am not sure if we maybe already put some > changes in pharo 6, that are not at the athens repository. > I once considered athens as an important package for the new pharo ui, but > the way it is handled now looks more like abandoned. > > that is the reason why I just put the fix for 20166 in the comment of the > bug entry instead of providing a slice / or update the version on the > repository. > > > It is ok if we tell hilaire to not just put bugreports on the ml but create > a bug report on fogbugz instead. So people can fix/provide a slice and run > the validation. > But this happend in this case. It is just that we do not get it right to > handle this case because it depens on athens. > > >> >> >> People are nice and trying to help now everybody has its own agenda >> and we set these "rules" >> to avoid that we all lose time. If you want that people help you then >> try to adhere to such best >> practices. >> >> Follow the Pharo process. >> >> Stef. >> >> >> On Tue, Jul 25, 2017 at 6:01 PM, Hilaire <[hidden email]> wrote: >> > Hi, >> > >> > It is the other minor bugs fixes details which were missing. >> > >> > What is hot-fixes? >> > >> > Hilaire >> > >> > >> > -- >> > Dr. Geo >> > http://drgeo.eu >> > >> > >> > >> > |
Re: [ANN] Pharo 6.1 (summer) released!
|
|
In reply to this post by Stephane Ducasse-3
If you read carefully what I wrote, I was wondering what were these
small bugs fixes... and if P6.1 would be helpful for the drgeo problems: a list of bugs with links to the bug tracker will have been enough. Hilaire Le 26/07/2017 à 16:25, Stephane Ducasse a écrit : > People are nice and trying to help now everybody has its own agenda > and we set these "rules" -- Dr. Geo http://drgeo.eu |
Re: [ANN] Pharo 6.1 (summer) released!
|
|
On Thu, Jul 27, 2017 at 10:04 AM, Hilaire <[hidden email]> wrote: If you read carefully what I wrote, I was wondering what were these small bugs fixes... and if P6.1 would be helpful for the drgeo problems: a list of bugs with links to the bug tracker will have been enough. I guess this will easier for Pharo 7. We can group PR with milestones on github in order to built nice list when release new version. I guess something similar could be done on fogbugz. Hilaire Serge Stinckwich
UCN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/ |
Re: [ANN] Pharo 6.1 (summer) released!
|
|
In reply to this post by Stephane Ducasse-3
Hi,
Athens is part of Pharo and the priority is to make it work for Pharo. If there are other users of such a core technology, they should be the ones adapting. @Alex Syrel: could you please take a look at the latest commits from Athens and clarify their state? Cheers, Doru > On Jul 26, 2017, at 9:44 PM, Stephane Ducasse <[hidden email]> wrote: > > Hi Nicolai > > Athens is important for us too. Now none of us in the team has the > experience in Cairo. > Users of Athens usually do not want to invest understanding it either. > > I tried to create the conditions that Igor could stay in the > communautee but it failed > because alone I could not do it. > > Now Athens is what is in Pharo. I have no idea of the rest. > > Stef > > > On Wed, Jul 26, 2017 at 4:42 PM, Nicolai Hess <[hidden email]> wrote: >> >> >> 2017-07-26 16:25 GMT+02:00 Stephane Ducasse <[hidden email]>: >>> >>> I imagine that hot-fixes means when we found a serious bug in the >>> alpha version and see that it is also in the previous version. >>> >>> Now Hilaire if you want a change to be integrated in Pharo and Pharo >>> 60 for example. >>> >>> - we should have a bug entry on fogbugz (you see when I read the >>> emails I do not see the bug entry >>> so I have to look for it and lose time - because crawling the bug >>> database is tedious, so this is a lot more efficient to send also bug >>> entries). >>> - we should have a fix. >>> - it should be tagged for Pharo 60. >>> - it should be validated (pass the tests). >>> >>> Each time we introduce a fix, we may break sometimes so we pay really >>> attention to have >>> limited fixes with limited impact. >>> >>> For the ones you mentioned: >>> >>> - I cannot find the PNGReader bug entry. I read all the mails of the >>> thread. >>> So this is not efficient. >>> >>> - https://pharo.fogbugz.com/f/cases/20166/ is there but there is no >>> fix so we will have >> >> >> The problem with fixes for Athens is, that nobody could tell we what the >> current state is. >> >> http://forum.world.st/current-athens-configuration-td4914441.html#a4914488 >> >> the latest changes are from alexej and I guess they are important for sparta >> and the further development for bloc/sparte for pharo 7/8 >> We can not just take the latest version and put it in pharo 6, and hope that >> it will work. >> We need for this external package a good communication about changes and >> versions. >> This did not happen here. And I am not sure if we maybe already put some >> changes in pharo 6, that are not at the athens repository. >> I once considered athens as an important package for the new pharo ui, but >> the way it is handled now looks more like abandoned. >> >> that is the reason why I just put the fix for 20166 in the comment of the >> bug entry instead of providing a slice / or update the version on the >> repository. >> >> >> It is ok if we tell hilaire to not just put bugreports on the ml but create >> a bug report on fogbugz instead. So people can fix/provide a slice and run >> the validation. >> But this happend in this case. It is just that we do not get it right to >> handle this case because it depens on athens. >> >> >>> >>> >>> People are nice and trying to help now everybody has its own agenda >>> and we set these "rules" >>> to avoid that we all lose time. If you want that people help you then >>> try to adhere to such best >>> practices. >>> >>> Follow the Pharo process. >>> >>> Stef. >>> >>> >>> On Tue, Jul 25, 2017 at 6:01 PM, Hilaire <[hidden email]> wrote: >>>> Hi, >>>> >>>> It is the other minor bugs fixes details which were missing. >>>> >>>> What is hot-fixes? >>>> >>>> Hilaire >>>> >>>> >>>> -- >>>> Dr. Geo >>>> http://drgeo.eu >>>> >>>> >>>> >>> >> > -- www.tudorgirba.com www.feenk.com “Live like you mean it." |
Re: [ANN] Pharo 6.1 (summer) released!
|
|
In reply to this post by Nicolai Hess-3-2
Le 26/07/2017 à 16:42, Nicolai Hess a écrit : > It is ok if we tell hilaire to not just put bugreports on the ml but > create a bug report on fogbugz instead. So people can fix/provide a > slice and run the validation. And this is what I do > But this happend in this case. It is just that we do not get it right > to handle this case because it depens on athens. Indeed -- Dr. Geo http://drgeo.eu |
Re: [ANN] Pharo 6.1 (summer) released!
|
|
In reply to this post by Nicolai Hess-3-2
Thanks Nicolai
Hilaire Le 26/07/2017 à 17:07, Nicolai Hess a écrit : > whatever, put a slice for this case into the inbox > SLICE-Issue-20166-wrong-cliprect-on-transformed-athens-canvas-NicolaiHess.1 -- Dr. Geo http://drgeo.eu |
|
|
In reply to this post by EstebanLM
Cool. How do i figure out, if i have installed 6.1? The Welcome Page shows 6.0? i used ... wget -O- get.pharo.org/stable+vm | bash Ubuntu 16.10 LG, Volkert On 24.07.2017 13:56, Esteban Lorenzano
wrote:
|
«
Return to Pharo Smalltalk Developers
|
1 view|%1 views
| Free forum by Nabble | Edit this page |