- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Pharo6 deployment issues

by Marcus Denker

> On 13 Jun 2017, at 13:44, Holger Freyther <holger(a)freyther.de> wrote: > > Hi! > > today I started to look at of why my benchmark in the CI stalled/didn't complete and I see three separate issues and wonder how to address them properly? I have a truncated log attached > > > Issues: > * In my CI script I disable Deprecation warnings but this has no influence on Deprecation>>#transform. This means that it will try to write the changes?! To scale we start the same image multiple times. > > * Somehow writing the log fails (and the TCP connection fails the same time?!) with a primitive error. > > * Errors "recurse". So while we try to exit the image it seems to fail the same way and tries again.. which fails again.. which fails again..at some point no new context will be allocated. > > > Solutions? > > * Prevent new errors in NonInteractiveUIManager>>#unhandledErrorDefaultAction:? > > * Check in >>#transform if transformation is disabled and then return early? > yes! This should have been like that. > * ??? No idea.. I will strace to see what happens to the Debug log.. but ideally I would like this file writing to be disabled. :) > > > Should I create tickets? > Yes! For the Deprecation one I can prepare the fixes for Pharo6 and 7. The other I have no idea yet, but having it on the tracker would be good. Marcus

June 14, 2017

Re: [Pharo-dev] debug vm windows?

by phil＠highoctane.be

Not at the moment. On Tue, Jun 13, 2017 at 10:08 PM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > Thanks! Any chance you can redo the build to get also a debug vm for > the latest version? > > Cheers, > Andrei > > On Tue, Jun 13, 2017 at 8:02 PM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: > > I have an older build here. > > > > https://ci.appveyor.com/project/philippeback/pharo-vm > > > > https://bintray.com/pharophile/pharo-vm/build/ > view/files?sort=name&order=asc#files/ > > > > There is an normal, assert and debug vm in there. > > > > Phil > > > > On Tue, Jun 13, 2017 at 7:14 PM, Andrei Chis <chisvasileandrei(a)gmail.com > > > > wrote: > >> > >> Hi, > >> > >> Is there a Pharo debug vm for windows already build and available > >> somewhere? > >> > >> Cheers, > >> Andrei > >> > > > >

June 13, 2017

Re: [Pharo-dev] debug vm windows?

by Andrei Chis

Thanks! Any chance you can redo the build to get also a debug vm for the latest version? Cheers, Andrei On Tue, Jun 13, 2017 at 8:02 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > I have an older build here. > > https://ci.appveyor.com/project/philippeback/pharo-vm > > https://bintray.com/pharophile/pharo-vm/build/view/files?sort=name&order=as… > > There is an normal, assert and debug vm in there. > > Phil > > On Tue, Jun 13, 2017 at 7:14 PM, Andrei Chis <chisvasileandrei(a)gmail.com> > wrote: >> >> Hi, >> >> Is there a Pharo debug vm for windows already build and available >> somewhere? >> >> Cheers, >> Andrei >> >

June 13, 2017

Re: [Pharo-dev] debug vm windows?

by phil＠highoctane.be

I have an older build here. https://ci.appveyor.com/project/philippeback/pharo-vm https://bintray.com/pharophile/pharo-vm/build/view/files?sort=name&order=as… There is an normal, assert and debug vm in there. Phil On Tue, Jun 13, 2017 at 7:14 PM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > Hi, > > Is there a Pharo debug vm for windows already build and available > somewhere? > > Cheers, > Andrei > >

June 13, 2017

debug vm windows?

by Andrei Chis

Hi, Is there a Pharo debug vm for windows already build and available somewhere? Cheers, Andrei

June 13, 2017

Re: [Pharo-dev] PharoDays17 Slides and some Videos

by Marcus Denker

We have now 9 more videos in the playlist: https://www.youtube.com/playlist?list=PL4actYd6bfnw7ous5We-XnWq0NZquP3gM > On 7 Jun 2017, at 16:24, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Hi, > > I have uploaded the Slides and Videos of PharoDays2017. Slides are complete (minus those > talks that were due demos). For the Videos we have right now 8 talks and the âShow Us Your > Projectâ session. More might come in the future (I need to check). > > Slides: > - https://www.slideshare.net/pharoproject/presentations > - http://files.pharo.org/conferences/2017PharoDays/ > > PlayList: https://www.youtube.com/playlist?list=PL4actYd6bfnw7ous5We-XnWq0NZquP3gM >

June 13, 2017

Pharo6 deployment issues

by Holger Freyther

