-
Notifications
You must be signed in to change notification settings - Fork 29.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc: change references to Stable to Current #6318
Conversation
LGTM |
/cc @nodejs/ctc |
I think changelog-maker will need an update too if I am remembering correctly |
From my comment in nodejs/nodejs.org#669
edit: I'm making a checklist in the top comment. Other collaborators please feel free to edit my comment and add more to the list |
@evanlucas afaik changelog maker is agnostic to release lines. The title of the changelog is always made manually afaik |
It breaks https://github.com/rvagg/changelog-maker/blob/master/groups.js#L19 (the --filter-release flag) |
PR has come in at a first pass to updating the website nodejs/nodejs.org#672 |
PR for changelog-maker: nodejs/changelog-maker#38 |
We do? |
There was another thread where there seemed to be consensus. Tbqh the
language is written for the commit if it lands. I copied it over to the PR.
I should have likely switched to more democratic language in the issue.
|
I have voiced my concerns at nodejs/nodejs.org#669 (comment) We need to make sure we give the large changes more time and not just cram them in before breaking releases... Speaking of which, this doesn't actually have to be done in a breaking release at all. I'd rather everyone be good with it and change it afterwards than not. |
This probably needs CTC approval? |
@evanlucas at the very least, I think. |
Thinking about this more in nodejs/nodejs.org#669 (comment)
|
Getting ctc review and encouraging input from the collaborators is exactly why this PR was opened :-) |
@Fishrock123 wrote:
@nodejs/evangelism @nodejs/website |
CTC should weigh in but it would be good to have the website change ready On Saturday, April 23, 2016, Rich Trott notifications@github.com wrote:
|
Need to know today if we're going to use the new naming for v6 |
@@ -187,7 +187,7 @@ Jenkins collects the artifacts from the builds, allowing you to download and ins | |||
|
|||
Once you have produced builds that you're happy with, create a new tag. By waiting until this stage to create tags, you can discard a proposed release if something goes wrong or additional commits are required. Once you have created a tag and pushed it to GitHub, you ***should not*** delete and re-tag. If you make a mistake after tagging then you'll have to version-bump and start again and count that tag/version as lost. | |||
|
|||
Tag summaries have a predictable format, look at a recent tag to see, `git tag -v v5.3.0`. The message should look something like `2015-12-16 Node.js v5.3.0 (Stable) Release`. | |||
Tag summaries have a predictable format, look at a recent tag to see, `git tag -v v6.0.0`. The message should look something like `2016-4-26 Node.js v6.0.0 (Current) Release`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2016-04-26
(note the 0
).
This does LGTM (with a nit). The only concern that I have here is that we would actually have LTS, Current, Maintenance, and Stable, at least in the changelog. We should make sure that the renaming is clear and that people can look up what did |
LGTM with @ChALkeR's nit addressed |
7da4fd4
to
c7066fb
Compare
PR for download page redirect: nodejs/build#399 @thealphanerd Can you please update the original post? |
@nodejs/ctc ... I need a final Go / No Go on making this change in this release. @Fishrock123 has voiced an objection. Need to know what to use for this release. |
@jasnell Website has already been updated: nodejs/nodejs.org#672 (comment) |
Ok... that settles it then lol. @thealphanerd can you make sure this PR is up to date and get it landed? |
With v6 we plan to rename the Stable release line to Current. This commit updates all references to Stable in the codebase. It will have to land along side updates to other repos within the org. ref: nodejs/nodejs.org#669
2384db1
to
d6a5f98
Compare
With v6 we plan to rename the Stable release line to Current. This commit updates all references to Stable in the codebase. It will have to land along side updates to other repos within the org. Refs: nodejs/nodejs.org#669 PR-URL: #6318 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Сковорода Никита Андреевич <chalkerx@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
Landed in 29a6c7c |
With v6 we plan to rename the Stable release line to Current. This commit updates all references to Stable in the codebase. It will have to land along side updates to other repos within the org. Refs: nodejs/nodejs.org#669 PR-URL: #6318 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Сковорода Никита Андреевич <chalkerx@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
With the change of release names from 'Stable' to 'Current' (introduced with Node.js v6), the old download page needs to be redirected. PR-URL: #399 Refs: nodejs/node#6318 Refs: nodejs/nodejs.org#672 Reviewed-By: Johan Bergström <bugs@bergstroem.nu>
With v6 we plan to rename the Stable release line to Current. This commit updates all references to Stable in the codebase. It will have to land along side updates to other repos within the org. Refs: nodejs/nodejs.org#669 PR-URL: #6318 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Сковорода Никита Андреевич <chalkerx@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
With v6 we plan to rename the Stable release line to Current. This commit updates all references to Stable in the codebase. It will have to land along side updates to other repos within the org. Refs: nodejs/nodejs.org#669 PR-URL: #6318 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Сковорода Никита Андреевич <chalkerx@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
With v6 we plan to rename the Stable release line to Current. This commit updates all references to Stable in the codebase. It will have to land along side updates to other repos within the org. Refs: nodejs/nodejs.org#669 PR-URL: #6318 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Сковорода Никита Андреевич <chalkerx@gmail.com> Reviewed-By: Evan Lucas <evanlucas@me.com>
Checklist
Notes
With v6 we plan to rename the Stable release line to Current.
This commit updates all references to Stable in the codebase. It will
have to land along side updates to other repos within the org.
ref: nodejs/nodejs.org#669