hammer is frozen

hammer is frozen

[Sage Weil]

I created the branch on Monday, but am traveling and forgot to send an 
email.  This means we're not merging new features until we have a handle 
on the testing and the QA results are looking good.

Specifically:

- There is a 'hammer' ceph.git branch.  Please target any bug fixes at 
  this.

- The 'next' branch is deleted for the time being (see above)

- Do not merge any new features to master; not yet.  It's too confusing 
  and we have enough work to do stabilizing things.

- There are still several pull requests open that are bug fixes and target 
  master that should get merged once they are tested, so we will probably 
  merge hammer and master together periodically to avoid doing all the 
  merged manually.  (Another reason not to merge any new code into master 
  that does not target hammer.)

- We're using the 'hammer' milestone on github to track what to pay 
  attention to.  Please help keep it in sync with the open pull 
  requests that are hammer-bound vs future work for infernalis.

If there is something exceptional that hasn't made it in yet and is 
low-risk, plea your case, but no promises.  Bribery in the form of fixes 
for open bugs can be effective.  :)

Thanks!
sage

RE: hammer is frozen

[Miyamae, Takeshi]

Hi Sage,

> If there is something exceptional that hasn't made it in yet and is low-risk,
> plea your case,

We would like to contribute our following code to the nearest stable release
Hammer, and we believe that our code has sufficiently low risk.

 mSHEC : multiple Shingled Erasure Code #3534
 https://github.com/ceph/ceph/pull/3534

One of the reasons why we think it has low risk is that we have already
finished extended tests shown below assuming a product use case.

 Test items done:
  * erasure code plugin I/F tests (TestErasureCodeShec.cc)
  * exhaustive parity layouts tests (TestErasureCodeShec_all.cc)
  * thread safety tests (TestErasureCodeShec_thread.cc)
  * tests on a real ceph cluster
     - pool creation/deletion
     - read/write
     - recovery (up to N multiple failures)

Another reason is that the code is just a plugin, which is completely
isolated from the core of Ceph and has no risks for users who do not
need to use it.

Best regards,
Takeshi Miyamae

-----Original Message-----
From: ceph-devel-owner@vger.kernel.org [mailto:ceph-devel-owner@vger.kernel.org] On Behalf Of Sage Weil
Sent: Thursday, February 5, 2015 5:51 AM
To: ceph-devel@vger.kernel.org
Subject: hammer is frozen

I created the branch on Monday, but am traveling and forgot to send an email.  This means we're not merging new features until we have a handle on the testing and the QA results are looking good.

Specifically:

- There is a 'hammer' ceph.git branch.  Please target any bug fixes at
  this.

- The 'next' branch is deleted for the time being (see above)

- Do not merge any new features to master; not yet.  It's too confusing
  and we have enough work to do stabilizing things.

- There are still several pull requests open that are bug fixes and target
  master that should get merged once they are tested, so we will probably
  merge hammer and master together periodically to avoid doing all the
  merged manually.  (Another reason not to merge any new code into master
  that does not target hammer.)

- We're using the 'hammer' milestone on github to track what to pay
  attention to.  Please help keep it in sync with the open pull
  requests that are hammer-bound vs future work for infernalis.

If there is something exceptional that hasn't made it in yet and is low-risk, plea your case, but no promises.  Bribery in the form of fixes for open bugs can be effective.  :)

Thanks!
sage
--
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

Re: hammer is frozen

[Loic Dachary]

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

Hi,

In my opinion this should have been merged: it was ready before the feature freeze.

Cheers

On 06/02/2015 13:25, Miyamae, Takeshi wrote:
> Hi Sage,
> 
>> If there is something exceptional that hasn't made it in yet and is low-risk,
>> plea your case,
> 
> We would like to contribute our following code to the nearest stable release
> Hammer, and we believe that our code has sufficiently low risk.
> 
>  mSHEC : multiple Shingled Erasure Code #3534
>  https://github.com/ceph/ceph/pull/3534
> 
> One of the reasons why we think it has low risk is that we have already
> finished extended tests shown below assuming a product use case.
> 
>  Test items done:
>   * erasure code plugin I/F tests (TestErasureCodeShec.cc)
>   * exhaustive parity layouts tests (TestErasureCodeShec_all.cc)
>   * thread safety tests (TestErasureCodeShec_thread.cc)
>   * tests on a real ceph cluster
>      - pool creation/deletion
>      - read/write
>      - recovery (up to N multiple failures)
> 
> Another reason is that the code is just a plugin, which is completely
> isolated from the core of Ceph and has no risks for users who do not
> need to use it.
> 
> Best regards,
> Takeshi Miyamae
> 
> -----Original Message-----
> From: ceph-devel-owner@vger.kernel.org [mailto:ceph-devel-owner@vger.kernel.org] On Behalf Of Sage Weil
> Sent: Thursday, February 5, 2015 5:51 AM
> To: ceph-devel@vger.kernel.org
> Subject: hammer is frozen
> 
> I created the branch on Monday, but am traveling and forgot to send an email.  This means we're not merging new features until we have a handle on the testing and the QA results are looking good.
> 
> Specifically:
> 
> - There is a 'hammer' ceph.git branch.  Please target any bug fixes at
>   this.
> 
> - The 'next' branch is deleted for the time being (see above)
> 
> - Do not merge any new features to master; not yet.  It's too confusing
>   and we have enough work to do stabilizing things.
> 
> - There are still several pull requests open that are bug fixes and target
>   master that should get merged once they are tested, so we will probably
>   merge hammer and master together periodically to avoid doing all the
>   merged manually.  (Another reason not to merge any new code into master
>   that does not target hammer.)
> 
> - We're using the 'hammer' milestone on github to track what to pay
>   attention to.  Please help keep it in sync with the open pull
>   requests that are hammer-bound vs future work for infernalis.
> 
> If there is something exceptional that hasn't made it in yet and is low-risk, plea your case, but no promises.  Bribery in the form of fixes for open bugs can be effective.  :)
> 
> Thanks!
> sage
> --
> 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
> --
> 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
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


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