fenics team mailing list archive

[Martin Sandve Alnæs <martinal@xxxxxxxxx>]

I think the main challenge for us is to adapt the workflow to
cross-project changes.

How to deal with topic branches for cross-project features is not
discussed directly in gitworkflows, but I guess the natural extension
is simply to:
- Create topic branches with same name across relevant projects.
- Do each step such as merging into maint/master/next, etc.
simultaneously for all projects.

The core point being that maint/master/next/mytopic brances must be
kept compatible across projects at any time (when published).

There's a potential race condition if Alice and Bob try pushing
simultaneously to fenics/*/master, but that's not a new problem.

Martin