It is encouraged that the "next" branch is used except for packages that you are actively developing.

The git repositories are also set up so that

git push
git push autobuild

will always push to master, to avoid having people pushing changes to next by accident. Unfortunately, I did not find any way to make sure that it does not happen when pushing from git-gui

To use "next":

General policy

Projects should use next whenever possible. For now, the strategy is to use "next" for all packages that are not actively developed within a given project (i.e. developed by the team that is using the build configuration).

Select the "next" flavor

This can be done in two ways:

  • The main autoproj configuration for rock allows selecting it. For people that already have their own main autoproj configuration, you can either change it to match what is done in

(you mainly need to copy the rock.rb file, require it in init.rb and call rock_autoproj_init)

  • you forcefully set it in your init.rb by doing Autoproj.change_option("ROCK_FLAVOR", "next")

Override the branch for the packages that you want to develop

This can be done install-wide by adding an overrides section to autoproj/overrides.yml or in the source.yml file of some package set. The section should look like

   - package_name:
     branch: master

The package name can be a regular expression, so

   - .*:
     branch: master

would select master for every package in the installation

Last modified 10 years ago Last modified on 05/27/11 17:11:45