All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Abhishek Varshney <abhishek.varshney@flipkart.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: creating the issue for the v0.94.4 release
Date: Sat, 15 Aug 2015 12:30:35 +0200	[thread overview]
Message-ID: <55CF14CB.1040900@dachary.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1326 bytes --]

Hi Abhishek,

I'll be driving the next hammer point release (v0.94.4) and theanalyst will participate as I did for v0.94.3 (i.e. helping and mentoring when there is a need). During the v0.94.4 release you will have the opportunity to participate in all the steps. When we move to v0.94.5 you'll hopefully know all you need to drive it, should you want to. As you discovered over the past few weeks, it's not a complex process, but there are a lot of details. 

Contrary to what I told you the other day

http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO_start_backporting_a_stable_release/diff?utf8=%E2%9C%93&version=7&version_from=6&commit=View+differences

is not the documentation you need to create a new ticket for v0.94.4 and I removed this chapter to avoid further confusion. There is a more detailed explanation at:

http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO_start_working_on_a_new_point_release

A section was added as a reminder that someone has to volunteer to drive the release. 

http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO_start_working_on_a_new_point_release/diff?utf8=%E2%9C%93&version=9&version_from=8&commit=View+differences

Let me know if you need anything else to create the issue vor v0.94.4.

Cheers
-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2015-08-15 10:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-15 10:30 Loic Dachary [this message]
     [not found] ` <CAP3mxSyGkYz6vfbE4sNkV2K6iS4waBrptQ+Vnfprqc75Uc2CHg@mail.gmail.com>
2015-08-15 16:17   ` creating the issue for the v0.94.4 release Loic Dachary
     [not found]     ` <CAP3mxSyqMCicjzPGo119j5krgr74NnN1cp9D1mswdg=FLGqD_A@mail.gmail.com>
2015-08-15 20:15       ` Loic Dachary
2015-08-17 13:51         ` Alexandre DERUMIER
2015-08-17 16:09           ` rbd: default map options, new options, misc (Re: creating the issue for the v0.94.4 release) Loic Dachary

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=55CF14CB.1040900@dachary.org \
    --to=loic@dachary.org \
    --cc=abhishek.varshney@flipkart.com \
    --cc=ceph-devel@vger.kernel.org \
    /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.