From: Nathan Cutler <ncutler@suse.cz>
To: Loic Dachary <loic@dachary.org>,
Abhishek L <abhishek.lekshmanan@gmail.com>,
Abhishek Varshney <abhishek.varshney@flipkart.com>,
Martin Palma <martin@palma.bz>,
"Chen, Xiaoxi" <xiaoxchen@ebay.com>,
Vicente Cheng <freeze.bilsted@gmail.com>,
Gaurav Bafna <bafnag@gmail.com>,
Rajat Garg <rajatgarg.iitr@gmail.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Publishing development releases
Date: Tue, 15 Mar 2016 21:31:48 +0100 [thread overview]
Message-ID: <56E87134.6060206@suse.cz> (raw)
In-Reply-To: <56E7D22E.2060701@dachary.org>
Hi Loic:
I, too, think this is a good idea and am willing to accept the extra
workload.
Nathan
On 03/15/2016 10:13 AM, 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
>
--
Nathan Cutler
Software Engineer Distributed Storage
SUSE LINUX, s.r.o.
Tel.: +420 284 084 037
next prev parent reply other threads:[~2016-03-15 20:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-15 9:13 Publishing development releases Loic Dachary
2016-03-15 20:08 ` Martin Palma
2016-03-15 20:31 ` Nathan Cutler [this message]
[not found] ` <CAHDn051vzYxzqVUT=4KQc0FBwZK4C-XEBCRsw4+BihCTkvGORQ@mail.gmail.com>
2016-03-16 7:30 ` Loic Dachary
2016-03-16 8:43 ` Abhishek Lekshmanan
[not found] ` <CAP3mxSzuZyQ1038kO0-STJ-DUvph21aMa_8M1fWDMzSZJRyUjQ@mail.gmail.com>
2016-03-16 9:57 ` Abhishek Varshney
2016-03-16 10:22 ` M Ranga Swami Reddy
2016-03-16 13:20 ` Loic Dachary
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=56E87134.6060206@suse.cz \
--to=ncutler@suse.cz \
--cc=abhishek.lekshmanan@gmail.com \
--cc=abhishek.varshney@flipkart.com \
--cc=bafnag@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=freeze.bilsted@gmail.com \
--cc=loic@dachary.org \
--cc=martin@palma.bz \
--cc=rajatgarg.iitr@gmail.com \
--cc=xiaoxchen@ebay.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.