From: Yuri Weinstein <yweinste@redhat.com>
To: Loic Dachary <loic@dachary.org>
Cc: Sage Weil <sweil@redhat.com>,
Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: hammer tasks in http://tracker.ceph.com/projects/ceph-releases
Date: Sun, 22 Mar 2015 12:16:45 -0400 (EDT) [thread overview]
Message-ID: <1042516820.1185244.1427041005119.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <550E832E.6040004@dachary.org>
Loic, I think the idea was to do more process driven approach for releasing hammer, e.g. keep track of suites vs. results and open issues, so we can have a high level view on status at any time before the final cut day.
Do you have any suggestions or objections?
Thx
YuriW
----- Original Message -----
From: "Loic Dachary" <loic@dachary.org>
To: "Sage Weil" <sweil@redhat.com>
Cc: "Ceph Development" <ceph-devel@vger.kernel.org>
Sent: Sunday, March 22, 2015 1:54:06 AM
Subject: hammer tasks in http://tracker.ceph.com/projects/ceph-releases
Hi Sage,
You have created a few hammer related tasks at http://tracker.ceph.com/projects/ceph-releases/issues . What did you have in mind ?
Cheers
--
Loïc Dachary, Artisan Logiciel Libre
--
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:[~2015-03-22 17:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-22 8:54 hammer tasks in http://tracker.ceph.com/projects/ceph-releases Loic Dachary
2015-03-22 16:16 ` Yuri Weinstein [this message]
2015-03-22 23:50 ` Loic Dachary
2015-03-23 0:35 ` Loic Dachary
2015-03-23 15:09 ` Yuri Weinstein
2015-03-23 15:40 ` Loic Dachary
2015-03-23 15:44 ` Yuri Weinstein
2015-03-23 16:10 ` Loic Dachary
2015-03-23 16:27 ` Yuri Weinstein
2015-03-23 17:09 ` 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=1042516820.1185244.1427041005119.JavaMail.zimbra@redhat.com \
--to=yweinste@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=loic@dachary.org \
--cc=sweil@redhat.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.