Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Four releases a year on known dates (within reason, weekends, blockers, etc.).
  • Everything merged to master at all times is intended and ready to be included in the next scheduled release.  No or minimal cherry-picking.
  • Each release has a fixed and well known feature-freeze date. Features may be targetted for releases, but no promises are made of features being included unless they have been merged to master by that date.
  • Merging earlier rather than later in the merge window is to be encouraged!
  • After the feature freeze date only fixes intended for the release should be merged to master until the next feature window opens. Aside from any release-specific commits, the release branch will be kept in sync with master.
  • All fixes merged to master after the feature-freeze date should be made in accordance with the Bug Priority Guidelines
  • One release a year is designated a long-term / extended support version -
    • Only this release has a full NetCAT process, and subsequently a much shorter (month less) merge window to accommodate it (and because the emphasis for this release should be on fully stabilising features added in the previous 3 releases).
    • For 9 months of the year that means that people have a choice of two downloads (need to consider how to describe that, and what if any infrastructure concerns that brings?).  NetBeans 11.0 remains available until April 2020.
    • Minimal serious bug fixes might be backported to the LTS release and pushed via UC, taking into account the Bug Priority Guidelines (critical or blocker affecting significant users?) These should be done on the relevant release branch.
    • Users needing features should be encouraged on to the faster release train, and help test those features before next LTS.
    • Major version number is incremented for LTS.  So NetBeans 12.0 would be in April 2020.  Perhaps counter-intuitively the major version number would be increased for the versions with least new features. (Consider NetBeans 11.1 equivalent to NetBeans 11 feature update 1?)

Schedule

released. 11
DateReleaseDateDescription

NetBeans 11.1
NetBeans 12.1

June 15th


Feature freeze. Merge window closes. Only fixes intended for next release to be merged into master.
Release branch xx<version>.1 created and beta build(s) made available.  NetCAT lite???
July 7th
NB xx<version>.1 voting candidate created and release vote commences.
July 15thNB xx

NetBeans 11.1


NetBeans

12.1

NB <version>.1 released.2
NetBeans 12.2
July 21st


NB xx<version>.2 merge window opens.
September 15th

Feature freeze. Merge window closes.
Release branch xx<version>.2 created and beta build(s) made available.

October 7th
NB xx<version>.2 voting candidate created and release vote commences.
October 15th

NetBeans 11.2
NetBeans 12.2

NB <version>NB xx.2 released.
October 21st
NB xx<version>.3 merge window opens.NetBeans 11.3
NetBeans 12.3
December 15th

Feature freeze. Merge window closes.
Release branch xx<version>.3 created and beta build(s) made available.

January 7th
NB xx<version>.3 voting candidate created and release vote commences.
January 15th

NetBeans 11.3
NetBeans 12.3

NB <version>NB xx.3 released. (Start NetCAT with this release here???)
January 21st
NB xx<version+11>.0 merge window opens.
NetCAT announced and signups begin.
NetBeans 12.0
NetBeans 13.0
LTS
February 15th
Feature freeze. Merge window closes.
Release branch xx<version+11>.0 created and beta build(s) made available.
NetCAT test spec review starts.
February 21st
NetCAT testing phase starts.
March 21st
NetCAT testing ends.
NetCAT community acceptance vote.
April 7th
NB xx<version+11>.0 voting candidate created and release vote commences.
April 15thNB xx+1.0

LTS

released.

NetBeans 12.

1

0
NetBeans 13.

1

0

NB <version+1>.0 LTS released.
April 21st

NB xx<version+11>.1 merge window openopens.

GOTO 10

NB. The dates here are deliberately mid-month, two weeks after previously suggested.  Because no-one wants to do a release on New Years Eve, and it potentially gives a little more leeway in releasing / testing with JDK releases?

...