All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Yuri Weinstein <yweinste@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: dumpling integration branch for v0.67.12 ready for QE
Date: Tue, 10 Feb 2015 18:22:58 +0100	[thread overview]
Message-ID: <54DA3E72.9010600@dachary.org> (raw)
In-Reply-To: <54483038.14900677.1423588756901.JavaMail.zimbra@redhat.com>

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



On 10/02/2015 18:19, Yuri Weinstein wrote:> 
> Loic,
> 
> The only difference between options if we run suits on merged dumpling vs dumpling-backports first - is time.
> We will have to run suites on the final branch after the merge anyway.

Could you explain why ? After merging dumpling and dumpling-backports will be exactly the same.

> 
> Unless I hear otherwise, I will schedule suites to run on dumpling-backports first (as you are suggesting, with higher priority) and then assuming that we resolved all issues, we will run on the dumpling merged. 
> 
> Sage, pls correct if this is not what has to be done.
> 
> 
> Thx
> YuriW
> 
> ----- Original Message -----
> From: "Loic Dachary" <loic@dachary.org>
> To: "Yuri Weinstein" <yweinste@redhat.com>
> Cc: "Ceph Development" <ceph-devel@vger.kernel.org>
> Sent: Tuesday, February 10, 2015 9:05:31 AM
> Subject: dumpling integration branch for v0.67.12 ready for QE
> 
> Hi Yuri,
> 
> The dumpling integration branch for v0.67.12 as found at https://github.com/ceph/ceph/commits/dumpling-backports has been approved by Yehuda, Josh and Sam and is ready for QE. 
> 
> For the record, the head is https://github.com/ceph/ceph/commit/3944c77c404c4a05886fe8276d5d0dd7e4f20410
> 
> I think it would be best for the QE tests to use the dumpling-backports. The alternative would be to merge dumpling-backports into dumpling. However, since testing may take a long time and require more patches, it probably is better to not do that iterative process on the dumpling branch itself. As it is now, there already are a number of commits in the dumpling branch that should really be in the dumpling-backports: they do not belong to v0.67.11 and are going to be released in v0.67.12. In the future though, the dumpling branch will only receive commits that have been carefully tested and all the integration work will be on the dumpling-backports branch exclusively. So that third parties do not have to worry that the dumpling branch contains commits that have not been tested yet.
> 
> Cheers
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


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

  reply	other threads:[~2015-02-10 17:23 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-10 17:05 dumpling integration branch for v0.67.12 ready for QE Loic Dachary
2015-02-10 17:19 ` Yuri Weinstein
2015-02-10 17:22   ` Loic Dachary [this message]
2015-02-10 17:29     ` Yuri Weinstein
2015-02-10 18:04       ` Loic Dachary
2015-02-10 18:25         ` Gregory Farnum
2015-02-10 18:33           ` Loic Dachary
2015-02-10 18:40             ` Gregory Farnum
2015-02-10 18:37           ` Sage Weil
2015-02-10 19:06             ` Loic Dachary
2015-02-10 19:11               ` Yuri Weinstein
2015-02-10 19:15                 ` Loic Dachary
2015-02-10 17:31     ` Gregory Farnum
2015-02-11 22:24 ` Yuri Weinstein
2015-02-11 22:48   ` Loic Dachary
2015-02-12  0:29   ` Josh Durgin
2015-02-12 22:06   ` Yuri Weinstein
2015-02-12 22:17     ` Loic Dachary
2015-02-18 17:38       ` Yuri Weinstein
2015-02-18 17:54         ` Samuel Just
2015-02-18 17:56         ` Loic Dachary
2015-02-18 18:25           ` Josh Durgin
2015-02-26  0:18         ` Yuri Weinstein
2015-02-26  1:35           ` Loic Dachary
2015-02-12 22: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=54DA3E72.9010600@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    --cc=yweinste@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.