2015-12-19 02:16, Wiles, Keith:
> On 12/18/15, 6:01 PM, "dev on behalf of Thomas Monjalon" <dev-bounces at
> dpdk.org on behalf of thomas.monjalon at 6wind.com> wrote:
>
> >2015-12-13 20:22, Thomas Monjalon:
> >> We need to define the deadlines for the next releases.
> >> During 2015, we were doing a release every 4 months.
> >> If we keep the same pace, the next releases would be:
> >> 2.3: end of March
> >> 2.4: end of July
> >> 2.5: end of November
> >>
> >> However, things move fast and it may be a bit long to wait 4 months for
> >> a feature. That's why I suggest to progressively shorten release terms:
> >> 2.3: end of March
> >> 2.4: mid July
> >> 2.5: end of October
> >> and continue with a release every 3 months:
> >> 2.6: end of January
> >> 2.7: end of April
> >> 2.8: end of July
> >> This planning would preserve some of the major holiday periods
> >> (February, May, August, December).
> >>
> >> The first period, for the first submission of a feature, was 2 months long.
> >> Then we had 2 other months to discuss, merge and fix.
> >> We should shorten only the first period.
> >>
> >> Anyway, the next deadlines should be unchanged:
> >> - January 31: end of first submission phase
> >> - March 31: release 2.3
> >>
> >> Opinions are welcome.
> >
> >It seems everybody agree with this new scheduling.
> >The web site will be updated accordingly:
> >http://dpdk.org/ml/archives/web/2015-December/000008.html
> >
> >There were some discussions to change the numbering scheme
> >and rename 2.3 to 16.04. The patch (with arguments) is welcome.
> >I won't do the patch myself because I don't care :)
> >
> >Another discussion was about having a long term support,
> >i.e. doing some backport maintenance during a given period for
> >some selected releases.
>
> I think we need to decide on the YY.MM.PP format then select
> the dates for release now. This way we have it out of the way.
>
> The date of the release is the first day of the month for the release.
>
> March 1st - 15th is 16.03 Patches for 16.03 are from now to Feb 15th
> Try to get the release out as close to the 1st as possible.
> This one is a short release.
> June 1st - 15th is 16.06 For 16.06 March 1st to May 15th
> Sept 1st - 15th is 16.09 For 16.09 June 1st to Aug 15th
> Dec 1st - 15th is 16.12 For 16.12 Sept 1st to Nov 15th.
>
> The 15th just before the release month is the deadline for patches, gives up
> 2 weeks before the release date and to the 15th of the release month to get
> the release out, but we should try for the 1st. The deadline is just a
> suggestion here or example, we can adjust it to something else.
>
> Tag 2.2.0 in the repo also as 15.12 plus I would suggest we tag it as LTS
> Long Term Support as well.
Hi Keith,
I'm confused. Have you read the proposal above and the patch above?
I add it here again to make it more visible:
http://dpdk.org/ml/archives/web/2015-December/000008.html
And I copy-paste here:
The release cycles are progressively shorten during 2016.
Release 16.04
Proposal deadline: January 31
Integration deadline: March 10
Release: April 7
Release 16.07
Proposal deadline: May 8
Integration deadline: June 16
Release: July 18
Release 16.11
Proposal deadline: August 28
Integration deadline: September 30
Release: November 2
Release 17.02
Release: February 1
Release 17.05
Release: May 2
Release 17.08
Release: August 1
Release 17.11
Release: November 2
