Changes between Version 20 and Version 21 of StartModMaint

Timestamp:

Dec 14, 2013, 3:00:17 PM (9 years ago)

Author:

Beman Dawes

Comment:

--

StartModMaint

@@ -22 +22 @@
 == Getting started ==
 
-The preferred development environment is usually for the library being worked on have a development branch checked out, while Boost super-project and other libraries remain on the {{{master}}} branch.
-
-=== Checking out the development branch ===
+The preferred development environment is usually for the library being worked on have a development branch checked out, while Boost super-project and other Boost libraries are on the {{{master}}} branch. This causes tests of your library to run against {{{master}}} of other Boost libraries and that is a more realistic test environment in than the possibly unstable {{{develop}}} branch of other Boost libraries.
+
+=== Update super-project and submodules for all libraries ===
+
+{{{
+cd modular-boost
+git checkout master
+git pull --recurse-submodules
+
+}}} 
+
+=== Check out the development branch of your library ===
 
 You can see what branch {{{mylib}}} is currently on like this:
@@ -199 +208 @@
 
 Large, complex libraries, particularly those with multiple developers working in parallel, need to use a release procedure that scales up better than the lightweight procedure. The Git Flow approach is recommended. Find out more at [wiki:StartModWorkflow Modular Boost Library Workflow Overview] and be sure to study the examples given in [http://nvie.com/posts/a-successful-git-branching-model/ Vincent Driessen's original blog posting].
+