DPDK usage discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Luca Boccassi <bluca@debian.org>
Cc: Thomas Monjalon <thomas@monjalon.net>, dpdk-dev <dev@dpdk.org>,
	users@dpdk.org
Subject: Re: release schedule change proposal
Date: Mon, 15 Nov 2021 21:09:26 +0530	[thread overview]
Message-ID: <CALBAE1Nxai13TOuO0a7HXPQMka03PHeGRrmz2Pku81+MZM=pCQ@mail.gmail.com> (raw)
In-Reply-To: <7c5d07fd690dbde4a155ed476f4e6cee5fc4aed9.camel@debian.org>

On Mon, Nov 15, 2021 at 8:42 PM Luca Boccassi <bluca@debian.org> wrote:
>
> On Mon, 2021-11-15 at 15:58 +0100, Thomas Monjalon wrote:
> > For the last 5 years, DPDK was doing 4 releases per year,
> > in February, May, August and November (the LTS one):
> >       .02   .05   .08   .11 (LTS)
> >
> > This schedule has multiple issues:
> >       - clash with China's Spring Festival
> >       - too many rushes, impacting maintainers & testers
> >       - not much buffer, impacting proposal period
> >
> > I propose to switch to a new schedule with 3 releases per year:
> >       .03      .07      .11 (LTS)


+1


> >
> > New LTS branch would start at the same time of the year as before.
> > There would be one less intermediate release during spring/summer:
> > .05 and .08 intermediate releases would become a single .07.
> > I think it has almost no impact for the users.
> > This change could be done starting next year.
> >
> > In details, this is how we could extend some milestones:
> >
> >       ideal schedule so far (in 13 weeks):
> >               proposal deadline: 4
> >               rc1 - API freeze: 5
> >               rc2 - PMD features freeze: 2
> >               rc3 - app features freeze: 1
> >               rc4 - last chance to fix: 1
> >               release: 0
> >
> >       proposed schedule (in 17 weeks):
> >               proposal deadline: 4
> >               rc1 - API freeze: 7
> >               rc2 - PMD features freeze: 3
> >               rc3 - app features freeze: 1
> >               rc4 - more fixes: 1
> >               rc5 - last chance buffer: 1
> >               release: 0
> >
> > Opinions?
>
> We upload only LTS releases to Debian/Ubuntu, so as long as those stay
> the same as it is proposed here, no problem for us.
>
> --
> Kind regards,
> Luca Boccassi

  reply	other threads:[~2021-11-15 15:39 UTC|newest]

Thread overview: 9+ 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 [this message]
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
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='CALBAE1Nxai13TOuO0a7HXPQMka03PHeGRrmz2Pku81+MZM=pCQ@mail.gmail.com' \
    --to=jerinjacobk@gmail.com \
    --cc=bluca@debian.org \
    --cc=dev@dpdk.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).