Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

DevelopmentGuidelines

Will Rogers edited this page Apr 4, 2016 · 2 revisions

  • All commits to master and stable must be a pull request

  • All commits reference a github issue number

  • The Hot Fix branch is for quickly testing urgent bug fixes and patches that need to be incorporated into the current release branch

  • The Master branch is a release preparation branch, once a feature is ready for release it is merged in to the master via a pull request tested and then included in the next release branch

  • Once a project is ready to be incorporated into a release it is added to the master (release preparation) branch via a pull request

  • The project branches are used by developers to create new applications and features, this can be done in a separate fork too, when projects are done the branch is removed

  • Forks can be used for

    1. preparing bug fixes when can then be added to the hot fix branch with a pull request
    2. performing development work which does not merit a new named branch in the main repo
    3. by external developers

Mylyn users: http://eclipsesource.com/blogs/2012/08/28/tips-and-tricks-using-eclipse-with-github/

Github help: https://help.github.com/articles/using-pull-requests

Clone this wiki locally

Morty Proxy This is a proxified and sanitized view of the page, visit original site.