From: Shepard Siegel <shepard.siegel@atomicrules.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>,
users@dpdk.org, david.marchand@redhat.com,
ferruh.yigit@intel.com, andrew.rybchenko@oktetlabs.ru,
qi.z.zhang@intel.com, jerinj@marvell.com, rasland@nvidia.com,
maxime.coquelin@redhat.com, gakhil@marvell.com,
bluca@debian.org, ktraynor@redhat.com,
bruce.richardson@intel.com, mdr@ashroe.eu,
konstantin.ananyev@intel.com, olivier.matz@6wind.com,
Honnappa.Nagarahalli@arm.com, hemant.agrawal@nxp.com,
aconole@redhat.com, ajit.khaparde@broadcom.com
Subject: Re: release schedule change proposal
Date: Mon, 15 Nov 2021 12:15:21 -0500 [thread overview]
Message-ID: <CAMMLSKA-jTG-1EhvDZo82MknxzvaH5d3OZ3qQ=hGJ-sStFd-YQ@mail.gmail.com> (raw)
In-Reply-To: <20211115085821.0f89cc96@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 427 bytes --]
> Opinions?
Atomic Rules has been releasing our Arkville product in lockstep with DPDK
for the past 19 quarters. Our FPGA solution has the added burden of testing
with async releases of FPGA vendor CAD tools. Although we have gotten used
to the quarterly cadence, for the reasons given by Thomas and others,
Atomic Rules supports the move to a three release per year schedule.
Shepard Siegel, CTO and Founder
atomicrules.com
[-- Attachment #2: Type: text/html, Size: 595 bytes --]
next prev parent reply other threads:[~2021-11-15 17:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 14:58 Thomas Monjalon
2021-11-15 15:11 ` Luca Boccassi
2021-11-15 15:39 ` Jerin Jacob
2021-11-15 16:04 ` Asaf Penso
2021-11-15 16:06 ` Kevin Traynor
2021-11-19 13:48 ` Flavio Leitner
2021-11-19 15:22 ` Ilya Maximets
2021-11-15 16:58 ` Stephen Hemminger
2021-11-15 17:15 ` Shepard Siegel [this message]
2021-11-18 4:08 ` Ajit Khaparde
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='CAMMLSKA-jTG-1EhvDZo82MknxzvaH5d3OZ3qQ=hGJ-sStFd-YQ@mail.gmail.com' \
--to=shepard.siegel@atomicrules.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=aconole@redhat.com \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=konstantin.ananyev@intel.com \
--cc=ktraynor@redhat.com \
--cc=maxime.coquelin@redhat.com \
--cc=mdr@ashroe.eu \
--cc=olivier.matz@6wind.com \
--cc=qi.z.zhang@intel.com \
--cc=rasland@nvidia.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
--cc=users@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).