Skip to content

doc: add releases document detail release cycle

Rodrigo Muino Tomonari requested to merge github/fork/chrisdickinson/add-release-doc into v1.x

Add a release cycle document covering use of semver, LTS releases, support releases, train system, and git branching model.

Topics I am seeking feedback on: Everything generally, but in particular:

  • Until async-listener is released, a weekly release cycle is going to create epic amounts of work for anyone instrumenting io.js. Do we want to downsample the "stable" releases? Or do we want to wait to implement this until we have a proof of concept for async-listener?
  • Distribution linking. These are essentially human branch names as proposed, but I'm not sure in what form they should be best made available to downstream packagers.
  • Semver: I'm still on the fence about the "major bumps except for NAN" bit, but I'm happy to adopt that and see how it fares.
  • Git branching: this puts us back on master, and makes the vN.x branches a pre-release phenomenon – that is, as v2.0.0 gets released, a v1.x branch is cut and master becomes the work on the v2 major version.
  • Is this too complicated?

cc @iojs/tc @iojs/build @iojs/collaborators @domenic @wraithan

Merge request reports