[MOAB-dev] MOAB git branching model

[Tim Tautges]

On 09/17/2013 06:07 PM, Jed Brown wrote:
> Tim Tautges <tautges at mcs.anl.gov> writes:
>> 2) I think we should go to a more formalized repo structure and branching/release process, similar to what is described
>> in http://nvie.com/posts/a-successful-git-branching-model/.
>
> While "git-flow" is better than no branching model, I think it is
> terrible.  I wrote a fairly comprehensive explanation:
>
> http://mail-archive.com/search?l=mid&q=87zjx4x417.fsf@mcs.anl.gov
>

My concern with the petsc workflow is about branch merges to next taking awhile to graduate to master.  However, looking 
over the repo structure, it seems like that happens quickly enough in petsc.

For releases, do they just get tagged on master, or is there a separate release branch?  If the former, do point 
releases get inserted into master as well?

And, does auto testing happen on next?  I'd assume so (and on master too, of course?).

- tim

-- 
================================================================
"You will keep in perfect peace him whose mind is
   steadfast, because he trusts in you."               Isaiah 26:3

              Tim Tautges            Argonne National Laboratory
          (tautges at mcs.anl.gov)      (telecommuting from UW-Madison)
  phone (gvoice): (608) 354-1459      1500 Engineering Dr.
             fax: (608) 263-4499      Madison, WI 53706