October 2016 - Pharo-dev - lists.pharo.org

Notes about Pharo 6 release and new process for Pharo 7
by Esteban Lorenzano Oct. 25, 2016

Oct. 25, 2016

Time to send this to dev list: (btw, this has to do with what we are going to talk today in TechTalk). Hi, Last week we had a meeting where we tried to define current Pharo 6 efforts and the next Pharo 7 goals (in particular, how to revamp our process into something that fits better our numbers of today). The thing is there was no clear roadmap for Pharo 6 and we wanted to precise it. Also, during last years we put some pieces in place and we are ready to do the next big step (changing the Pharo process) but we need to work hard until we have it working (and we just have a draft of how we would want to work, I will talk about later), and we need to discuss, test, iterate before is working properly. Anyway, this is what we think: We need to put Pharo 6.0 development in âfeature freeze statusâ right now. Only things that needs to enter is: - Clements changes (full blocks, SISTA bytecode set, â¦) - 64bits - Bugfixes This way we can jump to work on the new process, that we think will take some months until we have it ready. NEW PROCESS: 1) Builds will be bootstrap based. This implies a change of mindset: pharo will be considered as a small kernel plus a set of maintained packages. This is important to remark because is a difference in our way of think: until now pharo is âthe imageâ, now it will be different because there is the possibility of build different images starting from the kernel and bootstrapping other packages. But of course, the standard-distributed image will be still a compound of the maintained packages (and tests will be ran against this amalgam to be sure everything continues working) 2) Sources will be moved to git. Concrete structure is TBD, but it will be an unique project (no submodules) for a start. This is because is hard to handle changes in multiple submodulesâ¦ Anyway I would like to have different source directories (to separate kernel from maintained packages :P) 3) Changes will be managed through Pull Requests (yay!) And of course there will be a validation process (travis based)â¦ - Iâm also thinking on push the built images into some place for people to be able to verify their errors in the built image (also we could do this)â¦ I mean, the build images for validationâ¦ of course the âintegratedâ images will be pushed allways. This implies a lot of work to make it work, build the tools we need and make us feel confortable with it, thatâs why we want to start as soon as possible. This way, when 7.0 starts in march, we are with the new process. So that. Opinions, suggestions? Esteban

3 5

[pharo-project/pharo-core]
by GitHub Oct. 25, 2016

Oct. 25, 2016

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

1 0

[pharo-project/pharo-core] 9733d5: 50762
by GitHub Oct. 25, 2016

Oct. 25, 2016

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 9733d5c59a3043f0425826f133fa7b71d24e3c2a https://github.com/pharo-project/pharo-core/commit/9733d5c59a3043f0425826f1… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-10-25 (Tue, 25 Oct 2016) Changed paths: M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/baselines/baseline33_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/baselines/baseline34_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/baselines/baseline40_.st M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/symbolic versions/development_.st M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version415_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version416_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version417_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version418_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version4191_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version419_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version420_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version421_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version422_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version423_.st M Glamour-Core.package/GLMAction.class/definition.st A Glamour-Core.package/GLMAction.class/instance/accessing/enabledCondition.st A Glamour-Core.package/GLMAction.class/instance/accessing/enabledCondition_.st A Glamour-Core.package/GLMAction.class/instance/testing/isEnabledOn_.st A Glamour-Core.package/GLMPresentation.class/instance/scripting actions/selectionAct_entitled_enabledWhen_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50761.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50762.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50761.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50762.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50762 19205 [Backport] Pharo 5: Enable / Disable options in context Menu in FastTable https://pharo.fogbugz.com/f/cases/19205 http://files.pharo.org/image/50/50762.zip

1 0

[pharo-project/pharo-core] 4a07c2: 60268
by GitHub Oct. 25, 2016

