Re: dumpling integration branch for v0.67.12 ready for QE

[Yuri Weinstein <yweinste@redhat.com>]

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.

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
--
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