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

Re: [Pharo-dev] Github and Fogbugz integration

by Dimitris Chloupis

Useless piece of info , I think I am the first person to actually create a github issue for Pharo. It was not for pharo code it was for pharo documentation https://github.com/SquareBracketAssociates/UpdatedPharoByExample/issues/1 Since then not only UPBE but also other pharo doc github repos have been using github issues , so we already doing that and none has blamed me so far :D On Sat, Aug 19, 2017 at 10:00 PM Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Hi sean > > I prefer to continue to use fogbugz. Changing is really costly. > > Stef > > On Sat, Aug 19, 2017 at 6:48 PM, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > > Guillermo Polito wrote > >> Sadly, this just works for the integration of commits into the main > >> branches, not pull requests. For pull request integration we will > probably > >> need a home made solution. > > > > Now that we are moving development to GH, has there been any discussion > of > > moving issue tracking there as well? > > > > > > > > ----- > > Cheers, > > Sean > > -- > > View this message in context: > http://forum.world.st/Github-and-Fogbugz-integration-tp4960676p4962533.html > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > >

Aug. 19, 2017

Re: [Pharo-dev] Latest Debian, Ubuntu and CentOS packages of the pharo-vm

by Stephane Ducasse

Tx Holger!!!! Really tx. On Fri, Aug 18, 2017 at 11:54 AM, Holger Freyther <holger(a)freyther.de> wrote: > Hi, > > when running Pharo in production you might want to install the image and a VM from distribution packages. So far there were no current public packages and during the last months I have modernized the debian packaging and recently added CentOS rpm packaging as well. The process of generating new source packages is integrated into the pharo-vm travis-ci build as well. > > Every time that master of pharo-vm.git is updated a new source package will be uploaded to the Open(SUSE) Build Service and new packages will be built and are available in a "latest" package feed. The generated (and used) sourcecode is inside the source package and will be archived by the OBS platform (one can even nicely diff versions). The "stable" VM is not built from pharo-vm.git (yet?) so it doesn't show on OBS yet. > > Below are some semi-tested installation notes in case you want to try it out. The binary names are picked to allow to install the 32bit and 64bit VM in parallel. The names currently are: > > - pharo6-32 (32bit version) > - pharo6-64 (64bit version) > - pharo6-32-ui (32bit version with X11 dependencies) > - pharo6-64-ui (64bit version with X11 dependencies) > > > CentOS 6.8: > > # Add the repo > $ yum-config-manager --add-repo http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/C… > > # Install 32bit packages (with X11 dependency for *-ui or not) > > $ yum install pharo6-32-ui.i686 or pharo6-32.i386 > > # Install 64bit packages > > $ yum install pharo6-64-ui.x86_64 pharo6-64.x86_64 > > > > CentOS 7 (only 64bit): > > > $ yum-config-manager --add-repo http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/C… > $ yum install pharo6-64-ui.x86_64 pharo6-64.x86_64 > > > Debian 8: > > # Add signing key > $ wget -O - http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/D… | apt-key add - > > # Update and install > $ apt update > $ apt install pharo6-32-ui pharo6-64-ui (or pharo6-32 or pharo6-64) > > Ubuntu 14.04 LTS > > # Add signing key > $ wget -O - http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/x… | apt-key add - > > # Update and install > $ apt update > $ apt install pharo6-32-ui pharo6-64-ui > > Ubuntu 16.04 > > # Add signing key > $ wget -O - http://download.opensuse.org/repositories/devel:/languages:/pharo:/latest/x… | apt-key add - > > # Update and install > $ apt update > $ apt install pharo6-32-ui pharo6-64-ui > > >

Aug. 19, 2017

Re: [Pharo-dev] Github and Fogbugz integration

by Stephane Ducasse

Hi sean I prefer to continue to use fogbugz. Changing is really costly. Stef On Sat, Aug 19, 2017 at 6:48 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Guillermo Polito wrote >> Sadly, this just works for the integration of commits into the main >> branches, not pull requests. For pull request integration we will probably >> need a home made solution. > > Now that we are moving development to GH, has there been any discussion of > moving issue tracking there as well? > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Github-and-Fogbugz-integration-tp4960676p4962533.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Aug. 19, 2017

Re: [Pharo-dev] Github and Fogbugz integration

by Dimitris Chloupis

