DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jay Rolette <rolette@infinite.io>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Cc: "techboard@dpdk.org" <techboard@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Minutes of technical board meeting 2017-12-06
Date: Tue, 12 Dec 2017 12:30:11 -0600	[thread overview]
Message-ID: <CADNuJVod-=YZc8GGxCFBuY0d1uewN4ga-s7d5tYu4GjQaKEzfQ@mail.gmail.com> (raw)
In-Reply-To: <59AF69C657FD0841A61C55336867B5B0722026D2@IRSMSX103.ger.corp.intel.com>

On Tue, Dec 12, 2017 at 11:26 AM, Richardson, Bruce <
bruce.richardson@intel.com> wrote:


> Topic: Management of old patches in patchwork
> * Unanimous agreement that old patches should be rejected in patchwork
>   after a reasonable period, set initially at 3 releases (9 months).
> * After a release, all patches dated older than 3 releases previously,
>   e.g. after 17.11, any patches submitted before the release of 17.02,
>   will be marked as rejected and a mail reply sent to the appropriate
>   mailing list thread informing people of the same.
> * To have patches reconsidered for future inclusion, a new version of
>   the patches should be submitted to the mailing list.
>

Does this mean there is a commitment to act on submitted patches in a
timely manner? Maybe this is better now, but at least in the past, even
small patches to fix bugs would sit around with no action on them for 6+
months.

It's been a while since I submitted any patches, so if this isn't an issue
now, then nevermind :-)

Jay

  reply	other threads:[~2017-12-12 18:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-12 17:26 Richardson, Bruce
2017-12-12 18:30 ` Jay Rolette [this message]
2017-12-13  9:38   ` Bruce Richardson

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='CADNuJVod-=YZc8GGxCFBuY0d1uewN4ga-s7d5tYu4GjQaKEzfQ@mail.gmail.com' \
    --to=rolette@infinite.io \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=techboard@dpdk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).