[petsc-dev] workflow diagram

[Jed Brown]

Karl Rupp <rupp at iue.tuwien.ac.at> writes:
> One more thing: The graph does not contain the case where a feature 
> branch has been merged to master, but is soon after found to be buggy. A 
> discussion of how this gets resolved (new fix-branch vs. fixing the 
> feature branch) is needed as this shows up occasionally in practice.

It's not supposed to. ;-)

I don't know how to add this without creating too much clutter.  My
typical rule of thumb is to start bug-fix branches at the buggy commit
if it is easily determined and has the necessary dependencies to fix.
Otherwise start it on the oldest branch that may need the fix.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20140430/6319840b/attachment.sig>