Hi! today I started to look at of why my benchmark in the CI stalled/didn't complete and I see three separate issues and wonder how to address them properly? I have a truncated log attached Issues: * In my CI script I disable Deprecation warnings but this has no influence on Deprecation>>#transform. This means that it will try to write the changes?! To scale we start the same image multiple times. * Somehow writing the log fails (and the TCP connection fails the same time?!) with a primitive error. * Errors "recurse". So while we try to exit the image it seems to fail the same way and tries again.. which fails again.. which fails again..at some point no new context will be allocated. Solutions? * Prevent new errors in NonInteractiveUIManager>>#unhandledErrorDefaultAction:? * Check in >>#transform if transformation is disabled and then return early? * ??? No idea.. I will strace to see what happens to the Debug log.. but ideally I would like this file writing to be disabled. :) Should I create tickets? holger dispatch failed on "[ self doExpire. statsdClient flush ]". an OrderedCollection(MultiByteFileStream(Object)>>primitiveFailed: MultiByteFileStream(Object)>>primitiveFailed MultiByteFileStream(StandardFileStream)>>primFlush: MultiByteFileStream(StandardFileStream)>>flush MultiByteFileStream(WriteStream)>>nextChunkPut: SourceFileArray>>writeSource:preamble:onSuccess:onFail: CompiledMethod>>putSource:withPreamble: CompiledMethod>>putSource:class:category:withStamp:priorMethod: VODescriptionBuilder class(ClassDescription)>>logMethodSource:forMethod:inCategory:withStamp: VODescriptionBuilder class(ClassDescription)>>compile:classified:withStamp:notifying:logSource: VODescriptionBuilder class(ClassDescription)>>compile:classified:withStamp:notifying: VODescriptionBuilder class(ClassDescription)>>compile:classified:notifying: VODescriptionBuilder class(ClassDescription)>>compile:classified: [ aMethod origin compile: aMethod ast formattedCode classified: aMethod protocol ] in Deprecation>>transform BlockClosure>>ensure: Author>>useAuthor:during: Author class>>useAuthor:during: Deprecation>>transform Pragma(Object)>>deprecated:transformWith: Pragma>>selector) <snip log about lost TCP connection> PrimitiveFailed: primitive #primClose: in MultiByteFileStream failed MultiByteFileStream(Object)>>primitiveFailed: MultiByteFileStream(Object)>>primitiveFailed MultiByteFileStream(StandardFileStream)>>primClose: MultiByteFileStream(StandardFileStream)>>close SmalltalkImage>>closeLog: [ self closeLog: logStream ] in SmalltalkImage>>logDuring: in Block: [ self closeLog: logStream ] BlockClosure>>ensure: SmalltalkImage>>logDuring: NonInteractiveUIManager(CommandLineUIManager)>>inform: STCommandLineHandler(Object)>>inform: STCommandLineHandler>>handleError:reference: [ :e | self handleError: e reference: aReference ] in STCommandLineHandler>>handleErrorsDuring:reference: in Block: [ :e | self handleError: e reference: aReference ]...etc... BlockClosure>>cull: Context>>evaluateSignal: Context>>handleSignal: Context>>handleSignal: Context>>handleSignal: Context>>handleSignal: Context>>handleSignal: Context>>handleSignal: Context>>handleSignal: Context>>handleSignal: Context>>handleSignal: PrimitiveFailed(Exception)>>signal PrimitiveFailed class(SelectorException class)>>signalFor: MultiByteFileStream(Object)>>primitiveFailed: MultiByteFileStream(Object)>>primitiveFailed MultiByteFileStream(StandardFileStream)>>primClose: MultiByteFileStream(StandardFileStream)>>close SmalltalkImage>>closeLog: FileWriteError: File /build/build/PharoDebug.log write failed MultiByteFileStream(StandardFileStream)>>primWrite:from:startingAt:count: MultiByteFileStream(StandardFileStream)>>nextPut: MultiByteFileStream>>basicNextPut: UTF8TextConverter>>nextPut:toStream: [ :char | self nextPut: char toStream: aStream ] in UTF8TextConverter(TextConverter)>>nextPutAll:toStream: in Block: [ :char | self nextPut: char toStream: aStream ] ByteSymbol(SequenceableCollection)>>do: UTF8TextConverter(TextConverter)>>nextPutAll:toStream: MultiByteFileStream>>nextPutAll: Context>>printOn: MultiByteFileStream(Stream)>>print: Context>>errorReportOn: [ :logger | logger nextPutAll: 'THERE_BE_DRAGONS_HERE'; cr; nextPutAll: errMsg; cr. "just print the error message if no context is given" aContext ifNotNil: [ aContext errorReportOn: logger ]. " write some type of separator" logger nextPutAll: (String new: 79 withAll: $-); cr; cr ] in SmalltalkImage>>logError:inContext: in Block: [ :logger | ... [ logStream := self openLog. aMonadicBlock value: logStream ] in SmalltalkImage>>logDuring: in Block: [ logStream := self openLog.... BlockClosure>>ensure: SmalltalkImage>>logDuring: SmalltalkImage>>logError:inContext: [ Smalltalk logError: aString inContext: aContext. " Print stacks of all current processes " Smalltalk logDuring: [ :logger | logger nextPutAll: 'Processes and their stacks: '; cr. Process allInstances do: [ :each | | ctx | logger nextPutAll: 'Process: '; print: each; cr; nextPutAll: ' stack:'; cr; cr. ctx := each isActiveProcess ifTrue: [ thisContext sender ] ifFalse: [ each suspendedContext ]. ctx ifNotNil: [ (ctx stackOfSize: 20) do: [ :s | logger print: s; cr ] ]. logger nextPutAll: '------------------------------'; cr; cr ] ] ] in NonInteractiveUIManager(CommandLineUIManager)>>quitFrom:withMessage: in Block: [ Smalltalk logError: aString inContext: aContext....etc... BlockClosure>>ensure: NonInteractiveUIManager(CommandLineUIManager)>>quitFrom:withMessage: NonInteractiveUIManager(CommandLineUIManager)>>unhandledErrorDefaultAction: UnhandledError>>defaultAction UndefinedObject>>handleSignal: UnhandledError(Exception)>>signal UnhandledError class>>signalForException: PrimitiveFailed(Error)>>defaultAction UndefinedObject>>handleSignal: PrimitiveFailed(Exception)>>pass [ :ex | ActiveWorld := priorWorld. ActiveEvent := priorEvent. ActiveHand := priorHand. ex pass ] in WorldMorph(PasteUpMorph)>>becomeActiveDuring: in Block: [ :ex | ... BlockClosure>>cull: Context>>evaluateSignal: FileWriteError: File /build/build/PharoDebug.log write failed MultiByteFileStream(StandardFileStream)>>primWrite:from:startingAt:count: MultiByteFileStream(StandardFileStream)>>next:putAll:startingAt: MultiByteFileStream>>basicNext:putAll:startingAt: UTF8TextConverter(TextConverter)>>next:putByteString:startingAt:toStream: UTF8TextConverter(TextConverter)>>next:putAll:startingAt:toStream: MultiByteFileStream>>next:putAll:startingAt: UTF8TextConverter(TextConverter)>>nextPutByteString:toStream: UTF8TextConverter(TextConverter)>>nextPutAll:toStream: MultiByteFileStream>>nextPutAll: Context>>printDetails: Context>>errorReportOn: [ :logger | logger nextPutAll: 'THERE_BE_DRAGONS_HERE'; cr; nextPutAll: errMsg; cr. "just print the error message if no context is given" aContext ifNotNil: [ aContext errorReportOn: logger ]. " write some type of separator" logger nextPutAll: (String new: 79 withAll: $-); cr; cr ] in SmalltalkImage>>logError:inContext: in Block: [ :logger | ... [ logStream := self openLog. aMonadicBlock value: logStream ] in SmalltalkImage>>logDuring: in Block: [ logStream := self openLog.... BlockClosure>>ensure: SmalltalkImage>>logDuring: SmalltalkImage>>logError:inContext: [ Smalltalk logError: aString inContext: aContext. " Print stacks of all current processes " Smalltalk logDuring: [ :logger | logger nextPutAll: 'Processes and their stacks: '; cr. Process allInstances do: [ :each | | ctx | logger nextPutAll: 'Process: '; print: each; cr; nextPutAll: ' stack:'; cr; cr. ctx := each isActiveProcess ifTrue: [ thisContext sender ] ifFalse: [ each suspendedContext ]. ctx ifNotNil: [ (ctx stackOfSize: 20) do: [ :s | logger print: s; cr ] ]. logger nextPutAll: '------------------------------'; cr; cr ] ] ] in NonInteractiveUIManager(CommandLineUIManager)>>quitFrom:withMessage: in Block: [ Smalltalk logError: aString inContext: aContext....etc... BlockClosure>>ensure: NonInteractiveUIManager(CommandLineUIManager)>>quitFrom:withMessage: NonInteractiveUIManager(CommandLineUIManager)>>unhandledErrorDefaultAction: UnhandledError>>defaultAction UndefinedObject>>handleSignal: UnhandledError(Exception)>>signal UnhandledError class>>signalForException: FileWriteError(Error)>>defaultAction UndefinedObject>>handleSignal: FileWriteError(Exception)>>signal FileWriteError(Exception)>>signal: MultiByteFileStream(StandardFileStream)>>primWrite:from:startingAt:count: MultiByteFileStream(StandardFileStream)>>nextPut: FileWriteError: File /build/build/PharoDebug.log write failed MultiByteFileStream(StandardFileStream)>>primWrite:from:startingAt:count: MultiByteFileStream(StandardFileStream)>>next:putAll:startingAt: MultiByteFileStream>>basicNext:putAll:startingAt: UTF8TextConverter(TextConverter)>>next:putByteString:startingAt:toStream: UTF8TextConverter(TextConverter)>>next:putAll:startingAt:toStream: MultiByteFileStream>>next:putAll:startingAt: UTF8TextConverter(TextConverter)>>nextPutByteString:toStream: UTF8TextConverter(TextConverter)>>nextPutAll:toStream: MultiByteFileStream>>nextPutAll: Context>>printOn: MultiByteFileStream(Stream)>>print: Context>>errorReportOn:

