DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] DPDK Release Status Meeting 16/5/2019
@ 2019-05-16 17:02 Ferruh Yigit
  2019-05-16 21:43 ` Luca Boccassi
  0 siblings, 1 reply; 4+ messages in thread
From: Ferruh Yigit @ 2019-05-16 17:02 UTC (permalink / raw)
  To: dpdk-dev
  Cc: John McNamara, Stokes, Ian, Thomas Monjalon, Jerin Jacob, Akhil,
	Goyal, Cristian Dumitrescu, Qian Xu, Yongseok Koh,
	Maxime Coquelin, Qi Zhang, Shahaf Shuler, Pablo de Lara

Minutes 16 May 2019
-------------------

Agenda:
* Release Dates
* Subtrees
* OvS
* Conferences
* Opens


Participants:
* Debian/Microsoft
* Intel
* Marvell
* Mellanox
* NXP
* RedHat


Release Dates
-------------

* v19.05 is released on Tuesday, 14 May
  * https://mails.dpdk.org/archives/dev/2019-May/132193.html
  * https://core.dpdk.org/download/

* v19.08 dates:
  * Proposal/V1               Monday 03 June   2019  
  * Integration/Merge/RC1     Monday 01 July   2019  
  * Release                   Thurs  01 August 2019

  * Schedule updated on roadmap page:
    https://core.dpdk.org/roadmap/

  * Reminder to send roadmaps for the release, it helps planning
    * Intel is planning to send roadmap for next week
    * Marvell will have new PMDs and will provide a roadmap

* v19.11 proposed dates, *please comment*,
  * Proposal/V1               Friday 06 September 2019
  * Integration/Merge/RC1     Friday 11 October   2019
  * Release                   Friday 08 November  2019

  * Constrains:
    * PRC holidays on October 1-7 inclusive, rc1 shouldn't overlap with it
    * US DPDK Summit on mid November, better to have release before summit


Subtrees
--------

* main
* next-net
* next-virtio
* next-crypto
* next-eventdev
* next-pipeline
* next-qos
  * Starting new release cycle
  * Reminder that proposal deadline is less than three weeks away
  * We had a better release notes this release, please include release
    notes updates within the feature patchset

* Stable trees
  * 18.11.2 is in progress
    * Will have the -rc on 21 May
    * 11 June is the target release day
    * We should get test report from more companies
      Planning to not block the release to wait more testing,
      please provide tests results in defined window
  * Can be good to build contact information of the involved testers from
    various companies, for faster/better communication, if you are doing LTS
    testing please reach out to Kevin or Luca


OvS
---

* Will be testing 18.11.2 which will have known bug fixes


Conferences
-----------

* DPDK Userspace summit: DPDK Userspace · Sept. 19-20, 2019
  https://www.dpdk.org/event/dpdk-userspace-bordeaux/
  * CFP Opens: Monday, April 29
  * CFP Closes: Friday, May 24

  * Reminder of the short CFP duration and deadline is approaching

* US summit dates are not fixed yet


Opens
-----

* Akhil can able to spend more time on crypto sub-tree and there is a potential
  co-maintainer from Arm, can close this open for now

* There still some coverity defects open, some of them are from Marvell, NXP
  drivers, it would be great to close them


DPDK Release Status Meetings
============================

The DPDK Release Status Meeting is intended for DPDK Committers to discuss
the status of the master tree and sub-trees, and for project managers to
track progress or milestone dates.

The meeting occurs on Thursdays at 8:30 UTC. If you wish to attend just
send an email to "John McNamara <john.mcnamara@intel.com>" for the invite.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dpdk-dev] DPDK Release Status Meeting 16/5/2019
  2019-05-16 17:02 [dpdk-dev] DPDK Release Status Meeting 16/5/2019 Ferruh Yigit
@ 2019-05-16 21:43 ` Luca Boccassi
  2019-05-17  8:43   ` Thomas Monjalon
  0 siblings, 1 reply; 4+ messages in thread
From: Luca Boccassi @ 2019-05-16 21:43 UTC (permalink / raw)
  To: Ferruh Yigit, dpdk-dev; +Cc: John McNamara, Thomas Monjalon

On Thu, 2019-05-16 at 18:02 +0100, Ferruh Yigit wrote:
>   * Can be good to build contact information of the involved testers
> from
>     various companies, for faster/better communication, if you are
> doing LTS
>     testing please reach out to Kevin or Luca

Shall we add a list to the MAINTAINERS file? With the consent of each
person of course

-- 
Kind regards,
Luca Boccassi

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dpdk-dev] DPDK Release Status Meeting 16/5/2019
  2019-05-16 21:43 ` Luca Boccassi
@ 2019-05-17  8:43   ` Thomas Monjalon
  2019-05-17 10:16     ` Luca Boccassi
  0 siblings, 1 reply; 4+ messages in thread
From: Thomas Monjalon @ 2019-05-17  8:43 UTC (permalink / raw)
  To: Luca Boccassi; +Cc: Ferruh Yigit, dpdk-dev, John McNamara

16/05/2019 23:43, Luca Boccassi:
> On Thu, 2019-05-16 at 18:02 +0100, Ferruh Yigit wrote:
> >   * Can be good to build contact information of the involved testers
> > from
> >     various companies, for faster/better communication, if you are
> > doing LTS
> >     testing please reach out to Kevin or Luca
> 
> Shall we add a list to the MAINTAINERS file? With the consent of each
> person of course

Isn't it enough to have them Cc of mails and extend this list over time?
Or we can have a mailing list where they can register?



^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [dpdk-dev] DPDK Release Status Meeting 16/5/2019
  2019-05-17  8:43   ` Thomas Monjalon
@ 2019-05-17 10:16     ` Luca Boccassi
  0 siblings, 0 replies; 4+ messages in thread
From: Luca Boccassi @ 2019-05-17 10:16 UTC (permalink / raw)
  To: Thomas Monjalon; +Cc: Ferruh Yigit, dpdk-dev, John McNamara

On Fri, 2019-05-17 at 10:43 +0200, Thomas Monjalon wrote:
> 16/05/2019 23:43, Luca Boccassi:
> > On Thu, 2019-05-16 at 18:02 +0100, Ferruh Yigit wrote:
> > >   * Can be good to build contact information of the involved
> > > testers
> > > from
> > >     various companies, for faster/better communication, if you
> > > are
> > > doing LTS
> > >     testing please reach out to Kevin or Luca
> > 
> > Shall we add a list to the MAINTAINERS file? With the consent of
> > each
> > person of course
> 
> Isn't it enough to have them Cc of mails and extend this list over
> time?
> Or we can have a mailing list where they can register?

Sure, it's just to keep track it's easier to have it written somewhere
I think, so people can add/remove themselves, etc etc
A dedicated mailing list could work too

-- 
Kind regards,
Luca Boccassi

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2019-05-17 10:16 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-05-16 17:02 [dpdk-dev] DPDK Release Status Meeting 16/5/2019 Ferruh Yigit
2019-05-16 21:43 ` Luca Boccassi
2019-05-17  8:43   ` Thomas Monjalon
2019-05-17 10:16     ` Luca Boccassi

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).