This is the mail archive of the
libc-ports@sources.redhat.com
mailing list for the libc-ports project.
Re: 2.10 branch for ports
- From: Roland McGrath <roland at redhat dot com>
- To: "Joseph S. Myers" <joseph at codesourcery dot com>
- Cc: libc-ports at sourceware dot org
- Date: Thu, 30 Jul 2009 12:45:26 -0700 (PDT)
- Subject: Re: 2.10 branch for ports
- References: <Pine.LNX.4.64.0907291640170.9464@digraph.polyomino.org.uk>
Sounds fine to me. What I'd like to see is the weeest bit of formality
about ports release branch policy. That is, something written on the wiki
saying how the process works and what the rules are, etc. I don't think we
need (or could get) much real formality in who is the release branch
manager or codified procedures or anything. But some written guidelines
and pointers would be good.
The decisions about what cherry-picks go onto which release branches belong
to the ports maintainer for the given arch, or to someone that maintainer
has delegated to. For each particular release branch, the consensus of
participating ports maintainers (in lieu of a formal branch manager) can
decide what the procedure for git is. For some cycles, it might be that
each maintainer just does the push with their arch's changes whenever.
For others, it might be that someone is charged with doing the merge/push
of all the release branch tips coming in from particular arch maintainers.
Thanks,
Roland