v12.0.0 proposal by BethGriggs · Pull Request #26930 · nodejs/node (original) (raw)

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 andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation31 Commits1 Checks0 Files changed

Conversation

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters

[ Show hidden characters]({{ revealButtonHref }})

BethGriggs

In-progress 12.0.0 release - the changelog is expected to change significantly as new 11.x releases occur between now and April 23rd.

There will be one Release Candidate per week.

Refs: nodejs/Release#417, #26844

Notable Changes

bricss, refack, motss, dnalborczyk, gengjiawen, BridgeAR, treyhuffine, and siygle reacted with thumbs up emoji Trott, bricss, jasnell, motss, shisama, dnalborczyk, gengjiawen, treyhuffine, and siygle reacted with hooray emoji bricss, motss, gengjiawen, and treyhuffine reacted with rocket emoji

@nodejs-github-bot

@BethGriggs

@Trott

rc0: https://nodejs.org/download/rc/v12.0.0-rc.0/

I brought this up a lot in the past, and if this is a chance to change the process as it is being documented now, then let's change it finally: These should not be labeled 'rc'. They are not release candidates. A release candidate is something that you put out for testing and, if no issues are found, then the version number is bumped and it is your actual version. In contrast, these are things that whether or not bugs are found, we will be adding more commits to. (Or am I wrong about that? I would be thrilled to be wrong about that. But since we haven't hit the semver-major cutoff date yet, I don't see how I could be....)

We can call it an alpha or a beta or pre or even just 12.0.0-0. But 'rc' sends the wrong information.

There will be one Release Candidate per week.

Yeah, not a release candidate if we know there's going to be another one. This one is not a candidate for release. 😀

@Trott

Oh, and on that "rc" business: I'm OK with not switching it up and just sticking with the "rc" terminology for 12.x. But I guess I want to get it in front of the Release WG to change it going forward. I'm guessing nobody needs one more thing to figure out for 12.x while the existing process is being worked-through, knowledge-transferred, whatever-ed. 😀

@richardlau

Oh, and on that "rc" business: I'm OK with not switching it up and just sticking with the "rc" terminology for 12.x. But I guess I want to get it in front of the Release WG to change it going forward. I'm guessing nobody needs one more thing to figure out for 12.x while the existing process is being worked-through, knowledge-transferred, whatever-ed. 😀

@Trott I invite you to open an issue over in https://github.com/nodejs/Release which we can tag for discussion in the next or upcoming Release WG meeting. Bonus points if you can suggest alternative terminology. If we can agree on alternative terminology I think we'll need cooperation from the Build WG to change the directory the artifacts are uploaded to.

@Trott Trott mentioned this pull request

Mar 26, 2019

@BethGriggs

But since we haven't hit the semver-major cutoff date yet, I don't see how I could be....

@Trott - the semver-major cutoff date was set as 23rd March
#26844, nodejs/Release#417

@jasnell

Thank you @BethGriggs for pushing this one forward. I'm enjoying my much needed break from it ;-) ...

jasnell