Well technically you cannot stop people from using the github issue tracker for reporting bugs and by default if you are a contributor to a repo you will be alerted via email of new issues or replies to existing github issues. Both github and forgbuz issue tracker can happily coexist. There will be also little need create same issues on both githyb and fogbuz because there will be little benefit , both are quite efficient on what they do , I see little reason not to allow both ways of reporting bugs. Github has a bit the edge here because of how it handles pull requests which it separates from issues and it allows you to start discussions on top of the code to be merged etc. Again this is a technical detail, the important thing is to report bugs and to fix them , how you do it is a lesser concern. Github has also other advantages that I am not so familiar , especially with CI. Right now CI for Pharo is separate , this is also can be brought to gitgub in some way without actually moving the CI and have Github as a main hub for commits, issue reporting, CI discussions and free wiki and a static website (maybe as a more permanent version of the wiki). https://github.com/marketplace/category/continuous-integration Github is actually extremely flexible. Gitlab is even more so , cause its full open source and allow you to host it on your own servers and you do not need to relearn what you learned with Github as it follows a very similar interface. Gitlab allows to move repos from github and will copy not just the code but also issues etc. So that is also a good solution for some people who may way to have Pharo dev on their own server and more control of it. A rather new feature for Github is also projects, a way to visualise todo lists, roadmaps, pull requests etc https://help.github.com/articles/about-project-boards/ It also offers way to visualise other things like commits, issues etc and last but not least it can host downloads of releases so there is a convenient and obvious way to find the latest but also previous versions of pharo with Github releases https://help.github.com/articles/creating-releases/ On Sat, Aug 19, 2017 at 7:51 PM Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Guillermo Polito wrote > > Sadly, this just works for the integration of commits into the main > > branches, not pull requests. For pull request integration we will > probably > > need a home made solution. > > Now that we are moving development to GH, has there been any discussion of > moving issue tracking there as well? > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Github-and-Fogbugz-integration-tp4960676p4962533.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Aug. 19, 2017

Re: [Pharo-dev] Github and Fogbugz integration

by Sean P. DeNigris

Guillermo Polito wrote > Sadly, this just works for the integration of commits into the main > branches, not pull requests. For pull request integration we will probably > need a home made solution. Now that we are moving development to GH, has there been any discussion of moving issue tracking there as well? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Github-and-Fogbugz-integration-tp4960676p4962533.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 19, 2017

Re: [Pharo-dev] Ugly smell: really long symbols/selectors

by Sean P. DeNigris

Denis Kudriashov wrote > Which is actually shows that tests as methods are not really good idea. > Tests are supposed to be documentation but with classic SUnit we have only > two ways (classes and methods) to decompose them which is definitely not > enough for docs. He he +100. I remember us talking about this a long time ago. I have a vision for something like rspec, but with a domain UI and then have the classes/methods/whatever storage as an implementation detail. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Ugly-smell-really-long-symbols-selectors-tp4961544p49… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 19, 2017

Re: [Pharo-dev] Latest Debian, Ubuntu and CentOS packages of the pharo-vm

by Sean P. DeNigris

Holger Freyther wrote > Every time that master of pharo-vm.git is updated a new source package > will be uploaded to the Open(SUSE) Build Service and new packages will be > built and are available in a "latest" package feed. Awesome!! Esteban and I have wanted this for a long time but were unable to devote the time to figure out how to get it working. Out of curiosity, where can I see how it was set up/configured? There is a "Project Config" tab which seems to be empty... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Latest-Debian-Ubuntu-and-CentOS-packages-of-the-pharo… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 19, 2017

[ Pharo 70 ] Build 44 PR 175 Space-analysis-resurrection

by Stephane Ducasse

[ Pharo 70 ] Build 44 PR 175 Space-analysis-resurrection https://pharo.fogbugz.com/f/cases/20230/Space-analysis-resurrection https://github.com/pharo-project/pharo/pull/175

Aug. 19, 2017

Re: [Pharo-dev] Little extensions to easily manage file versions

by Stephane Ducasse

