Congrats! What the status of Pharo 7? When integrations will be started? 2017-06-06 17:11 GMT+02:00 Esteban Lorenzano <[hidden email]>:
|
Congratulations! :-D
Martín ps: I'll report in another email a small issue with curl and zeroconf for 64 bits On Tue, Jun 6, 2017 at 12:11 PM, Esteban Lorenzano <[hidden email]> wrote:
|
In reply to this post by Denis Kudriashov
+1 When will the development for Pharo 7 start ? (inbox / monkey / ...).2017-06-06 21:54 GMT+02:00 Denis Kudriashov <[hidden email]>:
|
Hi nicolai Last week we got a sync point to see what should be done. And Guille and Pavel started to set up some new monkey and check the full process. Esteban should do an announce soon. Stef On Tue, Jun 13, 2017 at 10:18 AM, Nicolai Hess <[hidden email]> wrote:
|
In reply to this post by Nicolai Hess-3-2
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) ...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: 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 <[hidden email]>:
|
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 [hidden email]: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 <[hidden email]>:
|
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)
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
|
Free forum by Nabble | Edit this page |