All of lore.kernel.org
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Nathan Cutler <ncutler@suse.cz>,
	Abhishek L <abhishek.lekshmanan@gmail.com>,
	Abhishek Varshney <abhishek.varshney@flipkart.com>,
	"Chen, Xiaoxi" <xiaoxi.chen@intel.com>,
	Gaurav Bafna <bafnag@gmail.com>,
	Wei-Chung Cheng <freeze.vicente.cheng@gmail.com>,
	Martin Palma <martin@palma.bz>, Chris Jones <cjones@cloudm2.com>,
	M Ranga Swami Reddy <swamireddy@gmail.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: (Un)Stable release team
Date: Fri, 26 Feb 2016 14:41:58 +0700	[thread overview]
Message-ID: <56D001C6.5080804@dachary.org> (raw)

Hi,

It's a quiet time in the small world of the stable release team, ideal for mentoring the new members who generously answered our call for participation. Welcome to Chen Xiaoxi, Gaurav Bafna, Wei-Chung Cheng, Martin Palma and Chris Jones :-)

I propose that we take advantage of the next few weeks to expand our scope in two ways: 

* test Ceph development versions as well as stable versions
* publish packages for Ceph development versions

Testing Ceph development versions is actually less work than with stable versions because the developers run a lot of tests already and fix problems on a daily basis. Our help would likely be needed with a few teuthology suite runs right before the development release is published, once a month. But the development versions tend to be more frequent, therefore it will probably be as much work as for a stable release, overall. The workflow would be revisited: there is no cherry-picking. Instead, bug fixes must be against the jewel branch or whatever branch will be the upcoming stable. And this branch is merged back into master on a regular basis (i.e. more frequently than the development releases).

As you may have noticed, no packages were published for the 10.0.3 development release and that's where we could make a real difference. This would be an entirely new part of our workflow, but also an exciting one because it's the last missing piece of the puzzle. Once we are able to publish usable packages for development releases, nothing is stopping us to do the same for stable releases. It's a lot easier than it seems since the packages are already built for the teuthology jobs. All we need is a public space to archive them and sign them. This is not mutually exclusive with the current package publication workflow, it would be a community driven alternative that is much needed in some cases.

Of course, this is easier said than done :-) What do you think ? Are there other important work that we should try to accomplish instead ? Things that would benefit Ceph users and developers more ?

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

             reply	other threads:[~2016-02-26  7:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-26  7:41 Loic Dachary [this message]
2016-02-26  8:12 ` (Un)Stable release team Abhishek Varshney
2016-02-26 10:11   ` Loic Dachary
2016-02-29  7:53   ` Loic Dachary
2016-02-29 11:44     ` Loic Dachary
2016-02-29 12:46       ` Abhishek Varshney
2016-02-29 14:47         ` Loic Dachary
2016-02-26 14:09 ` M Ranga Swami Reddy
2016-03-05  1:23 ` Loic Dachary
2016-03-07 13:15   ` Loic Dachary
2016-03-07 13:25     ` Martin Palma

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=56D001C6.5080804@dachary.org \
    --to=loic@dachary.org \
    --cc=abhishek.lekshmanan@gmail.com \
    --cc=abhishek.varshney@flipkart.com \
    --cc=bafnag@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=cjones@cloudm2.com \
    --cc=freeze.vicente.cheng@gmail.com \
    --cc=martin@palma.bz \
    --cc=ncutler@suse.cz \
    --cc=swamireddy@gmail.com \
    --cc=xiaoxi.chen@intel.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.