### Semver-Major Commits
* [[`afce912193`](https://github.com/nodejs/node/commit/afce912193)\] - **(SEMVER-MAJOR)** **assert**: improve performance to instantiate errors (Ruben Bridgewater) [#26738](https://github.com/nodejs/node/pull/26738)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's an option on branch-diff that will group the subsystems alphabetically by name... --group I think. Makes the changelog much easier to read.

@BethGriggs

@devsnek

#27033 got tsc signoff as semver major after the cutoff, will it be included in 12.x?

@BethGriggs

@devsnek, each week before I make the RC I'm hoping to post a list of the new Semver Major PRs on master for the TSC to 👍 - so it should be able to be included

@BethGriggs

@richardlau

It's a very minor thing but the linter is complaining about a missing newline in the changelog:

https://travis-ci.com/nodejs/node/jobs/193965570#L255-L256

Running Markdown linter on docs... doc/changelogs/CHANGELOG_V12.md 1:1 warning Missing newline character at end of file final-newline remark-lint ⚠ 1 warning

@rvagg

two more infra/build related items to come in, one is ready (#27275, coming out of #26714), can you please pull in a7d7d4d, the other, BUILDING.md #26714 isn't quite done yet but I'll try and get that ready shortly.

@rvagg

BUILDING.md is done, that's in b581d59 and needs to be included here along with a7d7d4d

According to nodejs/build#1768 we're set for Node 12 on the build side. We failed on getting macOS up to where we wanted and the Python situation is going to cause major headaches during the life of 12 but that's just going to have to be the case.

@mmarchini

Would be nice to include https://chromium-review.googlesource.com/c/v8/v8/+/1570582 as well, since it fixes an issue where Node.js will crash if executed with --interpreted-frames-native-stack flag. Unfortunately I don't think it will on V8 on time. I could open a floating patch here before the V8 PR lands if there's no objections.

@rvagg

@mmarchini I think a PR would be the appropriate way to go if you want to get it landed. It'd be doubtful for 12.0.0 at this stage I think but maybe the first follow-up.

BethGriggs added a commit that referenced this pull request

Apr 22, 2019

@BethGriggs

Notable changes:

PR-URL: #26930

@nodejs-github-bot

@BethGriggs

@BethGriggs

@rvagg, I've pulled in #27275 and #26714 - thank you for putting those together

@nodejs/release please take a look, I do not expect to pull in any further commits for v12.0.0 (v12.0.0 commits)

/cc @jasnell

jasnell

@rvagg

Thanks to @mhdawson for the heads-up: sunos binaries weren't appearing. The new smartos18 release machine wasn't hooked up to iojs+release (my bad I guess, although I'm sure I had this working last week!). I've re-run the rc.3 build and it's there now: https://nodejs.org/download/rc/v12.0.0-rc.3/

The promote script should give a ✓ on expected assets now when 12.0.0 gets promoted:

 ✓  Complete set of expected assets in place for v12.x

@addaleax

I’ll try to come up with some improvements for the notable changes list in a few minutes, if you don’t mind.

@addaleax

@BethGriggs In addaleax/node@aa3f88f, I’ve reworked the notable changes list in a few ways (grouped dependency changes, improved formatting via source highlighting, put changes in the right section, replaced useless commit messages, removed non-semver-major-commits).

Additionally, I’d suggest something like addaleax/node@b16ed10, where we separate out the changes that one would more typically consider “notable”, as opposed to having a long list of all breaking changes where the important ones don’t stand out.

Feel free to cherry-pick none, one, or both of these :)

@BethGriggs

Notable changes:

PR-URL: #26930

@nodejs-github-bot

@BethGriggs

@addaleax I have pulled in the first of those - thank you, it does make the notable changes clearer/easier to read :)

@refack

@BethGriggs

@refack, I didn't realise those additional suites were run via a separate job - I can update releases.md to make sure we run on each release.

There seems to have been one test failure benchmark/http/bench-parser.js . Do we block the release on that? Or follow up with a fix in the next v12.x? (/cc @nodejs/release thoughts?)

(I was tagging and about to upload the release as you posted)

@MylesBorins

I think we are in to move forward and patch that benchmark fix in a follow up

@BethGriggs

Ah, i've just spotted #27359, I think we're good to go as it is a test issue.

@mhdawson

@BethGriggs. Good you found that I was looking at the test and it had not be modified recently so good to see we have already decided its a test issue.

@refack

BethGriggs added a commit that referenced this pull request

Apr 23, 2019

@BethGriggs

BethGriggs added a commit that referenced this pull request

Apr 23, 2019

@BethGriggs

Notable changes:

PR-URL: #26930

BethGriggs added a commit to BethGriggs/nodejs.org that referenced this pull request

Apr 23, 2019

@BethGriggs

BethGriggs added a commit to nodejs/nodejs.org that referenced this pull request

Apr 23, 2019

@BethGriggs

@targos targos added release

Issues and PRs related to Node.js releases.

and removed meta

Issues and PRs related to the general management of the project.

labels

Jun 6, 2021

Labels

release

Issues and PRs related to Node.js releases.