[Glass] Notes on working with Github

With git/github, the projects tend to be in continuous release mode. I do development on a topic branch and when the travis-ci[5] build is green and I am "done" I merge the work into the master branch ... Moving forward I don't plan on sending mail to this list every time that I merge to master, so the question is how do you know what is happening?

For GsDevKit and tODE I recommend that you start "watching" the repositories[7]. You will receive email when a commit is made to the repository or issues are submitted. When an email announces a merge to master, you should consider updating ... especially if you've seen email addressing problems you are seeing go by ...

For updating tODE, you only need to use the 'load' menu item in the `project list` and tODE will be reloaded and you will pick up the new version. To update your pharo client image(s) to use the latest tODE, run the updateTodeImage[9] shell script.

For GsDevKit, it's a bit more complicated because you have forked the repository. Fortunately you can use a GitHub pull request to pull from  GsDevKit/gsDevKitHome to your fork. If you're not familiar with the procedure, here's a little writeup on doing a "reverse pull request"[8].

Once you've updated the master branch of your fork, you can use the same technique to merge the master branch into your working branch. Then on your local machine, you will do a `git pull origin <your branch>`. Then you can run the updateTodeImage[9] shell script to update your pharo clients.

Hope this helps,

Dale

[4] http://git-scm.com/book/en/Git-Branching-Branching-Workflows#Topic-Branches

[5] https://travis-ci.org/GsDevKit/gsDevKitHome

[6] https://github.com/dalehenrich/metacello-work

[7] https://github.com/blog/1204-notifications-stars

[8] https://github.com/GsDevKit/gsDevKitHome/blob/master/docs/reversePullRequest.md#reverse-pull-request

[9] https://github.com/GsDevKit/gsDevKitHome/blob/master/bin/updateTodeImage