From: Mark Nelson <mark.nelson@inktank.com>
To: Sage Weil <sage@inktank.com>
Cc: ceph-devel@vger.kernel.org
Subject: Re: branches
Date: Tue, 08 Jan 2013 12:48:26 -0600 [thread overview]
Message-ID: <50EC69FA.2030205@inktank.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1301081038580.30467@cobra.newdream.net>
On 01/08/2013 12:39 PM, Sage Weil wrote:
> I'd like to adjust the branches we're maintaining in ceph.git. Currently:
>
> master
> - active development
> next
> - frozen for next release
> - bug fixes only
> - regularly merged back into master
> testing
> - last development release
> - cherry-pick -x'd critical fixes
> - packages at ceph.com/debian-testing, /rpm-testing
> stable
> - argonaut long-term backport series
> - cherry-pick -x'd critical fixes
> - packages at ceph.com/debian-argonaut, /debian
>
> The stable is ambiguous, and testing is a confusing name. Instead, I
> propose:
>
> master -- same
> next -- same
> last
> - last release (instead of 'testing')
> - packages at /debian-testing and /debian-last, /rpm-testing, /rpm-last
I actually think I liked the testing name, but don't have a real strong
opinion.
> bobtail
> - bobtail backport series 0.56.x
> - packages at /debian-bobtail (and /debian, until cuttlefish),
> /rpm-bobtail, /rpm
> argonaut
> - argonaut backport series 0.48.x
> - packages at /debian-argonaut
>
Definitely yes.
> We'll need to update the parallel branches in teuthology.git,
> ceph-qa-suite.git, and s3-tests.git to match.
>
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-01-08 18:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 18:39 branches Sage Weil
2013-01-08 18:48 ` Mark Nelson [this message]
2013-01-18 18:32 ` branches Sage Weil
2013-01-18 19:02 ` branches Stefan Priebe
2013-01-18 19:36 ` branches Sage Weil
2013-01-18 21:06 ` branches Nick Couchman
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=50EC69FA.2030205@inktank.com \
--to=mark.nelson@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.com \
/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.