Oct. 25, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 4a07c2a919a25a29ecc26483fda83c7bf3ada95d https://github.com/pharo-project/pharo-core/commit/4a07c2a919a25a29ecc26483… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-10-25 (Tue, 25 Oct 2016) Changed paths: M Refactoring-Core.package/RBRefactoring.class/instance/preconditions/checkPreconditions.st M Refactoring-Core.package/RBRenameTemporaryRefactoring.class/instance/preconditions/preconditions.st M Refactoring-Core.package/RBRenameTemporaryRefactoring.class/instance/tranforming/renameNode_.st M Refactoring-Core.package/RBRenameTemporaryRefactoring.class/instance/tranforming/transform.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60267.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60268.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60267.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60268.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60268 19238 RBRenameTemporaryRefactoring do not set oldName if one of the optional precondition is not valid https://pharo.fogbugz.com/f/cases/19238 http://files.pharo.org/image/60/60268.zip

1 0

[pharo-project/pharo-core]
by GitHub Oct. 25, 2016

Oct. 25, 2016

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

1 0

[REMEMBER] TechTalk tomorrow 16UTC
by Esteban Lorenzano Oct. 25, 2016

Oct. 25, 2016

Hello fellow pharoers, The time has come (1 month passes so fast!). And tomorrow we will be handling another TechTalk. This time we propose to talk about the new Bootstrap process. For this, Iâd ask Guille, Pavel and/or Christophe to be present. They are the ones actually working on it, so weâll all learn from what they have to say :) Meeting will be handled with discord, as last time. And as always, this will also be a place to ask anything about pharo development (statuses, proposals, etc., etc., etc.) See you tomorrow ! Esteban

9 14

Spur VM Bug for Chinese Characters?
by Sean P. DeNigris Oct. 24, 2016

Oct. 24, 2016

I serialized an object graph with lots of Chinese characters in Pharo 4.0. I have been able to rematerialize it back into Pharo 4.0. However, when I try to materialize into a Pharo 5.0 image, I get "PrimitiveFailed: primitive #value: in Character class failed" from `Character class>>#value: 1310876005`. The only difference immediately apparent is the VM (both via Launcher; details below). More generally, I'm interested in debugging techniques for Fuel. How would I drill down and isolate the problem? Thanks! 5.0 VM: Virtual Machine --------------- /Applications/Pharo.app/Contents/MacOS/Pharo CoInterpreter VMMaker.oscog-eem.1855 uuid: d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016 StackToRegisterMappingCogit VMMaker.oscog-eem.1855 uuid: d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016 https://github.com/pharo-project/pharo-vm.git Commit: b8ec25a570d7539653e1d793e97609adb509aaed Date: 2016-05-04 11:14:22 +0200 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #589 Mac Cocoa Cog 5.8b12 21-Sep-10 >1B0534FA-246C-47C5-AB29-7A76C81CCDCB< VMMaker versionString https://github.com/pharo-project/pharo-vm.git Commit: b8ec25a570d7539653e1d793e97609adb509aaed Date: 2016-05-04 11:14:22 +0200 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #589 CoInterpreter VMMaker.oscog-eem.1855 uuid: d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016 StackToRegisterMappingCogit VMMaker.oscog-eem.1855 uuid: d8e4a3c2-a3bf-4adc-b224-8012903a1ef4 May 4 2016 VS. 4.0 VM: Virtual Machine --------------- /Applications/Pharo.app/Contents/Resources/vm/40/Pharo.app/Contents/MacOS/Pharo NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Apr 2 2015 NBCogit NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Apr 2 2015 https://github.com/pharo-project/pharo-vm.git Commit: 32d18ba0f2db9bee7f3bdbf16bdb24fe4801cfc5 Date: 2015-03-24 11:08:14 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14904 Mac Cocoa Cog 5.8b12 21-Sep-10 >1B0534FA-246C-47C5-AB29-7A76C81CCDCB< VMMaker versionString https://github.com/pharo-project/pharo-vm.git Commit: 32d18ba0f2db9bee7f3bdbf16bdb24fe4801cfc5 Date: 2015-03-24 11:08:14 +0100 By: Esteban Lorenzano <estebanlm(a)gmail.com> Jenkins build #14904 NBCoInterpreter NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Apr 2 2015 NBCogit NativeBoost-CogPlugin-EstebanLorenzano.21 uuid: 4d9b9bdf-2dfa-4c0b-99eb-5b110dadc697 Apr 2 2015 ----- Cheers, Sean -- View this message in context: http://forum.world.st/Spur-VM-Bug-for-Chinese-Characters-tp4918883.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

8 22