June 13, 2017

Re: [Pharo-dev] [Seaside] [ANN] Pharo 6.0 released!

by Esteban Lorenzano

> On 13 Jun 2017, at 11:40, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > This description is not official documentation, only hint for people brave enough to try it :-) > > For own fork synchronization you need to do something like: > > git remote add upstream git@github.com:pharo-project/pharo.git > git fetch upstream > git checkout --track origin/development > git pull upstream development > git push this is like a lot of steps. you usually just need the git pull upstream development git push part :) (the process works always if you already forked pharo and you already did the first clone) > > As soon as the repository is set, you need only to do: > > git fetch upstream > git checkout development > git pull upstream development > git push > > The synchronization can be done from Iceberg directly too. You simply need to pull from upstream and push to your fork. But for big repositories it is slower. what is slow now is the sync window (0.5 will fix that). But pull from a remote/push to your remote will also work on iceberg. Less visual feedback for now, but it will work (I have a proof, I do it like that) :) Esteban > > -- Pavel > > > > 2017-06-13 11:13 GMT+02:00 Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>>: > Hi, > > in fact the development of Pharo 7 has already started. But in a limited mode. > > For Pharo 7 we have the #development branch on GitHub (pharo-project/pharo) > > https://github.com/pharo-project/pharo/tree/development <https://github.com/pharo-project/pharo/tree/development> > > ...and we are already merging pull requests. > > We currently have (mostly technical) problems with the infrastructure so the monkey is not running. But we have a temporary CI jobs that can check specific pull request (that means that we bootstrap Pharo for them and run tests for all platforms). > > The latest Pharo 7 image can be found here: > https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/ <https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/> > > The image is currently not uploaded to files.pharo.org <http://files.pharo.org/> and it is not accessible by zero-conf scripts, sorry. > > If you want to try to create own pull request directly from Pharo 7, you need to do this: > - create own fork of pharo-project/pharo repository on GitHub and keep it in sync > - download Pharo 7 image > - clone pharo-project/pharo repository into the image directory, the directory with the clone MUST be named "pharo-core" > - checkout the development branch or better checkout the commit from which the Pharo 7 image was bootstrapped (SystemVersion current commitHash). Beware, in that case you will be in detached head state (you need to create own issue branch later to be able to commit something). The checkout to a particular commit cannot be done currently from Iceberg, you need to use git > - add your fork repository as a remote and mark it as default push target > - create issue on FogBugz to get issue ID > - create a branch for this issue (can be done easily from the repository context menu in Iceberg [Pharo], this option is valid only if you cloned pharo-project/pharo repository) > - commit the fix to your fork repository > - create the pull request (can be done easily from the repository context menu in Iceberg [Pharo], this option is valid only if you cloned pharo-project/pharo repository) > - add link to the pull request into the FogBugz issue entry > > Pull requests can be done from Pharo 6 too. Then you do not need to have clone in "pharo-core" directory, it can be everywhere, and you mast create your branches from the master branch (and create pull requests on #development) > > Because we currently have limited possibilities to check pull requests, we prefer to merge PRs needed for start of the new integration process. We really do not need to break the system in this fragile state ;-) > > Cheers, > -- Pavel > > > > > > > > 2017-06-13 10:18 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>>: > +1 > When will the development for Pharo 7 start ? (inbox / monkey / ...). > > > > 2017-06-06 21:54 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com <mailto:dionisiydk@gmail.com>>: > Congrats! > > What the status of Pharo 7? When integrations will be started? > > 2017-06-06 17:11 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > Dear World, > > The time has come for Pharo 6.0! > > Pharo is a pure object-oriented programming language and a powerful environment, focused on simplicity and immediate feedback. > > This is our most significant release yet. Here are some highlights: > > - Pharo is now provided in 64-bit version in Linux and OSX and brings even better performance and stability (beware, 64bits version is a new technology and a small amount of tests is still failing) > - A new code changes management system named Epicea for easier reviewing and recovering of your code easily > - Integrated support for Git through an easy-to-use tool for repositories and commits management named Iceberg (as a preview for Pharo 6, it will be the default in Pharo 7) > - The unified foreign function interface (UnifiedFFI) for interfacing with the outside world is significantly improved > - The PharoVM is now part of OpenSmalltalk initiative > - Introduction of object immutability, alternative bytecode sets and block closures independent of outer context > - Pharo can now be bootstrapped from source code managed by Git > - Pharo modularity is improved > - Pharo is faster > - The Dark Theme was improved and set as default color theme of Pharo > > <Pharo6.jpeg> > > These are just the more prominent highlights, but the details are just as important. We have closed 1474 issues in Pharo 6.0 (a more complete changelog can be found at https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo60Change… <https://github.com/pharo-project/pharo-changelogs/blob/master/Pharo60Change…>). > > While the technical improvements are significant (starting the transition to 64bits is a remarkable achievement), still the most impressive fact is that the new code that got in the main Pharo 6.0 image was contributed by more than 80 people. > > Pharo is more than code. It is an exciting project involving energetic people. We thank all the contributors of this release: > > Alberto Bacchelli, Alejandro Infante, Alexandre Bergel, Aliaksei Syrel, Alistair Grant, Andrei Chis, Ben Coman, Bernardo Contreras, Bernhard Pieber, Boris Spasojevic, Christophe Demarey, Clement Bera, Cyril Ferlicot, Dale Henrichs, Damien Cassou, Damien Pollet, Dave Lewis, Denis Kudriashov, Dirk Roeleveld, Eliot Miranda, Esteban Lorenzano, Esteban Maringolo, Evan Donahue, Federico Balaguer, Franck Warlouzet, Glenn Cavarle, Guillermo Polito, Gustavo Santos, Henrik Johansen, Henrik Nergaard, Hilaire Fernandes, Holger Hans, Jan Kurs, Jan van de Sandt, Johan Fabry, Juraj Kubelka, K. K. Subramaniam, Ken Causey, Kris Gybels, Lionel Akue, Luc Fabresse, Lucas Godoy, Marcus Denker, Mariano Martinez Peck, Marion Noirbent, Martin Dias, Max Leske, Maxime Roelandt, Merwan Ouddane, Matteo Bellotto, Miguel Campusano, Milton Mamani, Myroslava Romaniuk, Nicolai Hess, Nicolas Cellier, Nicolas Passerini, Norbert Hartl, Offray Luna, Pablo Tesone, Paul De Bruicker, Pavel Krivanek, Peter Uhnak, Philippe Back, Roger Stebler, Ronie Salgado, Sean DeNigris, Serge Stinckwich, Skip Lentz, Sophie Kaleba, Stefan Reichhart, Stephan Eggermont, Stephane Ducasse, Sven Van Caekenberghe, Thibault Arloing, Thibault Arloing, Thibault Raffaillac, Thierry Goubier, Thomas Heniart, Tommaso Dal Sasso, Torsten Bergmann, Tudor Girba, Udo Schneider, Valentin Ryckewaert, Vincent Blondeau, Werner Kassens, Yuriy Tymchuk > > (If you contributed with Pharo 6.0 development in any way and we missed your name, please send us a mail and we will add you). > > Enjoy! > > The Pharo Team > > Try Pharo: http://pharo.org/download <http://pharo.org/download> > Learn Pharo: http://pharo.org/documentation <http://pharo.org/documentation> > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org <mailto:seaside@lists.squeakfoundation.org> > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside <http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside> > > > > >

