Re: Publishing development releases

[Loic Dachary <loic@dachary.org>]

Hi,

It looks like we have a majority in favor, let's do it :-)

I took the first round with the publication of 10.0.5. Our rotation schedule was updated to add 10.1.0 (the next development release) http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO#Whos-who and I set myself as a backup. If someone is willing to learn how to publish a dev release, I'll be happy to explain. It is now documented at http://tracker.ceph.com/projects/ceph-releases/wiki/HOWTO_publish_a_release. There is no doubt things are missing but they can be fixed / documented as we make progress.

Cheers

On 15/03/2016 10:13, Loic Dachary wrote:
> Hi Abhishek V, Abhishek L, Swami, Nathan, Gaurav, Rajat, Martin, Xiaoxi, Vicente,
> 
> A few weeks ago, 10.0.3 was tagged for release, but packages were not published and these packages were missed by the Ceph user base. We, the members of the Stable Releases team, got to thinking how we could help.
> 
> This led to an idea that was discussed on the mailing list[1] and during CDM[2]. Since we were already building packages as a side effect of running teuthology suites on OpenStack, this could be extended into a full-fledged release process that would:
> 
> 1. ensure that the community's demand for development releases is met
> 2. complement, not replace, the existing package publication workflow
> 3. be automated.
> 
> So I added a "release" subcommand to the ceph-workbench[3] tool we are already using to automate various backporting tasks. The new subcommand is included in the latest ceph-workbench release, and works like this:
> 
>              ceph-workbench release --suite buildpackages/any \
>                          --ceph jewel \
>                          --version 10.0.5 \
>                          --filter ubuntu_14.04,centos_7.2
> 
> When it completes the packages can be uploaded to a permanent mirror similar to downloads.ceph.com.
> 
> I believe we can commit to publish Ceph development releases with this process. The "release" subcommand is relatively small (around 300 lines of code) and there are integration tests to help with its maintenance. There are enough of us to rotate the release duties so that it does not become too much of a burden for anyone.
> 
> Since it's a decision that changes our focus and our workload, are you OK with adding this activity to the scope of our team?
> 
> Cheers
> 
> [1] (Un)Stable release team http://www.spinics.net/lists/ceph-devel/msg28887.html
> [2] publishing development and unsupported releases http://tracker.ceph.com/projects/ceph/wiki/CDM_02-MAR-2016
> [3] ceph-workbench release merge request http://ceph-workbench.dachary.org/root/ceph-workbench/merge_requests/43/diffs#9f3ebf1fc38506b66593397f3baac514d515c496_231_232

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