Call for design for a literal programming doc similar to PythonDocTest
by stepharo Oct. 24, 2016

Oct. 24, 2016

Hi all I want something similar in the spirit to PythonDocTest https://docs.python.org/2/library/doctest.html I'm talking about basename "Returns the base of the basename, i.e. /foo/gloops.taz basename is 'gloops.taz' / basename is '/'" Pragmas do not work well i.e., basename "Returns the base of the basename" <expr: '''/foo/gloops.taz'' asFileReference basename' result: 'gloops.taz'> We should invent a syntax to be put inside comments and that we can easily parse because we need to improve the use and discovery of the library. I was thinking about basename "Returns the base of the basename" " '/foo/gloops.taz' asFileReference basename >>> 'gloops.taz' " Do you have any idea? I cannot not do anything and just complain that our methods are not that well documented. We as a community should take this and build an super cool system. I tried and defined >>> on Object to see if it works! Object >>> aResultingObject "If the method comment contains >>> then it is a pharo documentated test. We can check that it is true." " '/foo/gloops.taz' asFileReference basename >>> 'gloops.taz' " ^ self = aResultingObject Stef

14 42

[pharo-project/pharo-core]
by GitHub Oct. 24, 2016

Oct. 24, 2016

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

1 0

[pharo-project/pharo-core] 38da99: 60267
by GitHub Oct. 24, 2016

Oct. 24, 2016

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 38da991dc4126b0d59a0e9252ddc448407e6e04d https://github.com/pharo-project/pharo-core/commit/38da991dc4126b0d59a0e925… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-10-24 (Mon, 24 Oct 2016) Changed paths: M AST-Core.package/RBArgumentNode.class/instance/testing/isBlockVar.st M AST-Core.package/RBProgramNode.class/instance/testing/isBlockVar.st M AST-Core.package/RBTemporaryNode.class/instance/testing/isBlockVar.st A Kernel.package/PackageManifest.class/class/meta-data/description.st A Nautilus.package/AbstractNautilusUI.class/instance/comment pane/packageCommentEmptyOrUnchanged.st A Nautilus.package/AbstractNautilusUI.class/instance/comment pane/updatePackageComment.st M Nautilus.package/AbstractNautilusUI.class/instance/comment pane/whenTextUpdatedInCommentPane_.st M Nautilus.package/AbstractNautilusUI.class/instance/source code area/getComments.st M Nautilus.package/NautilusUI.class/instance/accessing/selectedPackageWithoutChangingSelection_.st M Nautilus.package/NautilusUI.class/instance/private/updateOnClassSelection.st A Nautilus.package/PackageTreePackageSelection.class/instance/accessing/packageComment.st A Nautilus.package/PackageTreePackageSelection.class/instance/accessing/packageComment_.st A RPackage-Core.package/RPackage.class/instance/accessing/packageComment.st A RPackage-Core.package/RPackage.class/instance/accessing/packageComment_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60266.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60267.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60266.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60267.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A System-Model.package/Model.class/instance/stepping-window/addModelItemsToWindowMenu_.st A System-Model.package/Model.class/instance/stepping-window/modelWakeUpIn_.st A System-Model.package/Model.class/instance/stepping-window/stepAt_in_.st A System-Model.package/Model.class/instance/stepping-window/stepIn_.st A System-Model.package/Model.class/instance/stepping-window/stepTimeIn_.st A System-Model.package/Model.class/instance/stepping-window/wantsStepsIn_.st A System-Model.package/Model.class/instance/stepping/step.st A System-Model.package/Model.class/instance/stepping/stepTime.st A System-Model.package/Model.class/instance/stepping/wantsSteps.st R System-Model.package/Model.class/instance/updating/step.st R System-Sources.package/SourceFileArray.class/class/instance creation/new_.st Log Message: ----------- 60267 19234 implement stepping methods in Model https://pharo.fogbugz.com/f/cases/19234 19232 Remove SourceFileArray>>#new: https://pharo.fogbugz.com/f/cases/19232 19228 Wrong method arg styleing for arg usage in blocks https://pharo.fogbugz.com/f/cases/19228 19222 Use class comment pane for package comments too https://pharo.fogbugz.com/f/cases/19222 http://files.pharo.org/image/60/60267.zip

1 0