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

[pharo-project/pharo-core] 97519b: 30517

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 97519bf22e86a3b42c647e4b4fe44a30921d2ec0 https://github.com/pharo-project/pharo-core/commit/97519bf22e86a3b42c647e4b… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-10-23 (Wed, 23 Oct 2013) Changed paths: M OpalCompiler-Core.package/OCASTTranslatorForEffect.class/instance/visitor-double dispatching/visitArrayNode_.st M OpalCompiler-Core.package/OCASTTranslatorForEffect.class/instance/visitor-double dispatching/visitBlockNode_.st M OpalCompiler-Core.package/OCAbstractLocalVariable.class/instance/read%2Fwrite usage/isUninitialized.st M OpalCompiler-Core.package/OCAbstractVariable.class/instance/read%2Fwrite usage/isRead.st M OpalCompiler-Core.package/OCAbstractVariable.class/instance/read%2Fwrite usage/isUnused.st M OpalCompiler-Core.package/OCAbstractVariable.class/instance/read%2Fwrite usage/markRead.st M OpalCompiler-Core.package/OCAbstractVariable.class/instance/read%2Fwrite usage/markWrite.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script172.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30517.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 30517 11975 Sync with Opal Repository https://pharo.fogbugz.com/f/cases/11975 http://files.pharo.org/image/30/30517.zip

Oct. 23, 2013

Re: [Pharo-dev] Release mails and update summary

by Torsten Bergmann

> because it's duplicate information. Makes sense > I don't understand, we send github mails since a while and they include all the information > you need, diffs + commit log. Yes - really a step forward! > smalltalkhub has never update it's search functionality, so yes you are lost. > Again, a result of limited resources, but you find it under the Pharo project: > > http://smalltalkhub.com/#!/~Pharo/ci Thanks - I will look into it. Thanks T.

Oct. 23, 2013

Re: [Pharo-dev] Release mails and update summary

by Camillo Bruni

On 2013-10-23, at 12:17, "Torsten Bergmann" <astares(a)gmx.de> wrote: > Marcus wrote: >> do it. The problem is that not everything that would be nice can be done just because the day >> has just 24 hours. > > No need to say this. We know that each others plate if full - but we all try to move Pharo forward. > We all did in the past and hopefully will be able to continue to do so. > > But currently I'm completely LOST to even know in which direction the release management moves, > its current state and what is planned for it. > > Just for demonstration: > > I only stumbled by accident on your mail regarding the release mails and that they > will not be sent anymore. > > http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2013-October/085… > > Is it because you have no time to write them, is it because there is a "grand plan" > to switch to a different process to make the updates reproducible? I dont know. because it's duplicate information. > Anything I know now from the mail is that I should now have to watch out for Github > mails and need to find out more out the current github activities - before getting even > a glue on whats going on or how to help. I don't understand, we send github mails since a while and they include all the information you need, diffs + commit log. > another example: > > Camillo talkes about "a complete fogbugz api written in pharo" - I can not find it when > searching "fogbugz" on SmalltalkHub => I'm LOST again smalltalkhub has never update it's search functionality, so yes you are lost. Again, a result of limited resources, but you find it under the Pharo project: http://smalltalkhub.com/#!/~Pharo/ci

Oct. 23, 2013

Release mails and update summary

by Torsten Bergmann

Marcus wrote: >do it. The problem is that not everything that would be nice can be done just because the day >has just 24 hours. No need to say this. We know that each others plate if full - but we all try to move Pharo forward. We all did in the past and hopefully will be able to continue to do so. But currently I'm completely LOST to even know in which direction the release management moves, its current state and what is planned for it. Just for demonstration: I only stumbled by accident on your mail regarding the release mails and that they will not be sent anymore. http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2013-October/085… Is it because you have no time to write them, is it because there is a "grand plan" to switch to a different process to make the updates reproducible? I dont know. Anything I know now from the mail is that I should now have to watch out for Github mails and need to find out more out the current github activities - before getting even a glue on whats going on or how to help. another example: Camillo talkes about "a complete fogbugz api written in pharo" - I can not find it when searching "fogbugz" on SmalltalkHub => I'm LOST again It's really hard to follow all the activities ...

