From: Thomas Monjalon <thomas@monjalon.net>
To: "Iremonger, Bernard" <bernard.iremonger@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dpdk-dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] DPDK Release Status Meeting 28/05/2020
Date: Tue, 02 Jun 2020 16:35:18 +0200 [thread overview]
Message-ID: <1653442.0L77payyoi@thomas> (raw)
In-Reply-To: <093c8be7-0bf7-395b-ea7c-89c607ac0d4e@intel.com>
02/06/2020 16:23, Ferruh Yigit:
> On 6/2/2020 12:39 PM, Iremonger, Bernard wrote:
> > From: Ferruh Yigit
> >> * v20.08 dates:
> >> * Proposal/V1:Friday, 12 June 2020
> >
> > Is the merge deadline Friday, 3 July?
> >
> >> * -rc1:Wednesday, 8 July 2020
>
> Hi Bernard,
>
> I personally find having the distinction for "merge deadline" and '-rc1" is
> confusing. I prefer to follow only -rc1.
>
> The thing to consider is, if -rc1 is 8 July, and you are sending a new version
> of the patch on that day, 8 July, I think it is not surprising if the patch
> misses the -rc1.
> So patch should be at least a few days before the -rc1, to give enough time for
> it to be processed. Should we formalize that a few days as "merge deadline" and
> explicitly call that day, as said above I don't think so but I don't know what
> others think about it.
>
> Roughly, please send your last version of the patch at least 2 work days before
> the -rc1. @Thomas, what do you think, is it a fair measurement?
I won't directly reply about the numbers and commitment.
Yes we need to be strict on dates.
But about when is the last time to have something merged,
I would say it depends and it is based on best effort.
The sooner is the better :-)
prev parent reply other threads:[~2020-06-02 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 15:55 [dpdk-dev] DPDK Release Status Meeting 28/05/2020 Ferruh Yigit
2020-05-28 16:19 ` Stephen Hemminger
2020-05-28 17:54 ` Akhil Goyal
2020-06-02 11:39 ` Iremonger, Bernard
2020-06-02 14:23 ` Ferruh Yigit
2020-06-02 14:35 ` Thomas Monjalon [this message]
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=1653442.0L77payyoi@thomas \
--to=thomas@monjalon.net \
--cc=bernard.iremonger@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@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.