April 2017 - Pharo-dev - lists.pharo.org

[Pharo6] Wanted: Human Readable ChangeLog

by Marcus Denker

Hi, We have the complete list of changes here: https://pharo.fogbugz.com/f/filters/?fClosedBugs=true&fGlobal=true&fOpenBug… <https://pharo.fogbugz.com/f/filters/?fClosedBugs=true&fGlobal=true&fOpenBug…> all 1386 closed issues with MileStone Pharo6. For the release announcement, it would be nice to have a shorter, more digestible list. I think we need 2 kind: 1) some 5-8 âmost importantâ ones 2) a list of maybe 20 issues that are interesting I think the easiest is to do it together.. so if you have points for the 2 kinds of changes, I would be interested. I will then create one merged version of everything people send me (or to the list). Marcus

April 11, 2017

Re: [Pharo-dev] stepping off the end of the debug stack

by Denis Kudriashov

2017-04-08 6:46 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > As an immediate stop-gap I'm adding the following comment to > BlockClosure>>newProcess > > "IMPORTANT! Debug stepping this deep infrastructure may lock your Image" > "If you are not sure what you are doing, close the debugger now." > And issue for this part 19929 <https://pharo.fogbugz.com/f/cases/19929/Comment-guard-to-warn-debugging-top…>

April 11, 2017

Re: [Pharo-dev] stepping off the end of the debug stack

by Denis Kudriashov

Hi Ben, 2017-04-08 6:32 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > I imagine a newcomer exploring the system could easily step off the end of > the debug stack like this... > > (1 printString) "debugIt" > then StepOver six times where the image hangs at "Processor > terminateActive" > > This could have a strong impact against first impressions. > What would it take to guard against this? > I opened issue 19928 <https://pharo.fogbugz.com/f/cases/19928/Debugger-step-over-through-last-doI…>. (I not found yours, right?)

April 11, 2017

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60464 Home: https://github.com/pharo-project/pharo-core

April 11, 2017

[pharo-project/pharo-core] 7282e7: 60464

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 7282e70f15433ab97e70d14b0e0868e345dd4c15 https://github.com/pharo-project/pharo-core/commit/7282e70f15433ab97e70d14b… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-04-11 (Tue, 11 Apr 2017) Changed paths: A Rubric.package/RubAbstractTextArea.class/class/settings/defaultMaxExtent.st M Rubric.package/RubAbstractTextArea.class/instance/drawing/drawingBounds.st M Rubric.package/RubParagraph.class/instance/composition/compositionExtent.st M Rubric.package/RubParagraph.class/instance/geometry/width.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60463.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60464.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60463.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60464.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60464 19884 Rubric should not use SmallInteger maxVal https://pharo.fogbugz.com/f/cases/19884 http://files.pharo.org/image/60/60464.zip

April 11, 2017

Re: [Pharo-dev] Estebanâs list of blocking issues for release Pharo 6.0 (updated to April 10)

by Esteban Lorenzano

> On 10 Apr 2017, at 11:39, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > > Hi Esteban, > > Is there a chance to have a fully working SDL2? (remember that conflicting issue with main window) > I am just curious :) Sorry, no. Last time that was made by replacing the complete Cocoa backend (from OpenGL to CoreGraphics). While that can be done, it is not realist it will arrive for Pharo 6.0 at all. Esteban > > Cheers, > Alex > > On 10 April 2017 at 09:20, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > Hello, > > This are the pending issues for release Pharo 6.0: > > VM: > === > - NEW: there is a problem with latest VM and primitiveFindSubstring that needs to be fixed. > - make all tests pass (there are still some failing tests when compiling a new VM). > - libgit2: Still not there, Jan and Ben were trying and sent some suggestions but I still didnât had the time to test it. > > Image: > ===== > - iceberg hit the image > > Fixed last week: > --------------------- > > - win32, cairo fonts problem > - leak revision by Pavel > (and of course several issues not mentioned in the list). > > Next: > - Make the release! > - Test the new process and tape some videos explaining how we will contribute with a bootstrapped process using github :) > > By the wayâ¦ this is a list we have to accomplish in order to make a release (so you know our pain): > > - Prepare release notes > Image: > - add welcome browser > - generate PharoV60.sources > - move SystemVersion > - prepare new ScriptLoader70 package (in theory, this will not needed anymore but better to have it as a backup :P) > VM: > - stable for 6.0 release > WebSite: > - Update index > - Update download page > Infrastructure: > - ZeroConf: Open new 7.0 development > - SmalltalkCI: Open new 7.0 development > - Create platform stable versions > - Jenkins: move all CI projects to Pharo 7.0 (again some will not needed anymore, notable those moved to travis, but still) > - And talking about travis: prepare all new process on github/travis/appveyor > Pub: > - announce post > - announce mail > - post to YC, Reddit > > â¦ and Iâm sure Iâm forgetting a lot more I will remember in the process of making the release. > > (which is one of the reasons why we do not have âmore releases in a yearâ) > > Anyway, do not despairâ¦ we are almost there! > > cheers! > Esteban > > > >