Oct. 23, 2013

Re: [Pharo-dev] Pharo-project.org success stories link to be revised a bit...

by phil＠highoctane.be

Sure, please do. --- Philippe Back Dramatic Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:phil@highoctane.be | Web: http://philippeback.eu Blog: http://philippeback.be | Twitter: @philippeback Youtube: http://www.youtube.com/user/philippeback/videos High Octane SPRL rue cour Boisacq 101 | 1301 Bierges | Belgium Pharo Consortium Member - http://consortium.pharo.org/ Featured on the Software Process and Measurement Cast - http://spamcast.libsyn.com Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller On Wed, Oct 23, 2013 at 8:46 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Oct 22, 2013, at 6:41 PM, phil(a)highoctane.be wrote: > > As Doru mentioned, marketing of Pharo should be improved to get more > traction. > > Now, on http://www.pharo-project.org/about/success-stories > > a serious bunch of links are not working, point to projects that are > abandoning Smalltalk for Javascript (Language of Languages) - link goes to > a page saying so -- bad karma. > > Even Esteban's Lawsuit Tracker is not the right URL (right one is * > http://smallworks.com.ar/web/projects/lawsuitTracker)*. > > Looks like other projects are not there anymore, click on the links for > issys or Ilon SA and end up waiting with nothing showing up. > > 2denker's http://taskfor.us/ is dead: 404 > > > So, some fixing needed. > > > -> the bug tracker can be good for thsese things, too. > > -> I can add you as someone who can change the website if you want. > > Marcus > >

Oct. 23, 2013

Re: [Pharo-dev] Release mails and update summary

by Marcus Denker

On 23 Oct 2013, at 10:54, Torsten Bergmann <astares(a)gmx.de> wrote: > "Pharo launcher" [1] has the ability to download and run images. It really > helps avoiding chaos on the hard disk and I can only recommend to others > to give it a try. > > One nice side effect is that one can download actual images depending > on image number (update version). As we have seen this is also very > helpful when hunting bugs that are introduced by new updates, see [2] > > Together with the release mails and its references to issues in the issue > tracker one can easily reproduce each build. But one always has to look into the > mail archive to get infos about the updates. > > Dont know how the release mails are written by integrators (manual or > automagically with a tool) but it looks like we switch to GitHub commit mails > these days [3]. > > IMHO it would also be helpful if we would have a single "Summary page" > on Pharo.org or directly under "updates.pharo.org" with a complete list > of all the updates: > > Pharo 3.0 > - 30516 > - 30515 > - ... > Pharo 2.0 > - 20624 > - 20623 > - ... > > and when clicking the update/version numbers one can get detailed infos about the update > and the corresponding links to issue tracker. > Maybe the info is there in a format that can accessed also from within Pharo for future > release management tools. > > One possible way would be by having each FogBugz issue assigned an update number when > a fix get integrated and maybe such a summary page can be generated directly from the > issue tracker. Is this already existing or planned? > > Any comments? > do it. The problem is that not everything that would be nice can be done just because the day has just 24 hours. Marcus

Oct. 23, 2013

Re: [Pharo-dev] Release mails and update summary

by Camillo Bruni

