On 06/21/2012 10:40 AM, Lucas Meneghel Rodrigues wrote:
> Hi guys,
>
> I ask your suggestions about release management.
>
> One thing that is proving to be a good decision was the creation of the
> 'next' branch. We're able to control what's going to 'master' better
> with it. But right now, we have our release tags referencing commits in
> master:
>
> 0.14.0 -> commit in master
> 0.14.1 -> commit in master
>
> So on and so forth...
>
> Now with Fedora packaging (and possibly other use cases), it is
> necessary that we extend the life cycle of a release, by having release
> based branches, say 0.14, and we would cherry pick fixes from master for
> an extended period of time, so we can release 0.14.2, 0.14.3,... so on
> and so forth.
>
> I'm inclined to go ahead and start doing it, but I'd like to hear your
> opinion about it.
>
> Cheers,
>
> Lucas
Lucas,
Thanks, seeing this in writing helps :D
Would we still have tags on master branch for releases, or just move
releases to be all branch-based? i.e.
master
\
|--- 0.14.0
| \
| |---0.14.1
| \
| --- 0.14.2
\
--- 0.15.0
\
--- 0.15.1
or both,
master (tags: 0.14, 0.15, ...)
\
|--- 0.14.0
| \
| |---0.14.1
| \
| --- 0.14.2
\
--- 0.15.0
\
--- 0.15.1
?
Using branches get's us automatic tarball'ing on github, no? What would
using tags off master buy us? Would it help in case we need to port a
fix from 0.15 based master tag to 0.14.x branch?
--
Chris Evich, RHCA, RHCE, RHCDS, RHCSS
Quality Assurance Engineer
e-mail: cevich + `@' + redhat.com o: 1-888-RED-HAT1 x44214
_______________________________________________
Autotest mailing list
[email protected]
http://test.kernel.org/cgi-bin/mailman/listinfo/autotest
