Versions Compared

Old Version 5

changes.mady.by.user Matei Zaharia

Saved on

compared with

New Version 6

changes.mady.by.user Reynold Xin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Minor -> Feature

...

Each Spark release will be versioned:
[MAJOR].[MINORFEATURE].[MAINTENANCE]

MAJOR: All releases with the same major version number will have API compatibility, defined as [1]. Major version numbers will remain stable over long periods of time. For instance, 1.X.Y may last 1 year or more.

MINORFEATURE: Minor Feature releases will typically contain new features, improvements, and improvementsbug fixes. The target frequency for minor feature releases is every 3-4 months. One change we'd like to make is to announce fixed release dates and merge windows for each release, to facilitate coordination. Each minorfeature release will have a merge window where new patches can be merged, a QA window when only fixes can be merged, then a final period where voting occurs on release candidates. These windows will be announced immediately after the previous minor feature release to give people plenty of time, and over time, we might make the whole release process more regular (similar to Ubuntu). The current merge window is listed here.

MAINTENANCE: Maintenance releases will occur more frequently and depend on specific patches introduced (e.g. bug fixes) and their urgency. In general these releases are designed to patch bugs. However, higher level libraries may introduce small features, such as a new algorithm, provided they are entirely additive and isolated from existing code paths. Spark core may not introduce any features.

...