| 57 | | We lack the manpower to do this; volunteer help is needed. |
| | 57 | We lack the manpower to do this; volunteer help is needed. Hint: take a look at [[http://seleniumhq.org|Selenium]]. |
| | 58 | * '''Improved SCM workflow''': We need to introduce code branches to isolate ongoing development from release and maintenance processes ''in order to stabilise the codebase and facilitate stable releases''. |
| | 59 | * Develop new features in dedicated "feature branches", branching off master. Merge back into master when developer testing was successful (features can be pretty small, merge often) |
| | 60 | * Create a "next" or a "release candidate" branch for the upcoming release, branching off master. Test and fix release until ready for release, merge fixes back to master |
| | 61 | * Maintain each release in its dedicated branch to allow for maintenance. Merge fixes back to master. |
| | 62 | * Alternatively, go for "[[http://nvie.com/posts/a-successful-git-branching-model|the real thing]]" using [[https://github.com/nvie/gitflow|git-flow]]. |
