DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: John McNamara <john.mcnamara@intel.com>
Subject: [dpdk-dev] Reviewathon
Date: Tue, 26 Jun 2018 10:04:40 +0100	[thread overview]
Message-ID: <a0b8ae23-4272-2fb6-66d8-1aed0ffa1147@intel.com> (raw)
In-Reply-To: <B27915DBBA3421428155699D51E4CFE23F37DE55@IRSMSX103.ger.corp.intel.com>

On 6/22/2018 1:13 PM, dev-bounces@dpdk.org wrote:
> DPDK Release Status Meeting 21/07/2018
> ======================================
> 
> Minutes from the weekly DPDK Release Status Meeting.

<...>

> Reviewathon
> -----------
> 
> * We plan a Community Reviewathon, next Tuesday 26th June.
> * Community will co-ordinate on IRC.
> * Look for announcement of dev mailing list.

As mentioned above this is planned for Tuesday 26th June.

The target is consume the patch backlog [1] as a community effort.


One thing we can think of is everybody attending review event join to dpdk irc
channel [1] which makes easier to communicate and reduces the communicating
related delay.

More comments are welcome for more efficient review event.


[1]
https://patches.dpdk.org/project/dpdk/list/


[2]
IRC freenode #dpdk-board
web client: https://webchat.freenode.net/

  reply	other threads:[~2018-06-26  9:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22 12:13 [dpdk-dev] DPDK Release Status Meeting 21/07/2018 Mcnamara, John
2018-06-26  9:04 ` Ferruh Yigit [this message]
2018-06-28  2:32   ` [dpdk-dev] Reviewathon Dan Gora
2018-06-28  8:59     ` Ferruh Yigit

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=a0b8ae23-4272-2fb6-66d8-1aed0ffa1147@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@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 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).