On Thu, Nov 01, 2012 at 03:12:46AM +0000, Cl??udio Martins wrote: > > On Wed, 31 Oct 2012 14:38:28 -0700 (PDT) Sage Weil <s...@inktank.com> wrote: > > On Wed, 31 Oct 2012, Noah Watkins wrote: > > > Which branch is the freeze taken against? master? > > > > Right. Basically, every 3-4 weeks: > > > > - next is tagged as v0.XX > > - and is merged back into master > > - next branch is reset to current master > > - testing branch is reset to just-tagged v0.XX > > > > Hmm, interesting. But doesn't that mean that when the real v0.XX is > later officially _released_, its top commit might not be the commit > that was tagged as v0.XX? Assuming that issues are found after the > testing branch is reset to v0.XX, fixes would go on top of v0.XX, right? > > Am I missing something, or people checking out a v0.XX with git might > not be getting the real v0.XX that was released as tarballs?
The tarball is released as soon as it's tagged. The tag never changes once it's tagged. Therefore tag v0.XX == tarball v0.XX. -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
