Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Scout/Contribution Guidelines

The Scout documentation has been moved to https://eclipsescout.github.io/.

Introduction

TODO

Git Branching Policy

The following table describes the branching policy used for the Eclipse Scout Git Repositories (http://git.eclipse.org/c/scout/).

Branch Usage
develop Contains the very latest sources. This branch is used for building the nightly version and contains the development of the newest features that usually will be available to the next stable release.
master Contains the sources of the latest stable release. This is equal to the sources for the features found in the P2 updatesite http://download.eclipse.org/scout/releases
release/<release_name> Contains the development for the corresponding releases. So e.g. a release branch named luna_sr1 contains the fixes for the Luna service release 1. These branches will be merged into the master and develop branches as soon as the corresponding release is shipped. Afterwards the branch is deleted and the merge into the master branch is tagged.
sandbox/*
hotfix/*

Git Repositories and current Branches

Please see http://wiki.eclipse.org/Scout/Contribution#Getting_the_Scout_Sources.

Back to the top