April 10, 2017

Re: [Pharo-dev] Estebanâs list of blocking issues for release Pharo 6.0 (updated to April 10)

by Aliaksei Syrel

Hi Esteban, Is there a chance to have a fully working SDL2? (remember that conflicting issue with main window) I am just curious :) Cheers, Alex On 10 April 2017 at 09:20, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hello, > > This are the pending issues for release Pharo 6.0: > > VM: > === > - NEW: there is a problem with latest VM and primitiveFindSubstring that > needs to be fixed. > - make all tests pass (there are still some failing tests when compiling a > new VM). > - libgit2: Still not there, Jan and Ben were trying and sent some > suggestions but I still didnât had the time to test it. > > Image: > ===== > - iceberg hit the image > > Fixed last week: > --------------------- > > - win32, cairo fonts problem > - leak revision by Pavel > (and of course several issues not mentioned in the list). > > Next: > - Make the release! > - Test the new process and tape some videos explaining how we will > contribute with a bootstrapped process using github :) > > By the wayâ¦ this is a list we have to accomplish in order to make a > release (so you know our pain): > > - Prepare release notes > Image: > - add welcome browser > - generate PharoV60.sources > - move SystemVersion > - prepare new ScriptLoader70 package (in theory, this will not needed > anymore but better to have it as a backup :P) > VM: > - stable for 6.0 release > WebSite: > - Update index > - Update download page > Infrastructure: > - ZeroConf: Open new 7.0 development > - SmalltalkCI: Open new 7.0 development > - Create platform stable versions > - Jenkins: move all CI projects to Pharo 7.0 (again some will not needed > anymore, notable those moved to travis, but still) > - And talking about travis: prepare all new process on > github/travis/appveyor > Pub: > - announce post > - announce mail > - post to YC, Reddit > > â¦ and Iâm sure Iâm forgetting a lot more I will remember in the process of > making the release. > > (which is one of the reasons why we do not have âmore releases in a yearâ) > > Anyway, do not despairâ¦ we are almost there! > > cheers! > Esteban > > > >

April 10, 2017

Estebanâs list of blocking issues for release Pharo 6.0 (updated to April 10)

by Esteban Lorenzano

Hello, This are the pending issues for release Pharo 6.0: VM: === - NEW: there is a problem with latest VM and primitiveFindSubstring that needs to be fixed. - make all tests pass (there are still some failing tests when compiling a new VM). - libgit2: Still not there, Jan and Ben were trying and sent some suggestions but I still didnât had the time to test it. Image: ===== - iceberg hit the image Fixed last week: --------------------- - win32, cairo fonts problem - leak revision by Pavel (and of course several issues not mentioned in the list). Next: - Make the release! - Test the new process and tape some videos explaining how we will contribute with a bootstrapped process using github :) By the wayâ¦ this is a list we have to accomplish in order to make a release (so you know our pain): - Prepare release notes Image: - add welcome browser - generate PharoV60.sources - move SystemVersion - prepare new ScriptLoader70 package (in theory, this will not needed anymore but better to have it as a backup :P) VM: - stable for 6.0 release WebSite: - Update index - Update download page Infrastructure: - ZeroConf: Open new 7.0 development - SmalltalkCI: Open new 7.0 development - Create platform stable versions - Jenkins: move all CI projects to Pharo 7.0 (again some will not needed anymore, notable those moved to travis, but still) - And talking about travis: prepare all new process on github/travis/appveyor Pub: - announce post - announce mail - post to YC, Reddit â¦ and Iâm sure Iâm forgetting a lot more I will remember in the process of making the release. (which is one of the reasons why we do not have âmore releases in a yearâ) Anyway, do not despairâ¦ we are almost there! cheers! Esteban

