Keeping up with the backports

Keeping up with the backports

[Loic Dachary]

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

Hi Alistair & Jean-Charles,

Thanks a lot for volunteering to work on the backports !

I have good news: the backlog of backports is almost empty. New backports are being added every day and we are going to make sure they are handled on a weekly basis so that point releases can be published every month or so, if needed. To start small and learn as we make progress, I propose to mentor you on a given point release, starting with cherry-picking backports and preparing an integration branch as described at http://tracker.ceph.com/projects/ceph-releases/wiki/Wiki (which is linked from the http://tracker.ceph.com/projects/ceph-releases/ landing page). The idea is that once you feel confortable you can keep going on your own.

If you agree we can arrange an IRC meeting next week to bootstrap that. Since we have multiple stable releases in flight at any given time, it can conveniently be parallelized. If that's ok with you, Alistair could start with Firefly and Jean-Charles with Dumpling. 

Please let me know if you have any question :-)

Cheers
-- 
Loïc Dachary, Artisan Logiciel Libre


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

Re: Keeping up with the backports

[Loic Dachary]

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

Hi Andrey,

On 19/03/2015 15:53, Andrey Korolyov wrote:
> On Thu, Mar 19, 2015 at 5:44 PM, Loic Dachary <loic@dachary.org> wrote:
>> Hi Alistair & Jean-Charles,
>>
>> Thanks a lot for volunteering to work on the backports !
>>
>> I have good news: the backlog of backports is almost empty. New backports are being added every day and we are going to make sure they are handled on a weekly basis so that point releases can be published every month or so, if needed. To start small and learn as we make progress, I propose to mentor you on a given point release, starting with cherry-picking backports and preparing an integration branch as described at http://tracker.ceph.com/projects/ceph-releases/wiki/Wiki (which is linked from the http://tracker.ceph.com/projects/ceph-releases/ landing page). The idea is that once you feel confortable you can keep going on your own.
>>
>> If you agree we can arrange an IRC meeting next week to bootstrap that. Since we have multiple stable releases in flight at any given time, it can conveniently be parallelized. If that's ok with you, Alistair could start with Firefly and Jean-Charles with Dumpling.
>>
>> Please let me know if you have any question :-)
>>
>> Cheers
>> --
>> Loïc Dachary, Artisan Logiciel Libre
> 
> 
> 
> Hi Loic,
> 
> Sage said recently that dumpling will be a less likely target to
> receive backports in a near future, was the point changed since then?

Dumpling was published about 18 month ago and that was its expected life time. Therefore, yes, in theory Dumpling 0.67.12 ( http://tracker.ceph.com/issues/10560 ) is likely to be the last point release. It's however the first LTS to reach "end of life" and I guess we may have another one, in case an interesting backport shows up.

> Or Dumpling will be still maintained but only by a community effort?

If someone from the community is willing to make that commitment to Dumpling, I'll help her/him as much as I can. I also think it would make sense for the Ceph project to provide the technical infrastructure for that, but it's not a discussion we had yet. For instance say there are 15 interesting patches pending for Firefly in three years from now. The teuthology/package building/release publishing machinery for Firefly could be saved somewhere for the benefit of someone willing to revive them and publish a new Firefly version. 

It could be argued that it does not make sense to keep going after the end of life of a stable release. But it's not true in some cases, as can be seen for instance with qemu where a some release are packaged on so many patches that it looks like a new release. I guess Ceph will be facing that kind of challenges in the near future.

Cheers

> Thanks!
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


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