From: Mike Ryan <mike.ryan@inktank.com>
To: Cl??udio Martins <ctpm@ist.utl.pt>
Cc: ceph-devel@vger.kernel.org
Subject: Re: bobtail timing
Date: Wed, 31 Oct 2012 20:17:28 -0700 [thread overview]
Message-ID: <20121101031728.GF19642@splice> (raw)
In-Reply-To: <20121101031246.fcc80a63e2506af3fcaa9dda@ist.utl.pt>
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 <sage@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.
next prev parent reply other threads:[~2012-11-01 3:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 20:46 bobtail timing Sage Weil
2012-10-31 21:35 ` Noah Watkins
2012-10-31 21:38 ` Sage Weil
2012-11-01 3:12 ` Cláudio Martins
2012-11-01 3:17 ` Mike Ryan [this message]
2012-11-01 3:17 ` Sage Weil
2012-11-01 4:14 ` Cláudio Martins
2012-11-09 1:30 ` Yehuda Sadeh
2012-11-09 3:23 ` Samuel Just
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121101031728.GF19642@splice \
--to=mike.ryan@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=ctpm@ist.utl.pt \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.