[petsc-dev] petsc branching methodology?

Jed Brown jed at jedbrown.org
Tue Nov 3 11:29:25 CST 2015

Sean Farley <sean at farley.io> writes:

> JR Cary <cary at txcorp.com> writes:
>> Thanks, Jed.
>> Just in case anyone has any thoughts, ideas, experience along this 
>> direction...
>> We have multiple internal library projects, lib1, lib2,...., and then
>> multiple applications, app1, app2, app3, all in different repos, and we
>> are trying to come up with a branching/merging strategy that gives the
>> best compromise between stability and agility.
> Careful. Here be dragons.

I concur.  I would not consider this model unless you have a very clear
understanding of the customer needs, relative maturity of the
components, and release/maintenance requirements.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20151103/8b7c094c/attachment.sig>

More information about the petsc-dev mailing list