June 13, 2017

Re: [Pharo-dev] [Seaside] [ANN] Pharo 6.0 released!

by Pavel Krivanek

This description is not official documentation, only hint for people brave enough to try it :-) For own fork synchronization you need to do something like: git remote add upstream git@github.com:pharo-project/pharo.git git fetch upstream git checkout --track origin/development git pull upstream development git push As soon as the repository is set, you need only to do: git fetch upstream git checkout development git pull upstream development git push The synchronization can be done from Iceberg directly too. You simply need to pull from upstream and push to your fork. But for big repositories it is slower. -- Pavel 2017-06-13 11:13 GMT+02:00 Pavel Krivanek <pavel.krivanek(a)gmail.com>: > Hi, > > in fact the development of Pharo 7 has already started. But in a limited > mode. > > For Pharo 7 we have the #development branch on GitHub (pharo-project/pharo) > > https://github.com/pharo-project/pharo/tree/development > > ...and we are already merging pull requests. > > We currently have (mostly technical) problems with the infrastructure so > the monkey is not running. But we have a temporary CI jobs that can check > specific pull request (that means that we bootstrap Pharo for them and run > tests for all platforms). > > The latest Pharo 7 image can be found here: > https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/ > > The image is currently not uploaded to files.pharo.org and it is not > accessible by zero-conf scripts, sorry. > > If you want to try to create own pull request directly from Pharo 7, you > need to do this: > - create own fork of pharo-project/pharo repository on GitHub and keep it > in sync > - download Pharo 7 image > - clone pharo-project/pharo repository into the image directory, the > directory with the clone MUST be named "pharo-core" > - checkout the development branch or better checkout the commit from which > the Pharo 7 image was bootstrapped (SystemVersion current commitHash). > Beware, in that case you will be in detached head state (you need to create > own issue branch later to be able to commit something). The checkout to a > particular commit cannot be done currently from Iceberg, you need to use git > - add your fork repository as a remote and mark it as default push target > - create issue on FogBugz to get issue ID > - create a branch for this issue (can be done easily from the repository > context menu in Iceberg [Pharo], this option is valid only if you cloned > pharo-project/pharo repository) > - commit the fix to your fork repository > - create the pull request (can be done easily from the repository context > menu in Iceberg [Pharo], this option is valid only if you cloned > pharo-project/pharo repository) > - add link to the pull request into the FogBugz issue entry > > Pull requests can be done from Pharo 6 too. Then you do not need to have > clone in "pharo-core" directory, it can be everywhere, and you mast create > your branches from the master branch (and create pull requests on > #development) > > Because we currently have limited possibilities to check pull requests, we > prefer to merge PRs needed for start of the new integration process. We > really do not need to break the system in this fragile state ;-) > > Cheers, > -- Pavel > > > > > > > > 2017-06-13 10:18 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: > >> +1 >> When will the development for Pharo 7 start ? (inbox / monkey / ...). >> >> >> >> 2017-06-06 21:54 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: >> >>> Congrats! >>> >>> What the status of Pharo 7? When integrations will be started? >>> >>> 2017-06-06 17:11 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >>> >>>> Dear World, >>>> >>>> The time has come for Pharo 6.0! >>>> >>>> Pharo is a pure object-oriented programming language and a powerful >>>> environment, focused on simplicity and immediate feedback. >>>> >>>> This is our most significant release yet. Here are some highlights: >>>> >>>> - Pharo is now provided in 64-bit version in Linux and OSX and brings >>>> even better performance and stability (beware, 64bits version is a new >>>> technology and a small amount of tests is still failing) >>>> - A new code changes management system named Epicea for easier >>>> reviewing and recovering of your code easily >>>> - Integrated support for Git through an easy-to-use tool for >>>> repositories and commits management named Iceberg (as a preview for Pharo >>>> 6, it will be the default in Pharo 7) >>>> - The unified foreign function interface (UnifiedFFI) for interfacing >>>> with the outside world is significantly improved >>>> - The PharoVM is now part of OpenSmalltalk initiative >>>> - Introduction of object immutability, alternative bytecode sets and >>>> block closures independent of outer context >>>> - Pharo can now be bootstrapped from source code managed by Git >>>> - Pharo modularity is improved >>>> - Pharo is faster >>>> - The Dark Theme was improved and set as default color theme of Pharo >>>> >>>> >>>> These are just the more prominent highlights, but the details are just >>>> as important. We have closed 1474 issues in Pharo 6.0 (a more complete >>>> changelog can be found at https://github.com/pharo-proje >>>> ct/pharo-changelogs/blob/master/Pharo60ChangeLogs.md). >>>> >>>> While the technical improvements are significant (starting the >>>> transition to 64bits is a remarkable achievement), still the most >>>> impressive fact is that the new code that got in the main Pharo 6.0 image >>>> was contributed by more than 80 people. >>>> >>>> Pharo is more than code. It is an exciting project involving energetic >>>> people. We thank all the contributors of this release: >>>> >>>> Alberto Bacchelli, Alejandro Infante, Alexandre Bergel, Aliaksei Syrel, >>>> Alistair Grant, Andrei Chis, Ben Coman, Bernardo Contreras, Bernhard >>>> Pieber, Boris Spasojevic, Christophe Demarey, Clement Bera, Cyril Ferlicot, >>>> Dale Henrichs, Damien Cassou, Damien Pollet, Dave Lewis, Denis Kudriashov, >>>> Dirk Roeleveld, Eliot Miranda, Esteban Lorenzano, Esteban Maringolo, Evan >>>> Donahue, Federico Balaguer, Franck Warlouzet, Glenn Cavarle, Guillermo >>>> Polito, Gustavo Santos, Henrik Johansen, Henrik Nergaard, Hilaire >>>> Fernandes, Holger Hans, Jan Kurs, Jan van de Sandt, Johan Fabry, Juraj >>>> Kubelka, K. K. Subramaniam, Ken Causey, Kris Gybels, Lionel Akue, Luc >>>> Fabresse, Lucas Godoy, Marcus Denker, Mariano Martinez Peck, Marion >>>> Noirbent, Martin Dias, Max Leske, Maxime Roelandt, Merwan Ouddane, Matteo >>>> Bellotto, Miguel Campusano, Milton Mamani, Myroslava Romaniuk, Nicolai >>>> Hess, Nicolas Cellier, Nicolas Passerini, Norbert Hartl, Offray Luna, Pablo >>>> Tesone, Paul De Bruicker, Pavel Krivanek, Peter Uhnak, Philippe Back, Roger >>>> Stebler, Ronie Salgado, Sean DeNigris, Serge Stinckwich, Skip Lentz, Sophie >>>> Kaleba, Stefan Reichhart, Stephan Eggermont, Stephane Ducasse, Sven Van >>>> Caekenberghe, Thibault Arloing, Thibault Arloing, Thibault Raffaillac, >>>> Thierry Goubier, Thomas Heniart, Tommaso Dal Sasso, Torsten Bergmann, Tudor >>>> Girba, Udo Schneider, Valentin Ryckewaert, Vincent Blondeau, Werner >>>> Kassens, Yuriy Tymchuk >>>> >>>> (If you contributed with Pharo 6.0 development in any way and we missed >>>> your name, please send us a mail and we will add you). >>>> >>>> Enjoy! >>>> >>>> The Pharo Team >>>> >>>> Try Pharo: http://pharo.org/download >>>> Learn Pharo: http://pharo.org/documentation >>>> >>>> _______________________________________________ >>>> seaside mailing list >>>> seaside(a)lists.squeakfoundation.org >>>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>>> >>>> >>> >> >