April 10, 2017

Esteban's ChangeLog week of 3 April 2017

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 3 April 2017 to 9 April 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=3/4/2017&to=9/4/2017 ChangeLog ========= 7 April 2017: ------------- * Fixed the small but annoying [issue 323](https://github.com/npasserini/iceberg/issues/323) (DNU when creating a local repository ) * Today I'm working on [Iceberg](http://github.com/npasserini/iceberg). I fixed a bug on locating existing repositories for +gitlocal:+ Metacello protocol, but most amusing, I added a new plugin: "Install Baseline", who allows you to install a project from a baseline listed in "Packages" tab from repositories browser. 6 April 2017: ------------- * I worked a lot preparing the new deployment model for VMs. Basically, now it will be like this: * nightly builds will be still built by our CI (to produce test VMs) * latest VMs will be produced on opensmalltalk-vm, using blessed sources. * stable VMs will be promoted by me :) I'm thinking on change a bit this scheme, but for now it will work like that. I finisged the [OpenSmalltalk](http://github.com/OpenSmalltalk/opensmalltalk-vm) part, now I need to adapt also [Pharo-Project](http://github.com/pharo-project/pharo-vm) (tomorrow). Then, we still need to fix one problem with a primitive... and we will be good to go. * I worked on [case: 19921](https://pharo.fogbugz.com/f/cases/19921), to allow Athens to run fine on 64bits (linux). 5 April 2017: ------------- * I worked on +UnifiedFFI+, making sure different architectures of linux (i386, x86_64) will have methods to find their libraries. In particular, I added: +#unix32ModuleName+ and +#unix64ModuleName+. Both are redirecting to +#unixModuleName+ by default as a way to provide backward compatibility (also, libraries could) be in same place in different architectures, like the case of libraries distributed by ourselves (libgit2, libssl, libssh2, libsdl2). 4 April 2017: ------------- * I made some fixes on [Iceberg](https://github.com/npasserini/iceberg)... in particular, this two issues: * [Issue 317](https://github.com/npasserini/iceberg/issues/317), which adds the posibility of removing a package from FileSystem. * [Issue 319](https://github.com/npasserini/iceberg/issues/319), forcing unix line endings to commit messages (as is required by git). * I fixed a problem when building the VM for Windows: thing is, as it was, it was building cairo library without freetype support, so frameworks like Roassal to fail. Problem was that pkgconfig was failing to find correct version of +freetype+ effectively letting it outside. I needed to change the build script (for Windows) to this: ---- $(THIRDPARTYLIBDIR)/$(CAIROLIBNAME): $(CAIROARCHIVE) tar x -f $(CAIROARCHIVE) -C $(THIRDPARTYDIR) cd $(CAIRODIR) \ && ./configure \ --prefix="$(THIRDPARTYOUTDIR)" \ --host=i686-w64-mingw32 \ PKG_CONFIG="$(PKG_CONFIG)" \ PKG_CONFIG_PATH="$(PKG_CONFIG_PATH)" \ CFLAGS='$(THIRDPARTY_CFLAGS) -I$(THIRDPARTYINCLUDEDIR) -march=pentium4' \ LDFLAGS='$(THIRDPARTY_LDFLAGS) -L$(THIRDPARTYLIBDIR) -march=pentium4' \ FREETYPE_LIBS="-L$(THIRDPARTYLIBDIR) -lfreetype -lz" \ FREETYPE_CFLAGS="-I$(THIRDPARTYINCLUDEDIR) -I$(THIRDPARTYINCLUDEDIR)/freetype2" \ --disable-silent-rules \ --disable-xlib \ --disable-dependency-tracking \ && sed -i '/.* sh .\/make-/i\\ttest -e \$$\@ \&\& rm \$$\@' test/Makefile \ && make \ && make install ---- Now averything seems working. cheers! Esteban

April 10, 2017

Re: [Pharo-dev] discord channel request

by Dimitris Chloupis

I forgot to add that yes Mee6 is hosted on its own server and I also created a Heroku account to host my own bot there. Heroku allows to host python apps (including web apps) for free and supports other languages too.

April 9, 2017