[petsc-dev] workflow diagram

[Satish Balay]

On Wed, 30 Apr 2014, Satish Balay wrote:

> On Wed, 30 Apr 2014, Jed Brown wrote:
> 
> > Peter Brune <prbrune at gmail.com> writes:
> > 
> > > In fact, this may be part of Barry's point too... you could emphasize the
> > > testing time for each of the feature/bugfix branches by putting the testing
> > > arrow after the branch. and showing that it ends when merged.
> > 
> > Done, though it's a bit more cluttered now.
> 
> Perhaps if there arrows were flipped the confusion could be reduced?
> 
> [Somehow the commits should be accentuated to the timescale - and not the arrows]

BTW: instead of associating 'discard when next is rewound' to the
dotted arrows - I'll suggest using the same 'merge' arrow notation here.

And then somehow show that the 'next branch is discared and
reconstruced (from master) at the next release..

Satish