On 2013-10-23, at 10:54, "Torsten Bergmann" <astares(a)gmx.de> wrote: > IMHO it would also be helpful if we would have a single "Summary page" > on Pharo.org or directly under "updates.pharo.org" with a complete list > of all the updates: > > Pharo 3.0 > - 30516 > - 30515 > - ... > Pharo 2.0 > - 20624 > - 20623 > - ... > and when clicking the update/version numbers one can get detailed infos about the update > and the corresponding links to issue tracker. > Maybe the info is there in a format that can accessed also from within Pharo for future > release management tools. I don't think the updates is the right place, the right place is to attach proper links of the issues to the commit logs, because this is the only place you have a complete overview of what changed. We already have the link to the proper github branch for the updates files, but not for the updates themselves. > One possible way would be by having each FogBugz issue assigned an update number when > a fix get integrated and maybe such a summary page can be generated directly from the > issue tracker. Is this already existing or planned? Yes this is good plan, but we need to automatize the integration process further before. After the incident on last friday we see that there are still many parts of the integration (namely the issue closing) that get forgotten easily. But we have almost all the pieces, - a complete fogbugz api written in pharo - a complete issue checker written in pharo - automatic commit logs on github What is missing is, to - generate commit messages only from the issue numbers - automatically push a tag / close the issues when the integration process is complete Another problem, albeit solvable, is that the update.cs files are generated before actually exporting everything (or running the tests for that matter). That means we would have to modify the updates files afterwards on the server somehow and recommit them to the git repository containing the update files.

Oct. 23, 2013

Release mails and update summary

by Torsten Bergmann

"Pharo launcher" [1] has the ability to download and run images. It really helps avoiding chaos on the hard disk and I can only recommend to others to give it a try. One nice side effect is that one can download actual images depending on image number (update version). As we have seen this is also very helpful when hunting bugs that are introduced by new updates, see [2] Together with the release mails and its references to issues in the issue tracker one can easily reproduce each build. But one always has to look into the mail archive to get infos about the updates. Dont know how the release mails are written by integrators (manual or automagically with a tool) but it looks like we switch to GitHub commit mails these days [3]. IMHO it would also be helpful if we would have a single "Summary page" on Pharo.org or directly under "updates.pharo.org" with a complete list of all the updates: Pharo 3.0 - 30516 - 30515 - ... Pharo 2.0 - 20624 - 20623 - ... and when clicking the update/version numbers one can get detailed infos about the update and the corresponding links to issue tracker. Maybe the info is there in a format that can accessed also from within Pharo for future release management tools. One possible way would be by having each FogBugz issue assigned an update number when a fix get integrated and maybe such a summary page can be generated directly from the issue tracker. Is this already existing or planned? Any comments? Thx T. [1] http://www.smalltalkhub.com/#!/~Pharo/PharoLauncher [2] http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2013-October/085… [3] http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/2013-October/085…

Oct. 23, 2013

Re: [Pharo-dev] ZnEasy and https?

by Sven Van Caekenberghe

Hi StÃ©phane, It is actually even simpler, you can use either: ZnEasy get: 'https://github.com/pharo-project/pharo-project-proposals/blob/master/Topics…'. or: ZnClient new get: 'https://github.com/pharo-project/pharo-project-proposals/blob/master/Topics…'. They return slightly different things, in the first case the response object, in the second case the actual contents. Look for users of ZnClient in the system and tests for tons of examples. HTH, Sven On 23 Oct 2013, at 10:46, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > hi sven > > I would like to fetch a file stored on github > > ZnEasy client > url: 'https://github.com/pharo-project/pharo-project-proposals/blob/master/Topics…'; > get; > response > > Else I tried to read zodiac code but I missed some examples. > I tried to read the tests but I failed. > > Stef > > >

Oct. 23, 2013

Re: [Pharo-dev] missing updates: 30503 30504

by Camillo Bruni

On 2013-10-22, at 10:44, Camillo Bruni <camillobruni(a)gmail.com> wrote: >>> For retracting files you need access to files.pharo.org. >> >> This is what should be written in the readme. > > BTW have you tried that you actually have access to the machine? > Because I remember that it didn't work for you nor Esteban... So stef, did you check that you can actually edit the file? Otherwise you will run into exactly the same trouble the next time...

Oct. 23, 2013