All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Should we create a "Stable releases" project on tracker.ceph.com ?
Date: Sun, 01 Mar 2015 00:51:36 +0100	[thread overview]
Message-ID: <54F25488.6050703@dachary.org> (raw)

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

Hi Ceph,

In the past few weeks I issues in the tracker of the Ceph project to update the progress of the ongoing effort to publish stable point releases (i.e. backports) at http://tracker.ceph.com/issues/10640. It started somewhat messy but turned out to be a convenient point of reference, with one issue for each stable release (see http://tracker.ceph.com/issues/10641 for firefly v0.80.9 for instance). The issues were set a priority "low" because they are squatting the Ceph issue namespace but follow a completely different workflow. 

Would it make sense to create a "Stable releases" project in http://tracker.ceph.com/ ?

Cheers

-- 
Loïc Dachary, Artisan Logiciel Libre


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

                 reply	other threads:[~2015-02-28 23:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=54F25488.6050703@dachary.org \
    --to=loic@dachary.org \
    --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.