On Thu, 2011-07-07 at 09:51 -0400, Kamil Paral wrote:
> > > OTOH I'm also fine with switching to using release
branches. They
> > > are
> > > pretty. And it may be simpler for understanding that our current
> > > approach.
> >
> > I think this is cleaner and easier than merging but still preserves
> > the
> > commit history. This gets my vote going forward.
>
> I'm more accustomed to this approach, so this would get my vote.
It is decided then. I created a first shot at the documentation at:
https://fedoraproject.org/wiki/User:Kparal/Sandbox:Git_release_process
If you don't have any concerns, I'll merge it into the final release
documentation page [1].
[1]
https://fedoraproject.org/wiki/AutoQA_Release_Process
Nice ... I'll absorb your draft and offer any feedback shortly.
I'd like to see the entire process handled by make targets to avoid
inconsistent branch and tag names. I'm thinking things like ... 'make
newversion' and 'make tag' etc... I'll experiment with that once the
document is finalized.
Thanks,
James