No I will have a look :) But I also need latestVersion because you need the two: to always load the latest and save latest + 1 Stef On Fri, Aug 18, 2017 at 11:38 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Do you know that there is #nextVersion method in FileReference? > > 2017-08-18 22:04 GMT+02:00 Stephane Ducasse <stepharo.self(a)gmail.com>: >> >> Hi >> >> I really like (when I save little data files) to have a simple versioning. >> For example for my game collection I have >> Games.1.ston >> Games.2.ston >> ... >> and I like that this is managed for me by the system. >> >> I harvested this functionality from squeak long time ago. >> I rewrote it fast and dirty in Pharo. I find this two methods super >> handy and they provide cheap versioning for little files. >> >> >> >> lastNameFor: baseFileName extension: extension >> "Assumes a file name includes a version number encoded as '.' >> followed by digits >> preceding the file extension, e.g., games.22.ston >> Answer the file name with the largest number. >> If a version number is not found, raises an error" >> >> "FileSystem workingDirectory lastNameFor: 'games' extension: 'ston'" >> >> | files | >> files := self childrenMatching: baseFileName , '.*.' , extension. >> files ifEmpty: [ ^ self error: 'No file with number pattern' ]. >> ^ (files asSortedCollection: [ :a :b | a basename < b basename ]) last >> >> nextNameFor: baseFileName extension: extension >> "Assumes a file name includes a version number encoded as '.' >> followed by digits >> preceding the file extension, e.g., games.22.ston >> Increment the version number (of the largest one) and answer the >> new file name, e.g., games23.ston >> If a version number is not found, set the version to 1 and answer a >> new file name" >> >> "FileSystem workingDirectory nextNameFor: 'games' extension: 'ston'" >> >> | files splits version | >> files := self childrenMatching: baseFileName , '.*.' , extension. >> files ifEmpty: [ ^ baseFileName , '.1.' , extension ]. >> splits := files >> collect: [ :filename | filename basename splitOn: $. ] >> thenSelect: [ :split | (split at: 1) = baseFileName and: [ >> split size = 3 ] ]. >> splits := splits asSortedCollection: [ :a :b | (a at: 2) < (b at: 2) >> ]. >> version := splits isEmpty >> ifTrue: [ 1 ] >> ifFalse: [ (splits last at: 2) asNumber + 1 ]. >> ^ baseFileName , '.' , version asString , '.' , extension >> >> I think that these to methods can be a valuable addition to >> fileReference (the methods can be better implemented). >> >> Let me know what you think. >> >> https://pharo.fogbugz.com/f/cases/20324/Handy-file-automatic-numbering >> >> Stef >> >

Aug. 19, 2017

Re: [Pharo-dev] [ANN] Pharo 6.1 (summer) released!

by Ben Coman

> Normally you have a CI that builds from the latest pharo image + the latest commit from your repo and you start with that all couple of days/weeks (This is important to make sure that you have a reproduce build, too). This is expected for production code, but maybe not the workflow for everyone (e.g. hobbyists or people exploring datasets.) On Fri, Aug 18, 2017 at 10:36 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 18 Aug 2017, at 15:41, Tim Mackinnon <tim(a)testit.works> wrote: > > If you donât mind - let me try a second attempt at paraphrasing what you > are saying (just to make sure Iâm clear, but it might help others too). > > We start each yearly cycle with an X0 new release (our current release is > 6). Then there may be point releases 6.1, 6.2 etc where there is a breaking > change (typically a new VM. Our last point release was 6.1). > > Thought the year (typically every few days) there are âhot fixesâ that > causes an image number change (these have worked there way through the CI, > and have triggered a new artefect). These images can be found at > http://files.pharo.org/image/60/ (where 60 designates the last release > cycle, we donât use point designations for this directory name). > > When you download the latest point release, you are getting all the major > elements of that release plus any of the hot fixes that have occurred since > that official release. *So you have the most up to date version of a > stable Pharo at the time that you download this file from: * > http://pharo.org/download > > > yes > > The implication of the above, is that if you want to revert to exactly > what was present in the launch of an official point release, you will need > to download the latest release from Pharo.org <http://pharo.org/> and > then find the image number that corresponded to that release at > http://files.pharo.org/image/60/ (is there an easy way to determine this > and then find that file? Or is there an official archive of the first point > release?). > > If you want to say up to date, you should periodically download the latest > point release (or you can simply find that latest named image file from: > http://files.pharo.org/image/60/ and use your current VM). > > If the above is the case - it seems like a reasonable way of operating, > although it might be good to know what the exact image number was in the > first issued point release (just for traceability). > > Have I now got it straight now? > > Yes. > And maybe it is not goodâ¦ maybe it would be better to accumulate the > changes between the point release without changing the download and have > the version numbers > more prominent in the downloaded files (so that it is easy to find old > versions, too). > For major.minor.hotfix versioning, maybe the hotfixes that pass CI could accumulate in a list that is loaded similar to the old System > Software Update method, so hotfixes are available without without having to throw away an image - i.e. a new download is only required for a "major.minor" update. A user might individually select a hotfix, but the default list gives a standard order to load them. Each change to that default list is essentially a ".hotfix" point release. This may provide the mechanism to provide more longevity of Pharo versions. As part of their CI, anyone can download the major.minor release and then the default hotfix list (or their own list). Older Pharo versions would tend to become more community-supported. cheers -ben

Aug. 19, 2017