Repository navigation
doc: reorg and cleanup - #59
Conversation
This is a significant update. * The document is restructured to have a more logical flow. * The LTS straw man is removed (it was just a straw man, after all, and it was causing confusion) * The supported platforms bit is simplified to better reflect reality. * Address breaking changes in the build * Clarify the release tagging and maintenance branching model The idea here is to simplify, clarify and define a branching model that is closer to reality. It's a significant change that will require additional review. The LTS straw man is removed entirely. It can be added back in as a separate document later on if necessary.
There was a problem hiding this comment.
in both node.js and io.js
Sounds like there is two in both :)
|
I personally like a lot of this more. IMO the entire maintenance thing should be much easier for people to understand than the previous LTS stuff. |
There was a problem hiding this comment.
Does this mean that patch level releases wouldn't be tagged? This seems contrary to what both projects currently do. See https://github.com/iojs/io.js/releases and https://github.com/joyent/node/releases
There was a problem hiding this comment.
Left that out for now because I wasn't clear on it. We can cut a release tag on every new semver-patch also
There was a problem hiding this comment.
In io.js we make pgp signed tags for every release.
There was a problem hiding this comment.
Ok, corrected in an additional commit.
|
@cjihrig does that look better after the additional commits? |
|
LGTM. I'd still like to see if others have comments. |
|
I think the updates look good. lgtm. |
|
Going to merge this but definitely keep the comments coming. |
This is a significant update.
after all, and it was causing confusion)
reality.
The idea here is to simplify, clarify and define a branching model that
is closer to reality. It's a significant change that will require
additional review.
The LTS straw man is removed entirely. It can be added back in as a
separate document later on if necessary.