DragonFly bugs List (threaded) for 2005-08
Re: A patch against FreeBSD-SA-05:15.tcp
:Could you let me know the procedure of MFC?
: 1. Prepare a patch against FreeBSD-SA-05:15.tcp to
: for DragonFly_RELEASE_1_2_Slip.
: 2. Wait for a sign from Matt.
: 3. Commit the prepared patch to DragonFly_RELEASE_1_2_Slip
: in the same way as the commit to HEAD.
:Is this correct?
Minimum 1 week wait before something goes into the release branch.
The release branch is DragonFly_RELEASE_1_2. That is what you would
commit into. You don't have to worry about it after that.
Generally I'm the only one who slips the slip tag. It doesn't become
truely official until I bump the release sub-version and synchronize
the slip tag on the release branch. The idea here is that we might get
a dribbling of MFCs into the release branch, and we want committers to
be able to MFC those, but we don't want to bump the subversion each time
or create confusion by rolling lots of subversions/official-updates. So
the slip tag will not typically be synchronized any faster then once a
month, depending, and I'm usually the only one who does it.