[ANN] Pharo 7.0 released!
Locked
12
12
Re: [ANN] Pharo 7.0 released!
 
|
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-onwards-tt5027111.html#none [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 <[hidden email] wrote: Hi, |
Re: [ANN] Pharo 7.0 released!
|
|
In reply to this post by Torsten Bergmann
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 |
|
|
In reply to this post by darth-cheney
Now github.
Stef
|
|
|
In reply to this post by Henrik Sperre Johansen
Hello
can you tell us if the following is understandable for you |
|
|
In reply to this post by Torsten Bergmann
Hi everybody
> On 24 Jan 2019, at 20:36, Torsten Bergmann <[hidden email]> 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-onwards-tt5027111.html#none > [2] https://github.com/pharo-project/pharo/graphs/contributors > > |
«
Return to Pharo Smalltalk Developers
|
1 view|%1 views
| Free forum by Nabble | Edit this page |