I fixed the files under http://pharo.gforge.inria.fr/updates/ so that
all of them are now tracked in the git repository.

now the only thing missing is changing the update process to work on
proper branches ;):

Currently there is a branch for each pharo-release: 10, 11, 12, 13, 14, 20

- Each update should then be applied to a dev branch which triggers all the 
  tests
- after all tests succeed the dev branch is merged into the stable branch by
  our ci services.

The update-process on the ci server is almost ready: 

- Pharo-2.0-Update-Tracker
- Pharo-2.0-Update-Validation
- Pharo-2.0-Update-Release


What is missing? Get Pharo down to 0 Failing tests :P

Reply via email to