June 13, 2017

Re: [Pharo-dev] [Seaside] [ANN] Pharo 6.0 released!

by Pavel Krivanek

Hi, in fact the development of Pharo 7 has already started. But in a limited mode. For Pharo 7 we have the #development branch on GitHub (pharo-project/pharo) https://github.com/pharo-project/pharo/tree/development ...and we are already merging pull requests. We currently have (mostly technical) problems with the infrastructure so the monkey is not running. But we have a temporary CI jobs that can check specific pull request (that means that we bootstrap Pharo for them and run tests for all platforms). The latest Pharo 7 image can be found here: https://ci.inria.fr/pharo/view/7.0/job/70-Bootstrap-32bit/ The image is currently not uploaded to files.pharo.org and it is not accessible by zero-conf scripts, sorry. If you want to try to create own pull request directly from Pharo 7, you need to do this: - create own fork of pharo-project/pharo repository on GitHub and keep it in sync - download Pharo 7 image - clone pharo-project/pharo repository into the image directory, the directory with the clone MUST be named "pharo-core" - checkout the development branch or better checkout the commit from which the Pharo 7 image was bootstrapped (SystemVersion current commitHash). Beware, in that case you will be in detached head state (you need to create own issue branch later to be able to commit something). The checkout to a particular commit cannot be done currently from Iceberg, you need to use git - add your fork repository as a remote and mark it as default push target - create issue on FogBugz to get issue ID - create a branch for this issue (can be done easily from the repository context menu in Iceberg [Pharo], this option is valid only if you cloned pharo-project/pharo repository) - commit the fix to your fork repository - create the pull request (can be done easily from the repository context menu in Iceberg [Pharo], this option is valid only if you cloned pharo-project/pharo repository) - add link to the pull request into the FogBugz issue entry Pull requests can be done from Pharo 6 too. Then you do not need to have clone in "pharo-core" directory, it can be everywhere, and you mast create your branches from the master branch (and create pull requests on #development) Because we currently have limited possibilities to check pull requests, we prefer to merge PRs needed for start of the new integration process. We really do not need to break the system in this fragile state ;-) Cheers, -- Pavel 2017-06-13 10:18 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: > +1 > When will the development for Pharo 7 start ? (inbox / monkey / ...). > > > > 2017-06-06 21:54 GMT+02:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > >> Congrats! >> >> What the status of Pharo 7? When integrations will be started? >> >> 2017-06-06 17:11 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> Dear World, >>> >>> The time has come for Pharo 6.0! >>> >>> Pharo is a pure object-oriented programming language and a powerful >>> environment, focused on simplicity and immediate feedback. >>> >>> This is our most significant release yet. Here are some highlights: >>> >>> - Pharo is now provided in 64-bit version in Linux and OSX and brings >>> even better performance and stability (beware, 64bits version is a new >>> technology and a small amount of tests is still failing) >>> - A new code changes management system named Epicea for easier reviewing >>> and recovering of your code easily >>> - Integrated support for Git through an easy-to-use tool for >>> repositories and commits management named Iceberg (as a preview for Pharo >>> 6, it will be the default in Pharo 7) >>> - The unified foreign function interface (UnifiedFFI) for interfacing >>> with the outside world is significantly improved >>> - The PharoVM is now part of OpenSmalltalk initiative >>> - Introduction of object immutability, alternative bytecode sets and >>> block closures independent of outer context >>> - Pharo can now be bootstrapped from source code managed by Git >>> - Pharo modularity is improved >>> - Pharo is faster >>> - The Dark Theme was improved and set as default color theme of Pharo >>> >>> >>> These are just the more prominent highlights, but the details are just >>> as important. We have closed 1474 issues in Pharo 6.0 (a more complete >>> changelog can be found at https://github.com/pharo-proje >>> ct/pharo-changelogs/blob/master/Pharo60ChangeLogs.md). >>> >>> While the technical improvements are significant (starting the >>> transition to 64bits is a remarkable achievement), still the most >>> impressive fact is that the new code that got in the main Pharo 6.0 image >>> was contributed by more than 80 people. >>> >>> Pharo is more than code. It is an exciting project involving energetic >>> people. We thank all the contributors of this release: >>> >>> Alberto Bacchelli, Alejandro Infante, Alexandre Bergel, Aliaksei Syrel, >>> Alistair Grant, Andrei Chis, Ben Coman, Bernardo Contreras, Bernhard >>> Pieber, Boris Spasojevic, Christophe Demarey, Clement Bera, Cyril Ferlicot, >>> Dale Henrichs, Damien Cassou, Damien Pollet, Dave Lewis, Denis Kudriashov, >>> Dirk Roeleveld, Eliot Miranda, Esteban Lorenzano, Esteban Maringolo, Evan >>> Donahue, Federico Balaguer, Franck Warlouzet, Glenn Cavarle, Guillermo >>> Polito, Gustavo Santos, Henrik Johansen, Henrik Nergaard, Hilaire >>> Fernandes, Holger Hans, Jan Kurs, Jan van de Sandt, Johan Fabry, Juraj >>> Kubelka, K. K. Subramaniam, Ken Causey, Kris Gybels, Lionel Akue, Luc >>> Fabresse, Lucas Godoy, Marcus Denker, Mariano Martinez Peck, Marion >>> Noirbent, Martin Dias, Max Leske, Maxime Roelandt, Merwan Ouddane, Matteo >>> Bellotto, Miguel Campusano, Milton Mamani, Myroslava Romaniuk, Nicolai >>> Hess, Nicolas Cellier, Nicolas Passerini, Norbert Hartl, Offray Luna, Pablo >>> Tesone, Paul De Bruicker, Pavel Krivanek, Peter Uhnak, Philippe Back, Roger >>> Stebler, Ronie Salgado, Sean DeNigris, Serge Stinckwich, Skip Lentz, Sophie >>> Kaleba, Stefan Reichhart, Stephan Eggermont, Stephane Ducasse, Sven Van >>> Caekenberghe, Thibault Arloing, Thibault Arloing, Thibault Raffaillac, >>> Thierry Goubier, Thomas Heniart, Tommaso Dal Sasso, Torsten Bergmann, Tudor >>> Girba, Udo Schneider, Valentin Ryckewaert, Vincent Blondeau, Werner >>> Kassens, Yuriy Tymchuk >>> >>> (If you contributed with Pharo 6.0 development in any way and we missed >>> your name, please send us a mail and we will add you). >>> >>> Enjoy! >>> >>> The Pharo Team >>> >>> Try Pharo: http://pharo.org/download >>> Learn Pharo: http://pharo.org/documentation >>> >>> _______________________________________________ >>> seaside mailing list >>> seaside(a)lists.squeakfoundation.org >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >>> >>> >> >

June 13, 2017