All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Cutler <ncutler@suse.cz>
To: Alfredo Deza <adeza@redhat.com>, Abhishek <abhishek@suse.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>,
	ceph-devel-owner@vger.kernel.org
Subject: Re: Better anticipation for minor releases
Date: Fri, 2 Feb 2018 13:28:57 +0100	[thread overview]
Message-ID: <bfc90180-334b-519b-cf2c-db13b33abff2@suse.cz> (raw)
In-Reply-To: <CAC-Np1xbgABOgjDoYpPrDUvX7hOn3U-AD-YF-LpRsbjAfEPi6g@mail.gmail.com>

On 02/02/2018 01:05 PM, Alfredo Deza wrote:
>> If we approximately stop accepting new PRs at the third week, ask leads at
>> beginning of week 4 and go through only critical PRs for week 4; and go to
>> QE in week5,6 we might be able to somewhat get to a more scheduled minor
>> releases.
> 
> This might be a bit hard to deal with, how do you prevent a PR from
> getting merged? I've seen several times PRs getting merged at the last
> minute,
> with little to no testing, and breaking a release :( It hasn't
> happened much lately, but I don't know of a way to block all PRs for a
> period of time

Do we have a way of releasing a given SHA1 (which has passed QE) even 
when additional PRs have been merged on top of it?

IIRC in the past we could only release the tip of the named (jewel, 
luminous) branch. That does indeed create a risk of PRs getting merged 
post-QE and inadvertently finding their way into a release.

Nathan

  reply	other threads:[~2018-02-02 12:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-31 17:46 Better anticipation for minor releases Alfredo Deza
2018-01-31 19:25 ` Abhishek
2018-01-31 19:35   ` Ken Dreyer
2018-02-02 12:05   ` Alfredo Deza
2018-02-02 12:28     ` Nathan Cutler [this message]
2018-02-02 17:15       ` Ken Dreyer
2018-02-02 19:55         ` Robin H. Johnson
2018-02-02 20:15           ` Vasu Kulkarni
2018-02-02 21:35           ` Nathan Cutler
2018-02-02 21:52             ` Robin H. Johnson
2018-02-05 15:28             ` Andrew Schoen
2018-02-05 15:50               ` Sage Weil
2018-02-05 16:22                 ` Ken Dreyer
2018-02-05 16:30                   ` Sage Weil
2018-02-05 21:20                     ` Nathan Cutler
2018-02-05 21:32                       ` Yuri Weinstein
2018-02-05 21:45                       ` Vasu Kulkarni

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=bfc90180-334b-519b-cf2c-db13b33abff2@suse.cz \
    --to=ncutler@suse.cz \
    --cc=abhishek@suse.com \
    --cc=adeza@redhat.com \
    --cc=ceph-devel-owner@vger.kernel.org \
    --cc=ceph-devel@vger.kernel.org \
    /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.