├── .editorconfig ├── CODENAMES.md ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── GOVERNANCE.md ├── README.md ├── doc ├── meetings │ ├── 2015-06-11.md │ ├── 2015-06-18.md │ ├── 2015-06-29.md │ ├── 2016-01-25.md │ ├── 2016-02-22.md │ ├── 2016-04-25.md │ ├── 2016-06-27.md │ ├── 2016-07-13.md │ ├── 2017-03-13.md │ ├── 2017-04-24.md │ ├── 2017-05-15.md │ ├── 2017-06-05.md │ ├── 2017-06-26.md │ ├── 2017-09-19.md │ ├── 2019-01-17.md │ ├── 2019-01-31.md │ ├── 2019-03-14.md │ ├── 2019-05-09.md │ ├── 2019-06-20.md │ ├── 2019-08-01.md │ ├── 2019-08-29.md │ ├── 2019-11-07.md │ ├── 2019-12-05.md │ ├── 2019-12-19.md │ ├── 2020-01-16.md │ ├── 2020-01-30.md │ ├── 2020-02-27.md │ ├── 2020-03-12.md │ ├── 2020-03-26.md │ ├── 2020-04-09.md │ ├── 2020-05-07.md │ ├── 2020-05-21.md │ ├── 2020-07-02.md │ ├── 2020-07-16.md │ ├── 2020-08-13.md │ ├── 2020-08-27.md │ ├── 2020-09-10.md │ ├── 2020-09-24.md │ ├── 2020-10-08.md │ ├── 2020-11-05.md │ ├── 2020-12-03.md │ ├── 2021-01-14.md │ ├── 2021-02-11.md │ ├── 2021-02-25.md │ ├── 2021-03-11.md │ ├── 2021-04-22.md │ ├── 2021-05-20.md │ ├── 2021-06-17.md │ ├── 2021-07-01.md │ ├── 2021-08-12.md │ ├── 2021-09-23.md │ ├── 2021-11-04.md │ ├── 2021-12-02.md │ ├── 2022-01-13.md │ ├── 2022-02-10.md │ ├── 2022-03-10.md │ ├── 2022-04-14.md │ ├── 2022-05-05.md │ ├── 2022-06-16.md │ ├── 2022-06-30.md │ ├── 2022-07-28.md │ ├── 2022-08-25.md │ ├── 2022-09-22.md │ ├── 2022-10-01.md │ ├── 2022-10-20.md │ ├── 2022-11-17.md │ ├── 2023-01-12.md │ ├── 2023-02-09.md │ ├── 2023-03-09.md │ ├── 2023-05-09.md │ ├── 2023-06-01.md │ ├── 2023-06-29.md │ ├── 2023-07-27.md │ ├── 2023-08-24.md │ ├── 2023-10-19.md │ ├── 2023-11-16.md │ ├── 2024-01-11.md │ ├── 2024-02-08.md │ ├── 2024-05-30.md │ ├── 2024-06-27.md │ ├── 2024-07-25.md │ ├── 2024-09-19.md │ ├── 2024-10-17.md │ ├── 2024-12-12.md │ └── 2025-05-29.md └── release-guide.md ├── generateReleasePlan.cjs ├── schedule.json └── schedule.svg /.editorconfig: -------------------------------------------------------------------------------- 1 | root = true 2 | 3 | [*] 4 | end_of_line = lf 5 | charset = utf-8 6 | trim_trailing_whitespace = true 7 | insert_final_newline = true 8 | -------------------------------------------------------------------------------- /CODENAMES.md: -------------------------------------------------------------------------------- 1 | This file contains a list of codenames for LTS releases. Codenames for future 2 | releases are subject to change. 3 | 4 | * Argon (4.x 2015) 5 | * Boron (6.x 2016) 6 | * Carbon (8.x 2017) 7 | * Dubnium (10.x 2018) 8 | * Erbium (12.x 2019) 9 | * Fermium (14.x 2020) 10 | * Gallium (16.x 2021) 11 | * Hydrogen (18.x 2022) 12 | * Iron (20.x 2023) 13 | * Jod (22.x 2024) 14 | * Krypton (24.x 2025) 15 | * Lithium (26.x 2026) 16 | * Magnesium (28.x 2027) 17 | * Neon (30.x 2028) 18 | * Oxygen (32.x 2029) 19 | * Platinum (34.x 2030) 20 | 21 | The release schedule is available as a [JSON](./schedule.json) file. 22 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Code of Conduct 2 | 3 | * [Node.js Code of Conduct](https://github.com/nodejs/admin/blob/main/CODE_OF_CONDUCT.md) 4 | * [Node.js Moderation Policy](https://github.com/nodejs/admin/blob/main/Moderation-Policy.md) 5 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | 2 | ## Developer's Certificate of Origin 1.1 3 | 4 | By making a contribution to this project, I certify that: 5 | 6 | * (a) The contribution was created in whole or in part by me and I 7 | have the right to submit it under the open source license 8 | indicated in the file; or 9 | 10 | * (b) The contribution is based upon previous work that, to the best 11 | of my knowledge, is covered under an appropriate open source 12 | license and I have the right under that license to submit that 13 | work with modifications, whether created in whole or in part 14 | by me, under the same open source license (unless I am 15 | permitted to submit under a different license), as indicated 16 | in the file; or 17 | 18 | * (c) The contribution was provided directly to me by some other 19 | person who certified (a), (b) or (c) and I have not modified 20 | it. 21 | 22 | * (d) I understand and agree that this project and the contribution 23 | are public and that a record of the contribution (including all 24 | personal information I submit with it, including my sign-off) is 25 | maintained indefinitely and may be redistributed consistent with 26 | this project or the open source license(s) involved. 27 | 28 | 29 | ### Moderation Policy 30 | 31 | The [Node.js Moderation Policy] applies to this WG. 32 | 33 | ### Code of Conduct 34 | 35 | The [Node.js Code of Conduct][] applies to this WG. 36 | 37 | [Node.js Code of Conduct]: https://github.com/nodejs/TSC/blob/main/CODE_OF_CONDUCT.md 38 | [Node.js Moderation Policy]: https://github.com/nodejs/TSC/blob/main/Moderation-Policy.md 39 | -------------------------------------------------------------------------------- /doc/meetings/2015-06-11.md: -------------------------------------------------------------------------------- 1 | # Node.js Foundation LTS Meeting Minutes 2015-06-11 2 | 3 | ## Present 4 | 5 | * Julien Gilli 6 | * Alexis Campailla 7 | * Michael Dawson 8 | * Colin Ihrig 9 | 10 | ## Agenda 11 | 12 | * Logjam/openssl upgrade 13 | * Upgrade of libuv to 1.6.1 14 | * First draft of breaking changes between io.js/Node 0.12 15 | * Windows Installer Changes 16 | 17 | ## Minutes 18 | 19 | ### Logjam/openssl upgrade 20 | 21 | Michael: Expect OpenSSL upgrade imminently. Just drop support for smaller size. Do we expect that to break users? 22 | 23 | Michael: should also consider including: 24 | 25 | * https://github.com/nodejs/node/pull/1739 26 | * https://github.com/nodejs/node/pull/1831 27 | * https://github.com/joyent/node/issues/25366 (checked and docs for io.js indicate modp1 is still there) 28 | 29 | Michael: Stewart on my team has volunteered to create a PR against Node.js to upgrade OpenSSL. 30 | 31 | ### Libuv upgrade to 1.6.1 32 | 33 | Julien: Libuv PR, fixes annoying issue on OSX 10. Worth reviewing soon. 34 | 35 | Colin: PR already landed in io.js 36 | 37 | Julien: top priority to review that ABI/API hasn.t changed in a breaking way. 38 | 39 | Julien: Julien to try and review today, likely to be included in release for openssl upgrade 40 | 41 | ### Breaking changes between io.js and Node 0.12.X 42 | 43 | First draft of doc of breaking changes between 0.12 and next LTS. 44 | 45 | Julien: https://github.com/nodejs/node/wiki/Breaking-changes-between-v0.12-and-next-LTS-release 46 | 47 | Based on io.js issue tracker, joyent\node backport commit log. v8 breaking changes from release notes (?) 48 | 49 | Please review and comment on issue. 50 | 51 | ### Debug port issues 52 | 53 | Colin working to fix https://github.com/nodejs/node/pull/1949 - new debug port for each worker. 54 | 55 | ### Windows installer changes 56 | 57 | Alexis: https://github.com/joyent/node/issues/5849 - currently a hybrid/broken, will submit PR to do full install for all users, to be added to next milestone 58 | 59 | https://github.com/joyent/node/issues/25087, same upgrade code used for 32/64 bit which is not good practice. Can result in binaries from one (32/64) being put into the other. Will move to use 2 upgrade codes, but this will break upgrade. Going to add manual action to check for old code and give message saying you cannot upgrade and that you should un-install and install again 60 | -------------------------------------------------------------------------------- /doc/meetings/2015-06-18.md: -------------------------------------------------------------------------------- 1 | # Node.js Foundation LTS Meeting Minutes 2015-06-18 2 | 3 | ## Present 4 | 5 | * Joao Reis 6 | * Julien Gilli 7 | * Michael Dawson 8 | * Steven Loomis 9 | 10 | ## Minutes 11 | 12 | ### Upcoming releases 13 | 14 | #### node v0.10.39 15 | 16 | Julien: What's left to do: I suggest to revert 17 | https://github.com/joyent/node/pull/25511. 18 | 19 | Michael: We have another security release with logjam fixes scheduled for 20 | v0.12, so that's ok with me to move that until next couple of v0.10/v0.12 21 | releases. 22 | 23 | Julien: I might have time to start the release process for v0.10.29 today. 24 | Once v0.10 is released, I can move on to releasing v0.12.5. 25 | 26 | #### node v0.12.5 27 | 28 | Julien: We have [a PR to upgrade npm to 29 | 2.11.2](https://github.com/joyent/node/pull/25517). It seems to be a small 30 | change from the current version, so I would advocate for landing that now. 31 | 32 | Michael: Playing devil's advocate: would it delay the OpenSSL upgrade? If so, 33 | then we could postpone it to 0.12.6. If the risk is low, and it's fairly quick 34 | to land it, I'm ok with that. 35 | 36 | Julien: Breaking changes for v0.12: the OpenSSL upgrade prevents TLS clients 37 | to connect to servers that use DH params with keys that are too short to be 38 | safe. 39 | 40 | Michael: Yes, and deferring the change to prevent servers to use shorter keys 41 | until next release. 42 | 43 | ### Moving this weekly call to the LTS WG call 44 | 45 | Julien: We have [a new 46 | doodle](https://github.com/nodejs/LTS/issues/6#issuecomment-112976451) to try 47 | to come up with the best time slot to have these meetings, please fill it out 48 | if you haven't yet. 49 | 50 | ### Having more than one person managing releases 51 | 52 | Julien: having only one person who manage releases is not sustainable, I would 53 | like to have a team of release managers for v0.10.x and v0.12.x releases, and 54 | future LTS releases. 55 | 56 | Julien: I've made some good progress on documenting the release process and 57 | improving some of the build scripts and Jenkins jobs to make them usable by 58 | other people than me. Hopefully that will be ready not too long from now. 59 | 60 | Julien: In the meantime, I'd like to raise that to the broader LTS group and 61 | see who would be interested in being a release manager. 62 | 63 | Steven: I have some experience with releases in the ICU project and other open 64 | source projects, so I can definitely help, even to review and give feedback on 65 | the release process. 66 | 67 | Julien: I'll create an issue in nodejs/LTS to gather initial feedback and see 68 | who could be interested. 69 | 70 | ### Deprecation of shorter keys in DH param server side 71 | 72 | Michael: The OpenSSL upgrade to 1.0.1o prevents clients from connecting to 73 | servers using DH parameters that have a key that is too small to be safe. We 74 | should deprecate passing DH params that are unsafe when creating TLS servers 75 | too. I suggested [some changes to do that on 76 | GitHub](https://github.com/joyent/node/issues/25509#issuecomment-112596586), 77 | could you please provide feedback on these changes? 78 | 79 | ### Transition from v0.12 to next converged LTS release 80 | 81 | Michael: Julien started documenting breaking changes between v0.12.x and 82 | what's currently in the converged repository. Julien, is there any way we can help? 83 | 84 | Julien: Documenting the changes is really the first step. What I need from you 85 | and other members of the LTS working group is to review this list and give 86 | feedback. Once we're confident that we have an accurate list of breaking 87 | changes, the next step is to reach out to various user communities and 88 | determine what we need to do to make the transition as smooth as possible. 89 | 90 | Michael: It seems that there were some productive discussions during Nodeconf 91 | about requirements from users regarding LTS releases. 92 | 93 | Julien: Yes, and there are other additional ways we can reach out to the 94 | broader community: leveraging the Node.js Advisory Board, reaching out to 95 | Joyent's Node.js Incubator participants, the broader community on GitHub, etc. 96 | We will need some coordination between a lot of entities within the Node.js 97 | project. 98 | 99 | Michael: I would suggest reaching out to nan maintainers to identify V8 100 | breaking changes that would be handled by nan. 101 | 102 | Julien: Sounds like a good idea! 103 | 104 | Michael: Maybe instead of commenting in an existing issue, Julien could create 105 | new issue on GitHub to get more attention with all details that he 106 | mentioned. 107 | 108 | Julien: agreed. 109 | 110 | Julien: One other thing that I'd like to use to make the transition even 111 | smoother is release candidates. I had started some work around that a while 112 | ago and unfortunately I haven't had the time to continue working on it. I 113 | think that Rod Vagg did some work around that for io.js and it might be ready 114 | there. Anyway, having release candidates for the next cycle of LTS releases 115 | would probably make things easier. 116 | 117 | Michael: Definitely, this is a broader topic for the LTS working group that we 118 | should probably even consider separately. 119 | -------------------------------------------------------------------------------- /doc/meetings/2015-06-29.md: -------------------------------------------------------------------------------- 1 | # Node.js Foundation LTS Meeting Minutes 2015-06-29 2 | 3 | Recording: https://youtu.be/L_8eDAFhCwc 4 | 5 | ## Present 6 | 7 | * Rod Vagg @rvagg 8 | * Ali Ijaz Sheikh @ofrobots 9 | * Michael Dawson @mhdawson 10 | * Ben Noordhuis @bnoordhuis 11 | * James Snell @jasnell 12 | * Dan Shaw @dshaw 13 | * Trevor Norris @trevnorris 14 | 15 | ## Agenda 16 | 17 | * Breaking changes between v0.12.x and next LTS releases cycle: https://github.com/nodejs/LTS/issues/10 18 | * Stock-take the resources (individuals, companies providing people time) we have available to maintain at least 3 LTS branches, likely more: 0.10, 0.12, possible io.js branches, future LTS—possibly multiple 19 | * 0.10 maintenance, what plans can we formulate at this stage, what do we communicate to users 20 | * 0.12 maintenance, plans and communication 21 | * V8 support, how, who, what can we realistically expect to be able to do & offer here 22 | Begin to formulate future LTS plan; connection with discussions here: nodejs/io.js#1997 and here: #8 (recap the final sections of those two threads for most relevant proposals). 23 | * Formulate some thresholds for backporting; we have a pending PR to pull some fixes in to io.js 1.8 but we haven't come up with a threshold of what should make it in so I've been stalling on my part. 24 | 25 | ## Minutes 26 | 27 | ### Breaking changes between 0.12 and next LTS 28 | 29 | * Julien: wiki page that we’re building: https://github.com/nodejs/LTS/wiki/Breaking-changes-between-v0.12-and-next-LTS-release 30 | * Julien: decide whether we need an 0.14 release cycle or what work we need to do to make sure the transition is smooth 31 | * Julien: don’t expect to need an 0.14, idea was to document the changes and communicate that there was no need for an 0.14; having them documented makes it possible to make the transition easy enough 32 | * James: 0.14 was suggested _if_ the changes were major enough that we needed a transition, alternatively just making the jump would be like “ripping the band-aid off”. 33 | * Dan: Does this include C++ changes? 34 | * Julien: Yes, we need to make sure that NAN covers this. io.js has forced a lot of upgrade in OSS modules but there are lot of enterprise, closed-source modules. 35 | * Julien: Can we have sign-off from the LTS group on this list please? 36 | * Dan: what is the status of Intl here? 37 | * James: still to be determined, Steve Loomis and I are still figuring some of these items out. Assumption is that it will be _at least_ what is in 0.12. 38 | * Rod: there are other changes, often semver-minor, that have caused breakage unintentionally, we should try and capture some of them if possible, although that’s tricky. (Rod TODO: make an issue on io.js to ask for help collecting info on these issues). 39 | * Julien: we need to work in collaboration with the evangelism group to encourage users to start trying this out when we release RCs. 40 | * Dan & James: encourage build & benchmarking groups to get involved in helping with testing compatibility and understanding breakage. 41 | * Julien: Action item: start work on a module testing platform for LTS, with James and Michael who have something in IBM to do this already. 42 | * Rod: https://github.com/rvagg/iojs-smoke-tests useful in smoke testing modules against io.js releases 43 | 44 | ### Resources available 45 | 46 | * Rod: worth taking stock of what resources companies have in making this work and providing people-resources. 47 | * Dan: NodeSource have enterprise customers where LTS is of vital importance so we are keenly interested in putting resources in. Market is very stuck at 0.10 so we are well served keeping that as an option even if it may not be the right choice. 48 | * James: IBM are in the same position, although have a focus on IBM platforms 49 | * Ben: same for StrongLoop, will likely have Ben, Bert and Sam (but mostly Ben). 50 | * Discussion about the next LTS & where io.js fits - agreement that next LTS would be from the converged stream. 51 | 52 | ### 0.10 maintenance 53 | ### 0.12 maintenance 54 | 55 | * Discussed community feedback on what people _want_ from LTS 56 | * James: it seems that an expected upgrade cycle of around 18 months is reasonable for the group we have feedback from already. https://github.com/nodejs/LTS/issues/8 57 | * James: ideally we’d like to get people off 0.10 in the next year. Maintain 0.10 for a year beyond when we release a new LTS, or at least an RC. 58 | * Michael: this would assume we have 3 LTSs in play. Another alternative would be to start putting pressure to get people to move up to 0.12 and drop 0.10 support when next LTS is rolled out. 59 | * Julien: 0.10 is currently called maintenance rather than LTS. 60 | * Rod: we could message this as 0.10 and 0.12 are maintenance releases and the new converged work is the first LTS. Also, can we shorten 0.10 lifecycle? 61 | * James: perhaps 12 months for 0.10 and 18 months for 0.12. 62 | * Julien: the npm stats were an eye-opener, we could use them as we move on to determine how well we are proceeding. 63 | * Discussion around giving people a reason to upgrade rather than letting it drag on forever. 64 | * Discussion around a strawman LTS plan: roll with 12 months for 0.10 and 18 months for 0.12 from new LTS. 65 | 66 | ### LTS Plan 67 | 68 | * James: proposal: 1 LTS release per year 69 | * Dan: preference for releasing at the same time of year. 70 | * Discussion about https://github.com/nodejs/io.js/issues/1997 discussion, particularly about the proposal to have master lasting for a year. 71 | * Rod: ideally we should come up with a plan for LTS and push that back on the non-LTS release discussion. 72 | 73 | **Summary of LTS plan** 74 | 75 | * Julien: LTS once a year for 18 months released at the same time of year, 0.10 for 12 months, 0.12 for 18 months from when we get an LTS out. 76 | * Discussion around 0.12 and the 18 months vs 12 months. 77 | * Discussion around “maintenance” vs full LTS: security only 78 | * James to write up an initial LTS strawman plan. 79 | 80 | * Moved on to discussion on V8, agreed to keep it for next meeting 81 | 82 | * Michael: scope for this group - e.g. what should we incorporate here for future planning work. 83 | 84 | ### Backporting thresholds 85 | 86 | _skipped_ 87 | 88 | ## Next meeting 89 | 90 | * July 6th, 2015 8pm UTC 91 | 92 | Deferred items: 93 | 94 | * Backporting thresholds 95 | * V8 maintenance 96 | -------------------------------------------------------------------------------- /doc/meetings/2016-01-25.md: -------------------------------------------------------------------------------- 1 | # Node.js LTS WG Minutes - 2016-01-25 2 | 3 | ## Attendees: 4 | * James M Snell / @jasnell 5 | * Michael Dawson/ @mhdawson 6 | * Myles Borins / @TheAlphaNerd 7 | * Jeremiah Senkpiel / @Fishrock123 8 | * Rodd Vagg/ @rvagg 9 | 10 | ## Agenda: 11 | 12 | ## nodejs/node-v0.x-archive 13 | 14 | * Deprecate Array#values() in 0.12.x [#25877](https://github.com/nodejs/node-v0.x-archive/issues/25877) 15 | * Deprecate smalloc in v0.12 [#25784](https://github.com/nodejs/node-v0.x-archive/issues/25784) 16 | 17 | ### nodejs/node 18 | 19 | * Updating async_wrap in 0.12.x [#4592](https://github.com/nodejs/node/issues/4592) 20 | 21 | ### nodejs/LTS 22 | 23 | * Discuss possible clarifications to the LTS messaging / labeling [#63](https://github.com/nodejs/LTS/issues/63) 24 | * Discuss the possibility of occasional semver-minor bumps in LTS [#61](https://github.com/nodejs/LTS/issues/61) 25 | * Schedule for v0.10.x and v0.12.x Releases [#52](https://github.com/nodejs/LTS/issues/52) 26 | * Charter this [#48](https://github.com/nodejs/LTS/issues/48) 27 | 28 | ## Minutes: 29 | 30 | These 2 were discussed and it was agreed that nobody's going to get to them and not that important so we'll just close: 31 | 32 | * Deprecate Array#values() in 0.12.x [#25877](https://github.com/nodejs/node-v0.x-archive/issues/25877) 33 | * Deprecate smalloc in v0.12 [#25784](https://github.com/nodejs/node-v0.x-archive/issues/25784) 34 | 35 | This we agreed should not be done: 36 | 37 | * Updating async_wrap in 0.12.x [#4592](https://github.com/nodejs/node/issues/4592) 38 | 39 | In respect to the naming for the LTS release, there is opposition to changing the LTS naming at this point. Myles took the action to discuss with the marketing team to see if there are any issues/background that we are not aware of: 40 | 41 | * Discuss possible clarifications to the LTS messaging / labeling [#63](https://github.com/nodejs/LTS/issues/63) 42 | 43 | 44 | 61 has already been discussed. We will review on a case by case basis. We expect the first 2 to be added in a release coming in a couple of weeks. 45 | * Discuss the possibility of occasional semver-minor bumps in LTS [#61](https://github.com/nodejs/LTS/issues/61) 46 | 47 | 52 was closed as we have done releases for v0.10.x and v0.12.x using the new CI 48 | 49 | * Schedule for v0.10.x and v0.12.x Releases [#52](https://github.com/nodejs/LTS/issues/52) 50 | 51 | This was discussed in the past and should just be closed now. 52 | * Charter this [#48](https://github.com/nodejs/LTS/issues/48) 53 | 54 | 55 | General Discussion 56 | 57 | Discussion on 4.2.5 where we had to respin quickly. We agreed we should start to build additional tests/steps that releasers should go through when releasing and add to that list each time we have a failure like this. Rod took the action to write up a first draft based on what they are doing internally at NodeSource. 58 | 59 | James, need to get more people adding labels with respect to the need to land a PR on LTS when the original PR is closed. Rod suggested we can call out in the PR when we add as one way to raise the awareness. James is also working on a tool to help land a commmit including applying the patch, running lint etc. and adding a reminder to tag as lts-watch could be part of that. 60 | 61 | ## Next Meeting: 62 | 63 | James to schedule in February. Some discussion about how often to schedule but I think we left it at every 2 weeks for now 64 | -------------------------------------------------------------------------------- /doc/meetings/2016-02-22.md: -------------------------------------------------------------------------------- 1 | # Node.js LTS WG Minutes - 2016-02-22 2 | 3 | ## Attendees: 4 | * Michael Dawson/ @mhdawson 5 | * Myles Borins / @TheAlphaNerd 6 | * Kat / @zkat 7 | * Jeremiah / @Fishrock123 8 | 9 | ## Agenda: 10 | 11 | * Round table 12 | * Issues marked with lts-agenda 13 | * Other discussion 14 | 15 | ## Round table 16 | 17 | Kat - continuing 2.x releases, nothing major coming down the pipe. If upgraded to Node 6.X, after latest update to npm 2.x it would still be ok (ie 2.x will work in 6.x). 3.x just pushed today to master should fix npm in master. Latest version of npm coming this friday for LTS should help resolve Windows long path issues. 18 | 19 | Myles - working on 4.4 release candidate. New RC this afternoon. 5.7 is going out tonight and we might pull a few more changes after they mature in 5.7 for a week. 20 | 21 | Michael - Sniff tested out PPC LE for 4.4 RC 22 | 23 | Jeremiah - Nothing specifically LTS related. Looking for discussion on Timers refactor to see if it can make it into LTS (4007 on Node repo) 24 | 25 | ## Issues marked lts-agenda 26 | 27 | ### nodejs/node-v0.x-archive 28 | 29 | ### nodejs/node 30 | 31 | ### nodejs/lts 32 | 33 | #### RC awareness/testing (https://github.com/nodejs/LTS/issues/78) 34 | 35 | ##### RC awareness 36 | 37 | would a callout to organizations through blog or email work ? Possibly an LTS users email ? Or maybe a github issue ? Continue discussion in github repo. 38 | 39 | ##### RC testing 40 | 41 | In terms of testing for native modules Michael D had to point to a different level of headers to be able to build native module. Myles confirmed he saw the same issue and will work to resolve. Issue is because its looking for headers with "dist" in the path and the rc has "rc" in the path intead. 42 | 43 | ## Other discussion 44 | 45 | ### Timer refactoring (https://github.com/nodejs/node/pull/4007) 46 | 47 | Discussion on whether this can go into LTS. Conclusion was we want more input, not a rush so will mark as 48 | lts-agenda and discuss next time when we have a bigger group and in particular Rodd/James 49 | 50 | ## Next Meeting: 51 | 52 | James to schedule in March. 53 | -------------------------------------------------------------------------------- /doc/meetings/2016-04-25.md: -------------------------------------------------------------------------------- 1 | # Node.js LTS WG Minutes - 2016-04-25 2 | 3 | ## Attendees: 4 | * Michael Dawson/ @mhdawson 5 | * James Snell/ @jasnell 6 | 7 | 8 | ## Agenda: 9 | 10 | * Release schedule [#92](https://github.com/nodejs/LTS/issues/92) 11 | * Support from V8 for Node's LTS releases [#88](https://github.com/nodejs/LTS/issues/88) 12 | * Track backporting Path optimizations [#87](https://github.com/nodejs/LTS/issues/87) 13 | * Track backporting AsyncWrap changes [#86](https://github.com/nodejs/LTS/issues/86) 14 | * We have three pr's sitting on master to be discussed: @Fishrock123's timer refactor nodejs/node#4007, 15 | @misterdjules's domain fix nodejs/node#4659, @saghul's libuv update nodejs/node#5994 alanshaw/david#106 16 | looks like it might be causing breakages 17 | * Naming of stable - deferred to github 18 | 19 | ## Issues marked lts-agenda 20 | 21 | ### Release schedule [#92](https://github.com/nodejs/LTS/issues/92) 22 | * Likely to have less changes going in with the release of 6.X 23 | * Plan for monthly release, last week of each month, unless not enough change to warrant it 24 | * Of course security releases may result in unplanned release before then 25 | 26 | ### Support from V8 for Node's LTS releases [#88](https://github.com/nodejs/LTS/issues/88) 27 | From now on if we have PR that is identified to be ported back to LTS release, 28 | ask originator to commit it first in the v8 repo in the older stream. 29 | LTS team will likely have to have to help out with the flow for the first one. 30 | We.ll ask @alphanerd to give LTS team a heads up the first time this happens. 31 | 32 | ### backport changes: 33 | One these wait and see as we want to be sure 34 | all regressions have been identified/resolved first: 35 | 36 | * Track backporting Path optimizations [#87](https://github.com/nodejs/LTS/issues/87) 37 | * Track backporting AsyncWrap changes [#86](https://github.com/nodejs/LTS/issues/86) 38 | * @Fishrock123's timer refactor nodejs/node#4007 39 | 40 | ### @misterdjules's domain fix nodejs/node#4659 41 | 42 | Semver major will not be backport will remove agenda tab 43 | 44 | ### libuv update - nodejs/node#5994 45 | Did not introduce issue, but exposed stdout on shutdown behaviour that a number of modules are 46 | having issues with. 47 | 48 | Should let it settle out for a few 49 | weeks before pulling into 4.x 50 | 51 | ## Next Meeting: 52 | 53 | James to schedule in May 54 | -------------------------------------------------------------------------------- /doc/meetings/2016-06-27.md: -------------------------------------------------------------------------------- 1 | # Attendees 2 | 3 | * James M Snell @jasnell 4 | * Myles Borins @thealphanerd 5 | * Michael Dawson @mhdawson 6 | * Jeremiah Senkpiel @fishrock123 7 | 8 | # Agenda 9 | 10 | ## https://github.com/nodejs/LTS/issues/111 11 | 12 | * going to schedule meeting to discuss with nodejs/v8 and v8 team. 13 | 14 | ## Release schedule for 4.4.7 (this Tuesday) and 4.5 (July 19). 15 | * discussion around what will go into 4.5 along with https://github.com/nodejs/node/issues/6806. Some concern over the libuv update from lts group but concern for libuv team if we do not. 16 | 17 | * discussion on https://github.com/nodejs/node/pull/5745 , was put on hold in an earlier CTC discussion. Agreed to put back on the CTC agenda. 18 | 19 | * Michael to look at backporting patch to allow v8 tests to run from Node tree to 4.X 20 | 21 | # https://github.com/nodejs/LTS/issues/113 22 | 23 | * Mostly security fixes is what has been backported to older stable. 24 | * Seems like weekly downloads were just overtaken by 6.X 25 | * Discussion for CTC as not really and LTS issue. Myles added ctc-agenda to 113 so it will be discussed in next CTC meeting. 26 | * Rod.s blog about security releases indicated June 30th was the end. 27 | -------------------------------------------------------------------------------- /doc/meetings/2016-07-13.md: -------------------------------------------------------------------------------- 1 | # Attendees 2 | 3 | * Myles Borins 4 | * Michael Dawson 5 | * Jeremiah Senkpiel 6 | * Ali Sheikh 7 | * Michael Hablich 8 | * Franziska Hinkelmann 9 | * Rod Vagg 10 | 11 | # Agenda 12 | 13 | * Managing v8 floating patches 14 | * v4.5 15 | * Exporting ssl symbols on windows 16 | 17 | # Discussion 18 | 19 | ## Managing v8 floating patches - https://github.com/nodejs/LTS/issues/111 20 | 21 | * V8 team willing to have place where floating patching can land 22 | * Overlap of 2-3 weeks were still maintained that might cause conflicts 23 | * would need to create separate branch for node. 24 | * Why not create fork 25 | * Notes from Ben N 26 | * What timeframe for using google infrastructure 27 | * We have our own infra and can run from Node tree 28 | 29 | ### Infrastructure 30 | * Chromium infrastructure team is moving fast and deprecating lots of things so may 31 | not support v8 version older than 1 year. 32 | * Will need special (LTS like) support for Node. 33 | * Jeremiah, backport changes need to allow older tests to run on new infra. 34 | * Can still run locally, but cannot run old way in google infra. 35 | * Michael (google) not a feasible option to run Node.js older branches 36 | after a few months. 37 | * Google may be able to assist in adding resources to the Node CI. 38 | * Conclusion is that its not feasible to use Google infra. 39 | 40 | ### Reviews 41 | * Jeremiah - what are the ideas on this front 42 | * Ali, Bookkeeping is also something we want to take care of, would it 43 | make sense to have intermediate v8 fork. Benefit no noise on that repo. 44 | It would be v8 + only patches node needs. Ali does a lot of the merging, 45 | direct fork would be easier to maintain. Would also let us loop 46 | in the v8 team. 47 | * Michael (D), how will google v8 reviewers get hooked in. 48 | So far Ali has been pulling in google people for specific reviews. 49 | Often pulling in an existing fix, so already reviewed so decision 50 | is mostly around whether it makes sense to backport and if does not 51 | apply cleanly then getting the originator to review. 52 | Start with a few people like Ali who will watch and the 53 | add on additional reviewers. 54 | * Ali to write up proposed flow in the issue for discusion in 55 | github 56 | 57 | ## v4.5 58 | 59 | * List of semver minor issues staged, discussed to get agreement 60 | that they can all go in- https://github.com/nodejs/LTS/issues/120 61 | 62 | * Most had been agreed earlier, 2 others were discussed in more 63 | detail. Agreed we should include the 2 new ones: 64 | 65 | * [1aa9c318c9] - (SEMVER-MINOR) repl: copying tabs shouldn't 66 | trigger completion (Eugene Obrezkov) #5958 67 | 68 | * [2e4fb99a86] - (SEMVER-MINOR) src: add node::FreeEnvironment 69 | public API (Cheng Zhao) #3098 70 | 71 | * Myles asked that people review the changelog. 72 | 73 | * 1.9.1 libuv is included in 4.5, want aggressive testing so Myles 74 | to contact npm to ask them to do testing, and will follow up offline 75 | with Rod who else we should ask to do testing. 76 | 77 | * Rod suggested we add flag to also discuss his in CTC meeting. Myles 78 | did that. 79 | 80 | ## Exporting ssl symbols on windows 81 | 82 | * Ben asked that we consider: https://github.com/nodejs/node/pull/7676 83 | 84 | * Landed about 8 days ago, so not likely a candidate for 4.5 release. 85 | Discussion around whether it can cause addon breakage. 86 | 87 | * Original issue: https://github.com/nodejs/node-v0.x-archive/issues/4051 88 | was open for almost 4 years. 89 | 90 | * Maybe we need Ben to talk to this, take offline to get more post-mortem 91 | writeup so that we can make the right decision. 92 | 93 | * Rod, may want to put on hold to let bake in 6 for a little while 94 | and if we see it solving problems for modules we may see 95 | demand to pull back. If it solves openssl issue for 96 | big interger module he is maintaining then he'd be quite 97 | interested 98 | 99 | ## Please review LTS README redo - https://github.com/nodejs/LTS/pull/121 100 | 101 | * It was requested that we all review this one. 102 | -------------------------------------------------------------------------------- /doc/meetings/2017-03-13.md: -------------------------------------------------------------------------------- 1 | # Node.js LTS meeting 13 March 2017 2 | 3 | * Github issue: https://github.com/nodejs/LTS/issues/185 4 | * Meeting video: https://www.youtube.com/watch?v=w45MlYvMSQM 5 | * Previous meeting: https://docs.google.com/document/d/1YK6hYnaVAgGIYC50I8utpx7mD_L-E_127CuuymE3YvU/edit 6 | * Next meeting: April 24 2017 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Myles Borins (@MylesBorins) 12 | * James Snell (@jasnell) 13 | * Jeremiah Senkpiel (@fishrock123) 14 | * Gibson Fahnestock (@gibfahn) 15 | 16 | ## Agenda 17 | * Potential Semver Minor Backports [#177](https://github.com/nodejs/LTS/issues/177) 18 | * Should we consider swapping the timeframe for Active LTS and 19 | maintenance [#130](https://github.com/nodejs/LTS/issues/130) 20 | * Managing floating V8 patches [#111](https://github.com/nodejs/LTS/issues/111) 21 | * Backporting WG [#184](https://github.com/nodejs/LTS/issues/184) 22 | 23 | ## Minutes 24 | 25 | ### Potential Semver Minor Backports [#177](https://github.com/nodejs/LTS/issues/177) 26 | * These have already landed, minor went out 2 weeks ago 27 | * Need to create newer list, to review next meeting. 28 | 29 | ### Should we consider swapping the timeframe for Active and Maintenance [#130](https://github.com/nodejs/LTS/issues/130) 30 | * Myles: seems like longer Active was useful, so he's ok 31 | with keeping as it for now 32 | * James: have been some calls to have longer LTS period (5 year period), 33 | this is a request for a longer overall LTS period as opposed to 34 | changing the split. But probably points to us not wanting to 35 | shorten the active period. 36 | * Jeremiah - suggested we might be able to let more changes into Maintenance. 37 | If no request will just do critical/security fixes. Could allow other 38 | changes on request at the discretion of the LTS team. 39 | * James/Michael - we could allow on request. Maintenance, we 40 | do not do it actively but if somebody wanted to backport we could 41 | land, not necessarily create a release. Would be limited to patch. 42 | * Michael ok, but limited to releases that are not EOL. 43 | Myles should not land unless we are going to do a release. 44 | * If we do takes more changes into Maintenance phase, when will 45 | builds actually go out. Mostly in the past those have been 46 | for security releases, and we don't include any other 47 | changes with those, so when would the changes go in ? 48 | * Myles, possibly if in Maintenance mode, if we accept PRs 49 | outside the critical ones, then we should have a release once/quarter. 50 | 51 | Next actions: 52 | * leave Active/Maintenance as is for now 53 | * open new issue to better define release schedule, this might 54 | include release 1/quarter once in Maintenance. For scheduled minors, 55 | might just be where it would be if the minor is needed. Myles will 56 | take action to open issue, it will include proposed release schedule template. 57 | 58 | ### Managing floating V8 patches [#111]https://github.com/nodejs/LTS/issues/111) 59 | * Myles: This has been pretty much under control. Ali(@ofrobots) has created good 60 | backporting guide. What was not resolved in this issue was how we manage v8. 61 | We had discussed having nodejs/v8 tree, but we are still just floating in 62 | the node repo. https://github.com/nodejs/v8 exists but Myles does not 63 | believe we are using as a staging group. Seems ok now as 64 | we don't need an extra stage of indirection until we have tooling 65 | to automate the flow. Ali has the TODO on a proposal for using the 66 | nodejs/v8 repo. Remove from lts-agenda until there is more progress in issue. 67 | 68 | ### Backporting WG [#184](https://github.com/nodejs/LTS/issues/184) 69 | * Myles (open issue on main repo [11099](https://github.com/nodejs/node/pull/11099) 70 | request to add guide for backporting PRs. Has evolved from documenting 71 | existing process to people defining new process. 72 | * other info, turns out to be just as easy to audit without labels, 73 | just audit everything, and just use tag to mark those that 74 | are blocked on something. 75 | * Myles suggesting that we have separate WG, they would define process 76 | and commit to spend time to do the backports. Each person should 77 | donate 10-15 hours/month. 78 | * Michael, is that document useful for when we ask people to do backport 79 | because it did not land cleanly. 80 | * Jeremiah, doc was supposed to cover all release branches, but current 81 | versus LTS releases may be different. 82 | * Myles, process really should be the same, same meta data etc. 83 | * Generally we are agreed, that a team for backporting would make sense. 84 | 85 | Next actions: 86 | * Volunteers, James, Gibson, Myles, Sam (10 hours each ?) 87 | * Myles will send out email to arrange time. 88 | -------------------------------------------------------------------------------- /doc/meetings/2017-04-24.md: -------------------------------------------------------------------------------- 1 | # Node.js LTS meeting 24 April 2017 2 | 3 | - Github issue: https://github.com/nodejs/LTS/issues/201 4 | - Meeting Video: https://www.youtube.com/watch?v=CVPtof6dZLc 5 | - Next meeting: May 15 2017 6 | - Previous meetings: https://github.com/nodejs/LTS/issues/194 7 | https://github.com/nodejs/LTS/issues/185 8 | 9 | ## Present 10 | 11 | - Michael Dawson (@mhdawson) 12 | - Myles Borins (@MylesBorins) 13 | - James Snell (@jasnell) 14 | - Jeremiah Senkpiel (@fishrock123) 15 | - Sam Roberts (@sam-github) 16 | - Gibson Fahnestock (@gibfahn) 17 | 18 | 19 | ## Agenda 20 | 21 | ### nodejs/LTS 22 | - Limit push access to LTS staging branches to backport team [#199](https://github.com/nodejs/LTS/issues/199) 23 | - Node-v8 LTS support end on 2019-12-31 to meet EOSL of openssl-1.0.2 [#186](https://github.com/nodejs/LTS/issues/186) 24 | - Backporting test fixes to maintenance branches [#205](https://github.com/nodejs/LTS/issues/205) 25 | - Inspector - retain support for `--inspect --debug-brk` https://github.com/nodejs/node/issues/12364 (related: https://github.com/nodejs/node/pull/12615) 26 | - Plan for triaging semver-minor backports in LTS meetings [#204](https://github.com/nodejs/LTS/issues/204) 27 | - Potential Semver Minor Backports [#177](https://github.com/nodejs/LTS/issues/188) 28 | 29 | ## Minutes 30 | 31 | ### Limit push access to LTS staging branches to backport team [#199](https://github.com/nodejs/LTS/issues/199) 32 | 33 | - Myles: knowing that only people with backporting auth allows more trust, as-is, myles has to audit the -staging branch before starting to land commits, which is time consuming. 34 | - Myles: also, everyone should turn on signed commits 35 | - Myles: doesn’t think 7.x-staging (current) needs this kind of protection, for now 36 | - Gibson: +1 37 | - Sam: +1 38 | - Michael: has only pushed to -staging when asked, would this be an issue? 39 | - Myles: would prefer to pick peoples commits to staging 40 | - James: +1 41 | - Myles: mark ctc-review and give it a few days to ensure no objections? 42 | - James: good idea 43 | 44 | 45 | ### Node-v8 LTS support end on 2019-12-31 to meet EOSL of openssl-1.0.2 [#186](https://github.com/nodejs/LTS/issues/186) 46 | 47 | - Gibson: would shorten by 3 months 48 | - Gibson: objections? 49 | - All: … (no objections) 50 | - Myles: what is next version of OpenSSL with long support 51 | - Michael: 1.2? 52 | - Myles: concerned that there is not a more proactive approach to planning when we upgrade openssl 53 | - Michael: lets wait until 8.0, then start talking about it 54 | 55 | 56 | ### Backporting test fixes to maintenance branches [#205](https://github.com/nodejs/LTS/issues/205) 57 | 58 | - Myles: there are already 2 test commits in that fix very broken behaviour 59 | - Myles: concerned about a slippery slope, and that there isn’t a clear policy, and that one test may pull more tests in 60 | - Myles: also concerned that anybody (not just LTS members) feel they have equal access to request backport, and if anybody can request backports, will there be too many? 61 | - James: active, we backport things we think can go, maintainance, we only backport when people request (and after considering the request) 62 | - Michael: feels it should be request driven, and based 63 | - Myles: what about semver-minor? Are we going to allow minors on things in maintenance? 64 | - Sam: I’m OK, if its high value, and VERY low risk 65 | - James: we’ve done this on a case-by-case basis in the past (0.10, 0.12) 66 | - Myles: OK, but we should change the process to express that people may request backports to the maintenance branch, and LTS WG will consider 67 | - Jeremiah: we should always backport tests along with features/fixes 68 | - Myles: need to add wording to that non-critical changes can land with LTS WG consensus, hopefully without a full meeting 69 | - Sam: thinks the test problem under consideration is critical… 70 | - Myles: wants critical to be high bar, something that EVERY user should update to get the fix for 71 | - Michael: willing to take a shot at a new language 72 | - Myles: “will land fixes into maintenance as considered necessary for the stability of the maintenance release” - but we are much less proactive in landing things. Stability is the most important value. 73 | - ... Much description 74 | - Myles: this specific test can land, if there are no objections, but we should change the docs and be very conservative 75 | - ... we all seem to want to be conservative in accepting changes into maintainence releases 76 | 77 | 78 | 79 | ### Inspector - retain support for `--inspect --debug-brk` [nodejs/node#12364](https://github.com/nodejs/node/issues/12364) (related: [nodejs/node#12615](https://github.com/nodejs/node/pull/12615)) 80 | 81 | - [2017-04-24 14:45] If you read me. I say remove `--inspect-brk`, it won't be adopted 82 | - [2017-04-24 14:46] refack: you listing to the LTS meeting? I'm OK with removing --inspect-brk as well. 83 | - Gibson: thinks we should backport --inspect-brk 84 | - Myles: `node debug` already aliased, why not alias `--debug-brk`? 85 | - Gibson: if we are going to use `--inspect-brk` in the future, we should backport it, if we are going to instead just use `--debug-brk` in the future, we should bring it back on master. Conversation about what to do should happen in a new issue. 86 | - [2017-04-24 15:02] octetcloud: new meta issue https://github.com/nodejs/node/issues/12630 87 | 88 | ### Plan for triaging semver-minor backports in LTS meetings [#204](https://github.com/nodejs/LTS/issues/204) 89 | 90 | - Gibson: can we agree on a async review process? If so, we can do triaging online. 91 | - ... no objections in theory 92 | 93 | ### Potential Semver Minor Backports [#177](https://github.com/nodejs/LTS/issues/188) 94 | 95 | - Skipped this time as the list wasn't filtered. 96 | -------------------------------------------------------------------------------- /doc/meetings/2017-05-15.md: -------------------------------------------------------------------------------- 1 | # Node.js LTS meeting 15 May 2017 2 | 3 | - Github issue: https://github.com/nodejs/LTS/issues/213 4 | - Meeting Video: https://youtu.be/UFBMF9ndBDo 5 | - Next meeting: 05 June 2017 6 | - Previous meetings: https://github.com/nodejs/LTS/issues/201 7 | 8 | ## Present 9 | 10 | - Michael Dawson (@mhdawson) 11 | - Myles Borins (@MylesBorins) 12 | - Jeremiah Senkpiel (@fishrock123) 13 | - Sam Roberts (@sam-github) 14 | - Gibson Fahnestock (@gibfahn) 15 | 16 | 17 | ## Agenda 18 | 19 | ### nodejs/LTS 20 | - meta: updated messaging regarding dates [#141](https://github.com/nodejs/LTS/pull/141) 21 | - Clarify what happens with odd-numbered releases in April [#128](https://github.com/nodejs/LTS/pull/128) 22 | - meta: charter the LTS Working Group [nodejs/CTC#122](https://github.com/nodejs/CTC/pull/122) 23 | - Potential Semver Minor Backports [#177](https://github.com/nodejs/LTS/issues/188) 24 | 25 | 26 | ## Minutes 27 | 28 | ### meta: updated messaging regarding dates [#141](https://github.com/nodejs/LTS/pull/141) 29 | 30 | All: No objections 31 | 32 | 33 | ### Clarify what happens with odd-numbered releases in April [#128](https://github.com/nodejs/LTS/pull/128) 34 | 35 | - Myles: I’m not sure we need to declare a support statement at all, we 36 | definitely don’t want to call it maintenance, that conflates it with LTS 37 | maintenance mode, which is different. 38 | - Sam: if we describe odd-numbered as stable then do we need maintenance? 39 | - Myles: we shouldn’t call odd-numbered releases stable, they are current 40 | because they don’t have a support process. 41 | - Myles: We could say: “After the next Current release line comes out, there 42 | will be no more scheduled releases. Further releases will be agreed on a 43 | case-by-case basis.” 44 | - Michael: how about: "An odd-numbered major release will cease to be actively 45 | updated when the subsequent even-numbered major release is cut." 46 | - All: agreed 47 | - Myles: I think the bigger issue is that we are inconsistent about how stable 48 | current is, and whether it’s recommended for more general use. 49 | - Myles to raise CTC issue 50 | 51 | ### meta: charter the LTS Working Group [nodejs/CTC#122](https://github.com/nodejs/CTC/pull/122) 52 | 53 | - Myles: I think the release team should include the LTS team, and a team of 54 | people who do releases. 55 | - Myles: Also the current Release WG should have meetings, even infrequent 56 | ones, that would help us stay on top of our release process. 57 | - Michael: I think it’s still good to have a `releasers` team under the 58 | proposed Release WG that actually handles the release process, so that we 59 | can have a wider Release team that aren’t required to all have release 60 | access. 61 | - Jeremiah: Yeah, there probably will be a lot of overlap between what the 62 | current Release and LTS teams talk about. 63 | - Jeremiah: If we do this, then the Release team might not all need to have the 64 | responsibility to do releases. 65 | - Myles: So maybe the rule should be that to add someone to the releasers team 66 | requires signoff from the CTC. 67 | - Michael: We need to make sure the other Release team members are on board. 68 | - Michael to write up a first draft of the proposal, Myles can review before 69 | the issue is created. 70 | 71 | 72 | -------------------------------------------------------------------------------- /doc/meetings/2017-06-26.md: -------------------------------------------------------------------------------- 1 | # Node.js LTS meeting 26 June 2017 2 | 3 | - [Github Issue](https://github.com/nodejs/LTS/issues/233) 4 | - [Meeting Video](https://www.youtube.com/watch?v=xSo6YiKzc5M) 5 | - [Previous meeting](https://github.com/nodejs/LTS/issues/225) 6 | - Next meeting: 17 July 2017 7 | 8 | 9 | ## Present 10 | 11 | - Gibson Fahnestock (@gibfahn) 12 | - Michael Dawson (@mhdawson) 13 | - James Snell (@jasnell) 14 | - Myles Borins (@MylesBorins) 15 | - Sam Roberts (@sam-github) 16 | 17 | 18 | ## Where 19 | 20 | Hangouts on Air: 21 | - [Observers](https://www.youtube.com/watch?v=XubwojXZGtU) 22 | - [Participants] (https://hangouts.google.com/hangouts/_/ytl/FcgwTFuBbVPgqYyk_hSRjhUJG8ZPjn6IaWBVjStt37g=?eid=100598160817214911030) 23 | - [Events page](https://www.youtube.com/my_live_events) 24 | - [Minutes](https://docs.google.com/document/d/16c_FvWTi-IJ-gZkjfo_eQtIOyRpgpGRUGTq2re3CnGs/edit?usp=sharing) 25 | 26 | ## Agenda 27 | 28 | ### doc: charter the Release working group [#223](https://github.com/nodejs/LTS/pull/223) 29 | 30 | - Michael: Not much to say on this, mostly just want to see if there are any 31 | major issues, or if it’s just a question of touching it up and taking it to 32 | the CTC. 33 | - Myles: I haven’t looked at it since the last update, I’ll get to that this 34 | week 35 | - Sam: I’ll take another look too 36 | 37 | ### Put the Boron releases in a more discoverable location 38 | 39 | - Gibson: I’ve had a couple of people ask me about the 6.x release schedule, 40 | and they’ve found the issue somewhat hard to find. 41 | - Myles: I want to make sure we keep the noncommittal nature of it. 42 | - Gibson: No reason you couldn’t just have a disclaimer above it. I think it 43 | would be nice to have it in a more accessible place. 44 | - Michael: I guess the problem is that updating the README is harder than just 45 | commenting on an issue. 46 | - Myles: I’m happy to compromise on keeping it in the wiki, we can just update 47 | it there, and have a link to it from the README. 48 | - Gibson: SGTM 49 | - Myles: I’ll look at doing that 50 | - All: no objections 51 | 52 | ### Backporting work 53 | 54 | - Michael: What’s the update on the backporting work? Are there things we can 55 | improve? 56 | - Myles: Yes definitely, I don’t have the solid block of time every month to 57 | put into it any more, it takes about 30 hours a week. 58 | - Gibson: I’ve done some of the work this time, just spending some time on it 59 | here and there. I found that doing it with Myles worked quite well, we just 60 | had to make sure we communicated about who was doing what. 61 | - Sam: I’d be happy to help out, I just don’t tend to know when the time is, so 62 | being pinged when there’s work to do would be nice. 63 | - Myles: I think we want to move to a more continuous backporting cadence, 64 | rather than doing it heavily for a few days before the release. Having an 65 | auditing issue in LTS worked quite well. 66 | - Myles: Also want to thank the folks at Github for working with me to fix the 67 | issue with our tool, I pushed an update to branch-diff to ameliorate the 68 | problem. 69 | - Michael: Is there a document detailing how the process works? 70 | - Gibson: I started writing some stuff down as I was doing it, but it’s not 71 | there yet. 72 | - Michael: I think having that would be pretty helpful. 73 | - Gibson: However I think the quickest way to get going is to pair with Myles 74 | for a couple of hours. 75 | - Myles: I’m moving around a lot, but I’m pretty on top of my calendar, so if 76 | anyone wants to pair we can definitely find a time and work something out. 77 | 78 | - Myles: James, would http2 be backportable to Node 6.x? 79 | - James: Yes, there are no breaking changes so it should absolutely be 80 | backportable. I’m just checking to make sure that there are no issues on all 81 | our supported platforms. 82 | 83 | ### other 84 | 85 | None 86 | 87 | 88 | -------------------------------------------------------------------------------- /doc/meetings/2017-09-19.md: -------------------------------------------------------------------------------- 1 | # Node.js LTS meeting 19 September 2017 2 | 3 | - [Github Issue](https://github.com/nodejs/Release/issues/244) 4 | - [Meeting Video](https://www.youtube.com/watch?v=Y01b-pMIp8E) 5 | - [Previous meeting](https://github.com/nodejs/Release/issues/243) 6 | - Next meeting: 9 October 2017 7 | 8 | ## Present 9 | 10 | - Myles Borins (@mylesborins) 11 | - James Snell (@jasnell) 12 | - Jeremiah Senkpiel (@fishrock123) 13 | - Sam Roberts (@sam-github) 14 | - Michael Dawson (@mhdawson) 15 | - Ali Iyaz Sheikh (@ofrobots) 16 | 17 | ## Agenda 18 | 19 | ### V8 6.1 in Node 8.x 20 | 21 | - Myles: V8 6.1 Branch is now ABI compatible with Node 8.x. 22 | - Myles: Propose October 31st for Node 8.x LTS 23 | - Jeremiah: If it slips it’ll be November, I’d prefer 24th 24 | - James: Planning 30th for 9.0.0 25 | - Myles: We could do a cutoff of 24th and do builds then, then promote on 31st 26 | - Jeremiah: Sounds good 27 | - Rod: 6.1 of v8 gives us what over 6.0? 28 | - Myles: modern v8 29 | - Ali: Lots of performance fixes for 6.1 30 | - Jeremiah: Does it have import module support? 31 | - Myles: That’s 6.2 32 | - Rod: Want to reiterate reasons we previously had for not upgrading last minute. I think we can make a special allowance in this case for Turbofan, as that itself is unstable. 33 | - Rod: Don’t want to get into a pattern of dumping stuff into LTS up to the last minute, negating part of the point of having LTS. 34 | - Myles: Having managed the LTS branches, I’m not sure it’s possible to stabilise a release over 6 months, given that we’re constantly releasing minors. 35 | - Rod: I was thinking about this too w.r.t the c-ares patch. 36 | - Rod: It increases the likelihood of unavoidable semver-majors 37 | - Sam: For V8 6.1, I think we need to get it out there. But I’m also concerned about the general precedent. Maybe we could not have minors over the last 3 months of current. The first thing that is called LTS should actually be LTS. 38 | - Myles: I think the amount of work that it takes to manage these branches means that it’s not feasible to diverge greatly from master for the first six months. 39 | - Michael: I think semver-minors are not all equal, something like a V8 update is a lot different from adding a new API or something. 40 | - Ali: I think the risk of a V8 upgrade is less destabilising than the diffs would suggest, it has been used in Chrome by millions of users. 41 | - Jeremiah: True, but it is more destabilising than the average semver-minor, and we have to discuss those. 42 | - Rod: It’s not just V8 6.1, we’ve had to shake out things that are different in Node to the browser. Stability has increased greatly, but there’s still a shaking-out period. It’s not entirely the same. 43 | - Ali: I think I’d like to see a month of feedback from Node regarding performance. 44 | - James: Yeah, but that month of feedback is before the release. 45 | - Myles: I think users want newer features as well as stability, we have to balance the two. 46 | - Michael: Specifically for 6.1 I think it’s worth the risk, in general we probably need to have more discussion about this not being general practice. 47 | - James: Agreed on both. 48 | - Myles: Perhaps we should revive the PR for a 2 month cutoff before semver-minors 49 | - Jeremiah: I think I like Sam’s idea from earlier 50 | - Michael to raise PR for policy, general agreement on V8 6.1 backport. 51 | 52 | ### Review of semver-minors for 6.x 53 | 54 | - _Notes in individual PRs_ 55 | -------------------------------------------------------------------------------- /doc/meetings/2019-01-17.md: -------------------------------------------------------------------------------- 1 | # Node.js Foundation Release WorkGroup Meeting 2019-01-17 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=x-hgNThytRU 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/407 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1Aq92HyIMUYHpxDqHLkR2HNv1sHQUFF_aG-fxLvGOZpA 8 | 9 | ## Present 10 | 11 | * Release team: @nodejs/Release 12 | * LTS team: @nodejs/lts 13 | * Beth Griggs 14 | * George Adams 15 | * Ruben Bridgewater 16 | * Myles Borins 17 | * Michael Dawson 18 | * Shelley Vohr 19 | 20 | ## Agenda 21 | 22 | ## Announcements 23 | 24 | *Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 25 | 26 | ### nodejs/Release 27 | 28 | ### Additional semver minor to 8.x during maintenance [#405](https://github.com/nodejs/Release/issues/405) 29 | * (Myles) Request for semver minor during maintenance for include backports for tsfn, crypto, and potentially namespaces. 30 | * (Michael): Overview of tsfn in N-API. Reduces the number of modules that have to use libuv directly. Good for N-API adoption, users telling us that it is important (including `fsevents`), low risk as additive. 31 | * (Myles): Suggestion of quarterly releases during maintenance. 32 | * Consensus for another semver minor for 8.x. 33 | 34 | * **Action:** Michael to write proposal LTS releases for N-API backports. 35 | 36 | ### Changes to 10.x q1 release schedule [#404](https://github.com/nodejs/Release/issues/404) 37 | 38 | * Happy with cadence of releases and the rotation of releasers. 39 | 40 | * Discussion of patch or minor to resolve the npm-rc issue. Preference to promote minor. 41 | 42 | * Rule to require promotion of a current release before an LTS release has not yet landed. Agreed the rule makes sense, but due to the current situation of onboarding several releasers and the rule no yet landing, Shelly will promote January 29th v10.x release. 43 | 44 | ### Plan for Node.js 11 Current releases [#397](https://github.com/nodejs/Release/issues/397) 45 | * 2019-01-22 11.x release will be pushed out due to v11.7.0 going out 2019-01-17. v11.7.0 was pushed out to allow time for more backports. 46 | 47 | * (Ruben) Currently in a good state for v11.x backports. 48 | 49 | * (Myles) Delaying the release points to the same issue we've had with LTS backports - maybe we should reexamine what the definition of what “done” is? Suggestion at collaborator summit that we should close PRs only when they are backported (or not to) release lines. 50 | 51 | * (Ruben) More automation rather than process change. Encourage owners of PRs to backport PRs as the owner will have the most context. 52 | 53 | * (Ruben) Suggestion of follow up commits to SemVer-majors that remove the SemVer-Major content. This will reduce the amount of churn while backporting PRs. Suggestion of adding version checks to SemVer-major commits. 54 | 55 | * (Myles) Suggests a playbook or proposal for Ruben's suggestion. 56 | 57 | ### Bringing back regular meetings [#333](https://github.com/nodejs/Release/issues/333) 58 | * Try and reschedule one of the meetings per quarter to better accommodate APAC. 59 | * **Action:** Beth to update template to contain meeting link. 60 | 61 | ## Q&A, Other 62 | 63 | * Determine how we onboard new releasers. 64 | 65 | * Increase discoverability of requested backports. Encourage both PR owners and others pick up backporting. Suggestion of code-and-learn for backporting or as a good second commit. 66 | * **Action:** Beth will open an issue to discuss. 67 | 68 | ## Upcoming Meetings 69 | 70 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 71 | 72 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 73 | 74 | 75 | -------------------------------------------------------------------------------- /doc/meetings/2019-01-31.md: -------------------------------------------------------------------------------- 1 | # Node.js Foundation Release WorkGroup Meeting 2019-01-31 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=Q4my5ucnGx8 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/411 7 | 8 | ## Present 9 | 10 | * Beth Griggs 11 | * Michael Dawson 12 | * Shelley Vohr 13 | * Michaël Zasso 14 | * Richard Lau 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | *Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 21 | 22 | ### nodejs/node 23 | 24 | ### \[v6.x backport\] src: add environment cleanup hooks [#22633](https://github.com/nodejs/node/pull/22633) 25 | 26 | * (Richard) I believe this is on the agenda because there are no scheduled further releases of 6. 27 | * (Richard) We need to make a decision one way or another whether this will land in v6.x. 28 | * (Michael) v6.x is broken in the sense that it claims to have support for 1.3 but it doesn't. Mitigating factor is no one has reported this as an issue. 29 | * (Beth) Will this cause any problems for migration? 30 | * (Michael) Not going to effect migration. If you write your addon with 8 or 10, this function would be missing. 31 | * (Michael) The documentation states the function is there, but it is missing. 32 | * (Michael) If it wasn't so close to 6.x going out of LTS i'd say we should definitely do another release to include it. 33 | * (Shelly) I guess the question is, is the work it would take worth the benefit we get from doing it. How much do we care about N-API consistency? 34 | * (Michael) Important for adoption phase and confidence of N-API. Nobody has complained since August though. 35 | * (Richard) There are commits on v6.x-staging that haven't gone out in a release. 36 | * (Richard) Maybe we should audit the commits on v6.x-staging to see if it is worth cutting a release. 37 | * **Action**: Audit commits on v6.x-staging 38 | 39 | ### nodejs/Release 40 | 41 | ### Plan for Node.js 11 Current releases [#397](https://github.com/nodejs/Release/issues/397) 42 | 43 | * (Michael Z) v11.9.0 went out yesterday, no one has volunteered for next release yet, I could possibly do that if no one else. 44 | * (Shelly) I could take that over. 45 | * (Beth) I think we're covered for the next couple of releases. 46 | 47 | ### doc: update the releaser onboarding process and rules [#393](https://github.com/nodejs/Release/pull/393) 48 | 49 | * (Beth) Rods PR that is open in nodejs/release. I guess what just needs to happen is it to get a few more reviews before it lands. 50 | * (Beth) Has everyone seen this PR? 51 | * (Michael) I can have a look after the meeting. 52 | * **Action**: Review and land PR. 53 | 54 | ### doc: update to reflect N-API [#410](https://github.com/nodejs/Release/pull/410) 55 | 56 | * (Michael) So we talked about this last week. Suggestion was I do a PR that tweaks the release process for N-API. 57 | * (Beth) Does anything nodejs/node need updating to reflect this? 58 | * (Michael) No, I think it belongs in Release. 59 | * (Michael) It has approvals, there are no objections, so I think it just on the release agenda to see if the release team agrees. Other than that it is ready to land. 60 | * **Action**: Land PR. 61 | 62 | ## Q&A, Other 63 | 64 | * v8.x release due March time. 65 | * **Action** (Beth) Node 12 prep to begin 66 | 67 | ## Upcoming Meetings 68 | 69 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 70 | 71 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 72 | 73 | -------------------------------------------------------------------------------- /doc/meetings/2019-03-14.md: -------------------------------------------------------------------------------- 1 | # Node.js Foundation Release WorkGroup Meeting 2019-03-14 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/419 7 | 8 | ## Present 9 | 10 | * Michael Dawson (@mhdawson) 11 | * Shelley Vohr (@codebytere) 12 | * Michael Zasso (@targos) 13 | * Richard Lau (@richardlau) 14 | * Bethany Griggs (@BethGriggs) 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | *Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 21 | 22 | ### nodejs/node 23 | 24 | * Should libuv upgrades be semver-minor? [#25785](https://github.com/nodejs/node/issues/25785) 25 | * Defer discussion to when we have Myles 26 | 27 | * \[v6.x backport\] src: add environment cleanup hooks [#22633](https://github.com/nodejs/node/pull/22633) 28 | * Michael will ping Gabriel to make sure it is on his radar, Done and 29 | Gabriel will look ASAP. 30 | 31 | ### nodejs/Release 32 | 33 | * Plan for Node.js 11 Current releases [#397](https://github.com/nodejs/Release/issues/397) 34 | * Ruben is working on this, had to pull out a few PRs 35 | * Some related to crypto, but not Sam’s to get us to 1.1.1 36 | * CITGM looks good, failures look like noise or not related 37 | * Last actions, pull out one more crypto PR, check with Fastify on one issue 38 | * Asked that Beth take a look at CITGM results as well. 39 | 40 | * Ruben, should we be landing commits in staging in advance as opposed to waiting 41 | for release? 42 | * Beth I think it’s just a matter of people getting time? 43 | * Ruben 2 branches, patch proposal and minor proposal? 44 | * First step start with branches, and can immediately land when ready 45 | * Michael first step is probably to do PR to update doc on flow? 46 | * Ruben, will do that. 47 | 48 | * Final 6.x release before EOL? [Discussion] #414 49 | * Target for first week of April (sounds good to everybody) 50 | 51 | * Preparation for Node 12 [#417](https://github.com/nodejs/Release/issues/417) (Build?) 52 | 53 | * Review v10.x Q2 release plan 54 | * Beth showed overview of proposal 55 | 56 | * Will defer review of SemVer minors for 8.x and 10.x to next meeting as we don’t currently have 57 | the lists 58 | 59 | ## Q&A, Other 60 | 61 | ## Upcoming Meetings 62 | 63 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 64 | 65 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 66 | -------------------------------------------------------------------------------- /doc/meetings/2019-05-09.md: -------------------------------------------------------------------------------- 1 | # Node.js Foundation Release WorkGroup Meeting 2019-05-09 2 | 3 | ## Links 4 | 5 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/444 6 | * **Minutes Google Doc**: https://docs.google.com/document/d/1wilsRUSzbsqk-D1pG2P3LEplg_UosPPtZwrk-8yPbyY 7 | 8 | ## Present 9 | 10 | * Beth 11 | * Richard 12 | * Ruben 13 | * Sam 14 | * Shelley 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | *Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 21 | 22 | ### nodejs/Release 23 | 24 | * Adding a "security" property to dist/index.json [#437](https://github.com/nodejs/Release/issues/437) 25 | - Richard is working on this. 26 | - **Action:** Release team to take a look at https://github.com/nodejs/node/pull/27612 and https://github.com/nodejs/nodejs-dist-indexer/pull/8 and provide feedback. 27 | * Defining a word for all current releases [#359](https://github.com/nodejs/Release/issues/359) 28 | - Discussed alternative words. Suggestions: LTS Maintenance, Current Maintenance. 29 | - **Action:** Ruben suggested PR the new wording so that we have something to work from. 30 | * Development kit and Deployment kit releases [#341](https://github.com/nodejs/Release/issues/341) 31 | - Old issue. No recent demand for development/deployment release. Issue calls out node-report but that is now in core. 32 | - Benefits/some demand in having a release without npm included. 33 | - **Action:** Will ask the build workgroup if they have capacity to add these build jobs and see if there is anyone willing to champion them. 34 | * Event stream for new releases and gpg keys [#322](https://github.com/nodejs/Release/issues/322) 35 | - Agreed that having such a tool would be nice, but the release team has not got the bandwidth to create it. 36 | - **Action:** To reach out and see if any contributors/collaborators would be interested in creating such a tool, including the tooling and/or automation teams. 37 | * Release metadata [#290](https://github.com/nodejs/Release/issues/290) 38 | - Seems related and may be partially addressed by [#437](https://github.com/nodejs/Release/issues/437) 39 | 40 | ### nodejs/TSC 41 | 42 | * Regular schedule for Security releases? [#647](https://github.com/nodejs/TSC/issues/647) 43 | - @sam-github discussed why these are wanted and to trial the idea. 44 | - **Action:** Add a “security” release to the Release schedule for 28th June across Node.js 8, 10, 12. 45 | 46 | ## Q&A, Other 47 | 48 | ## Upcoming Meetings 49 | 50 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 51 | 52 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 53 | 54 | 55 | -------------------------------------------------------------------------------- /doc/meetings/2019-06-20.md: -------------------------------------------------------------------------------- 1 | # Node.js Foundation Release WorkGroup Meeting 2019-06-20 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=IDJWHNgiMGE&t=398s 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/460 7 | 8 | ## Present 9 | 10 | * Beth Griggs (@BethGriggs) 11 | * Myles Borins (@MylesBorins) 12 | * Richard Lau (@richardlau) 13 | * Sam Roberts (@rsam) 14 | * Ruben Bridgewater (@BridgeAR) 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | *Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 21 | 22 | ### nodejs/Release 23 | 24 | * A proposal for changes to LTS [#458](https://github.com/nodejs/Release/issues/458) 25 | * Current state: 26 | * LTS Releases 6 months in current, 18 months in Active LTS, 12 months in maintenance 27 | * Aim for monthly release during active, no determined schedule for releases during maintenance 28 | * Generally avoid SEMVER-MINORS during maintenance 29 | * This proposal swaps active to 12 months and maintenance to 18 months 30 | * No longer have overlapping Active LTS releases 31 | * More accurately reflects the release teams capacity to do releases 32 | * We should make a decision before v12.x goes into Active LTS 33 | * (Action) Raise a PR changing and use approvals on that to gain consensus 34 | 35 | * Proposal: Stop specifying patch or minor for LTS releases [#449](https://github.com/nodejs/Release/issues/449) 36 | * Needs user research 37 | * Concerns: 38 | * Users typically want less SEMVER-MINORS in LTS releases for stability 39 | * Platforms and downstream distributions take a longer time to upgrade to SEMVER-MINOR than a PATCH 40 | * All LTS release would be SEMVER-MINOR and this could be a burden on consumers 41 | * Landing commits in order might not make things easier as there will still be commit gaps 42 | * Most of the burden is in the manual auditing of commits not landing 43 | * Sam found when backporting TLS 1.3 that order was significant 44 | * Hard to trial this proposal 45 | * (Sam) My experience is that users are reluctant to upgrade in general 46 | * Do we believe SEMVER-MINORS are more risky? 47 | * Likely to be more buggy as they've had less time to mature 48 | * Does it matter if there are bugs in new features? 49 | * LTS implies stability, so we shouldn't be adding unstable features 50 | * Alternative proposal: 51 | * Only land commits with LTS watch labels on them 52 | * Landing significantly less 53 | * Onus on collaborators to label things that need to go to LTS 54 | * Smaller LTS releases 55 | * Proposal regarding multiple branches [#420](https://github.com/nodejs/Release/pull/420): 56 | * Concerns: 57 | * Cannot change history of the vN.x branches, cannot force-push 58 | * Downstream users floating patches on release lines 59 | * Module maintainer point of view 60 | * May benefit from SEMVER-MINORs in older LTS releases due to more consistent feature availability across release lines 61 | * But if SEMVER-MINORs don't go back, incentive to upgrade 62 | * Suggestion of recruiting more LTS members/releasers to go through the process 63 | * (Action) User survey of expectations of LTS 64 | 65 | 66 | * Defining a word for all current releases [#359](https://github.com/nodejs/Release/issues/359) 67 | * Need to PR this change 68 | * Development kit and Deployment kit releases [#341](https://github.com/nodejs/Release/issues/341) 69 | * Work with Build WG 70 | * Myles check with TSC before doing so 71 | * Check the Release team are in sync with Node.js core 72 | * Start a thread with TSC 73 | 74 | ## Q&A, Other 75 | 76 | * (Richard) Will the security update happen? 77 | * Nothing to ship 78 | * OpenSSL updates can go in regular releases as they are public updates 79 | * Will not schedule security releases going forward 80 | 81 | ## Upcoming Meetings 82 | 83 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 84 | -------------------------------------------------------------------------------- /doc/meetings/2019-08-01.md: -------------------------------------------------------------------------------- 1 | # Node.js Foundation Release WorkGroup Meeting 2019-08-01 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | * **Minutes Google Doc**: $MINUTES_DOC$ 8 | 9 | ## Present 10 | 11 | * @BethGriggs 12 | * @BridgeAR 13 | * @keywordnew 14 | * @targos 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | *Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 21 | 22 | ### nodejs/Release 23 | 24 | * When to do the next v12.x release? 25 | * Continue to go two weeks between each release, next v12.x due 6th August 26 | * Typically 90 commits per week in current release line, every 2 weeks is managable 27 | * Updated the v12.x calendar 28 | * Final Node 8 scheduled release? [#466] 29 | * No objections - @BethGriggs has scheduled the release for 27th August 30 | * Patches only 31 | * @BridgeAR request to join LTS tutorial session with @keywordnew 32 | * Release survey [#461](https://github.com/nodejs/Release/issues/461) 33 | * Summary of conversations in https://github.com/nodejs/Release/issues/461 34 | 35 | ## Q&A, Other 36 | 37 | ## Upcoming Meetings 38 | 39 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 40 | 41 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 42 | -------------------------------------------------------------------------------- /doc/meetings/2019-08-29.md: -------------------------------------------------------------------------------- 1 | # Node.js Foundation Release WorkGroup Meeting 2019-08-29 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=MBqDK5icH8c 6 | * **GitHub Issue**: $GITHUB_ISSUE$ 7 | * **Minutes Google Doc**: $MINUTES_DOC$ 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Myles Borins (@MylesBorins) 13 | * Ruben Brigewater (@BrigeAR) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | *Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | ### nodejs/Release 22 | 23 | * Manual backports with compatibility patches [#468](https://github.com/nodejs/Release/issues/468) 24 | * Came to conclusion that we could ask contributors to create compatability patches when backporting PRs to make it easier for to review the changes that are specific to the release line. On laning we woul squash these commits into the original cherry-picked commit. 25 | * (Action) PR this information to the backporting guide for review. - @BridgeAR 26 | * Release survey [#461](https://github.com/nodejs/Release/issues/461) 27 | * (Action) All of release to read through and add commits in the issue. 28 | * Release plan - v12.x Current [#435](https://github.com/nodejs/Release/issues/435) 29 | * Continue as per schedule in [#435](https://github.com/nodejs/Release/issues/435) 30 | * Defining a word for all current releases [#359](https://github.com/nodejs/Release/issues/359) 31 | * Reviewed the PR in Package Maintenance 32 | * Sync up with Package Maintenance on the definition of "Maintained/Supported" 33 | * Clarify difference between "All" and "Maintained" or remove one of those. 34 | * Suggestion of including definition on nodejs.org. 35 | 36 | ## Q&A, Other 37 | 38 | ## Upcoming Meetings 39 | 40 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 41 | 42 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 43 | 44 | 45 | -------------------------------------------------------------------------------- /doc/meetings/2019-11-07.md: -------------------------------------------------------------------------------- 1 | # Node.js Foundation Release WorkGroup Meeting 2019-11-07 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=h4qoaC6Iy74 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/500 7 | 8 | ## Present 9 | 10 | * Beth Griggs 11 | * Michaël Zasso 12 | * Myles Borins 13 | * Ruben Bridgewater 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | *Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | ### nodejs/Release 22 | 23 | * doc: clarify LTS bit flip process [#496](https://github.com/nodejs/Release/pull/496) 24 | * Last couple of approvals, then ready to land. 25 | * Release plan - v12.x Active LTS [#494](https://github.com/nodejs/Release/issues/494) 26 | * (Action) Check documentation for release candidates. 27 | * (Action) Edit schedule to include release candidate dates. 28 | * Aim for no/minimal additional commits after the RC. 29 | * (Myles) I follow the rule that commits must be in current for two weeks before they land on staging. Decision by the LTS/Release team on case-by-case basis. 30 | * We should plan Q1 releases in a meeting in December. 31 | * Release plan - v13.x Current [#487](https://github.com/nodejs/Release/issues/487) 32 | * Covered for v13.x releases until January 2020. 33 | * Running benchmarks during release [#479](https://github.com/nodejs/Release/issues/479) 34 | * We should try and run a subset of benchmarks on the release candidates. 35 | * (Action) Identify Jenkins job that allows us to run benchmarks. Determine the subset of benchmarks that we will run. Add this job to the `test-release-candidate` Jenkins job. 36 | 37 | * Release survey [#461](https://github.com/nodejs/Release/issues/461) 38 | * Holding off on this for now due to concerns raised. Will leave the issue open for reference. 39 | 40 | * Defining a word for all current releases [#359](https://github.com/nodejs/Release/issues/359) 41 | * Waiting on @mhdawson’s PR. Will review once it is open. 42 | 43 | ## Q&A, Other 44 | 45 | * Node.js Collaborator Summit - Release Agenda [#502](https://github.com/nodejs/Release/issues/502) 46 | * Onboarding new releasers 47 | * Automation 48 | 49 | ## Upcoming Meetings 50 | 51 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 52 | 53 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 54 | 55 | 56 | -------------------------------------------------------------------------------- /doc/meetings/2019-12-05.md: -------------------------------------------------------------------------------- 1 | # Node.js Foundation Release WorkGroup Meeting 2019-12-05 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=1ZlmRoDeWyc 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/509 7 | 8 | ## Present 9 | 10 | * Beth Griggs 11 | * Michaël Zasso 12 | * Richard Lau 13 | * Ruben Bridgewater 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | *Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | ### nodejs/Release 22 | 23 | * Node.js Collaborator Summit - Release agenda [#502](https://github.com/nodejs/Release/issues/502) 24 | * Not many of us can attend this summit 25 | * Investigate potential to do a Zoom call 26 | * "Current" should include v12.13 [#495](https://github.com/nodejs/Release/issues/495) 27 | * Ask whether this is causing a functional issue (perhaps with `nvm`?), or our terminology needs improving 28 | * Website issue is fixed 29 | * Limited number of releasers - we cannot make promises around the ordering of releases as it may be determined by availability at the time 30 | * Should libuv upgrades be semver-minor? [#443](https://github.com/nodejs/Release/issues/443) 31 | * Consensus was that Node.js should follow what the libuv release was marked as (patch, minor) 32 | * Not make a special case for libuv 33 | * (Action) Document consensus in the issue 34 | * Defining a word for all current releases [#359](https://github.com/nodejs/Release/issues/359) 35 | * (Action) Create a table of definitions of our terminology in Node.js Release 36 | 37 | ### nodejs/build 38 | * Sharing release keys - nodejs/build#1913 39 | * +1 on a nodejs-keys dedicated repo 40 | * Existing documentation that references the release keys should be updated 41 | 42 | ## Q&A, Other 43 | 44 | * Node.js 8 open backports 45 | * No more planned releases of v8.x 46 | * (Beth) I don’t think we should do a release 4 weeks before End-of-Life 47 | * Timing of this release could be a challenge due to vacation 48 | 49 | ## Upcoming Meetings 50 | 51 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 52 | 53 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 54 | 55 | -------------------------------------------------------------------------------- /doc/meetings/2019-12-19.md: -------------------------------------------------------------------------------- 1 | # Node.js Foundation Release WorkGroup Meeting 2019-12-19 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=q02Viu-HHIk 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/512 7 | 8 | ## Present 9 | 10 | * Beth Griggs (@BethGriggs) 11 | * Michaël Zasso (@targos) 12 | * Myles Borins (@MylesBorins) 13 | * Richard Lau (@richardlau) 14 | * Ruben Bridgewater (@BridgeAR) 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | *Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 21 | 22 | ### nodejs/Release 23 | 24 | * Node.js Release mentoring/streaming [#511](https://github.com/nodejs/Release/issues/511) 25 | * Discussed at the Node.js Collaborator Summit release session 26 | * Active releasers set up/host regular meetings to allow shadowing 27 | * Few persons interested in contributing/attending these meetings so far 28 | * (Myles) I want to help with this. We should pick some times as a working group. 29 | * Use regular slot scheduled by Myles 11am EST alternate Tuesday. 30 | * Should steam live to YouTube using Zoom account? 31 | * Ask whether they’d prefer it to be live streamed or a private setting 32 | * Start January 2020 33 | * Node.js Collaborator Summit - Release agenda [#502](https://github.com/nodejs/Release/issues/502) 34 | * Summary in issue. 35 | * "Current" should include v12.13 [#495](https://github.com/nodejs/Release/issues/495) 36 | * Aim to cut the major current release first on a best effort basis. 37 | * We cannot make guarantees about which release comes first at the moment. 38 | * Defining a word for all current releases [#359](https://github.com/nodejs/Release/issues/359) 39 | * ‘Supported’ term discussed at collaborator summit was deemed appropriate. 40 | * (Action) Glossary on README.md of the terms. 41 | * (Action) Update Releases section on website. 42 | 43 | * Review schedule dates 44 | * (Myles) Do people feel comfortable with out-of-band releases? 45 | * Yes. 46 | * Keep in mind the Docker team, potentially investigate automation of the Docker process. 47 | * Schedules updated. 48 | * Change the release candidate baking time in the v10.x and v12.x schedule from 1 week to 2 weeks. 49 | 50 | ## Q&A, Other 51 | 52 | * Broken test on v12.x on FreeBSD. Bisect required. 53 | * (Myles) We should draft policy on running CI on releases. [#515](https://github.com/nodejs/Release/issues/515) 54 | 55 | ## Upcoming Meetings 56 | 57 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 58 | 59 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 60 | 61 | -------------------------------------------------------------------------------- /doc/meetings/2020-01-16.md: -------------------------------------------------------------------------------- 1 | # Node.js Foundation Release WorkGroup Meeting 2020-01-16 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=pMMYKUI1DKM&t=212s 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/521 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1WBxp_mVW0AdjWguNVqBoIX1M4PDUYJuGV_0R6HDaV2s 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Chengzhong Wu (@legendecas) 13 | * Michaël Zasso (@targos) 14 | * Owen Buckley (@thescientist13) 15 | * Richard Lau (@richardlau) 16 | * Ruben Bridgewater (@BridgeAR) 17 | * Shelley Vohr (@codebytere) 18 | 19 | ## Agenda 20 | 21 | ## Announcements 22 | 23 | *Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 24 | 25 | ### nodejs/node 26 | 27 | * v12.15.0 release proposal [#31368](https://github.com/nodejs/node/pull/31368) 28 | * On the agenda to review the minors. 29 | * It is hard to pin it down to an actual set of criteria - we kind of just gauge how stable we feel that feature is and just make sure we've got all of the bug fixes that come along with it. 30 | * What we've done before and is create list of minors for us to all just look at and go through. 31 | * (@targos) What I will do is prepare the notable changes section which will mention all of the semver minors and I will mention the release team to review that. 32 | * There's an HTTP parser patch in the release proposal, I think there were plans to pull that patch into its own release. 33 | * Minors for v12.15.0 - https://gist.github.com/BridgeAR/01d9773427147d531f050dc067387c02 34 | * (@targos) I will update this proposal after. 35 | 36 | ### nodejs/Release 37 | 38 | * Node.js Release mentoring/streaming [#511](https://github.com/nodejs/Release/issues/511) 39 | * First session we went through the release process and showed attendees the process of actually deploying a release. 40 | * All attendees were happy for that to be streamed live to YouTube so it is something that we will be able to record and then refer back to it. 41 | 42 | * Defining a word for all current releases [#359](https://github.com/nodejs/Release/issues/359) 43 | * There is a PR open in the Release repository 44 | * Myles suggested that we take a look at the content in the release plan section to make sure we're not duplicating anything. 45 | * Sam opened an issue mentioning he felt that documentation was fragmented across the nodejs/node and the nodejs/release repository. 46 | * (@richardlau) I kind of feel that the schedule should stay where it is especially since other things refer to it. I have no real objections if bits of the process were moved over. 47 | 48 | ## Q&A, Other 49 | 50 | * (@richardlau) We’ve added the option now so that you can run the `citgm-smoker-nobuild` against release candidates and v8 canary. 51 | * (@BethGriggs) Ashley Cripps has added a v10.x and v12.x version specific job to Jenkins. We should trial and see how much having these dedicated jobs benefit us. 52 | 53 | ## Upcoming Meetings 54 | 55 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 56 | 57 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 58 | 59 | 60 | -------------------------------------------------------------------------------- /doc/meetings/2020-01-30.md: -------------------------------------------------------------------------------- 1 | # Node.js Foundation Release WorkGroup Meeting 2020-01-30 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=GEgW0RA3qIQ 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/527 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1B3yr0blBOWrn0-h39UtPQRavtZsEHxt12_AuAiXTbLE 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Richard Lau (@richardlau) 13 | * Shelley Vohr (@codebytere) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | *Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 20 | 21 | ### nodejs/node 22 | 23 | * v12.15.0 release proposal [#31368](https://github.com/nodejs/node/pull/31368) 24 | * Delayed to 11th February due to security releases. 25 | * Reviewed the minors. 26 | * v12.x-proposal CI was failing due to a recent commit landing. 27 | 28 | ### nodejs/Release 29 | 30 | * Defining a word for all current releases [#359](https://github.com/nodejs/Release/issues/359) 31 | * PR needs updating. 32 | * Please review. 33 | 34 | ## Q&A, Other 35 | 36 | * PR was opened to drop "foundation" from the Release Working Group name. 37 | * Aim to define a policy for releasers running CI. 38 | * Node.js Release mentoring/streaming is still happening at 11 EST alternate Tuesdays (scheduled in https://nodejs.org/calendar), 39 | * Pushed v12.16.1 back by one week due to security release timing. 40 | 41 | ## Upcoming Meetings 42 | 43 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 44 | 45 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 46 | -------------------------------------------------------------------------------- /doc/meetings/2020-02-27.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2020-02-27 2 | 3 | ## Links 4 | 5 | * **Recording**: http://www.youtube.com/watch?v=qTRg0SgruKY 6 | * **GitHub Issue**: https://github.com/nodejs/release/issues/539 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1G_k11gEhIR5C3KEuJiF9p54r-Mh_OrZEvjKHGK0YdF0 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Darcy Clarke (@darcyclarke) 13 | * Michaël Zasso (@targos) 14 | * Myles Borins (@MylesBorins) 15 | * Ruben Bridgewater (@BridgeAR) 16 | * Shelley Vohr (@codebytere) 17 | 18 | ## Agenda 19 | 20 | ## Announcements 21 | 22 | *Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 23 | 24 | ### nodejs/Release 25 | 26 | * v12.16.0 post-mortem [#536](https://github.com/nodejs/Release/issues/536) 27 | * (@MylesBorins) **Bugs introduced**: 28 | * Package resolution 29 | * V8 wasm 30 | * Large pages breaking builds 31 | * Change to async hooks 32 | * EventEmitter enumerablity 33 | * **Ideas on how to avoid issues like this in the future**: 34 | * Encourage more people to test the release candidates. 35 | * Pull requests for significant conflicts? (ESM?). 36 | * Document and provide links to issues/bugs on the PR itself (including in build systems). 37 | * `backport-blocked-x` label should be added. 38 | * Let things bake longer, especially around holidays. 39 | * Introduce policy around enumerability of enums. 40 | 41 | * Working out a policy around reverts for LTS branches - [#535](https://github.com/nodejs/Release/issues/535) 42 | * (@BethGriggs & @MylesBorins) to post back on issue itself AND/OR document guidelines in nodejs/release README.md. 43 | * (@MylesBorins) We should create a folder for documents/guidelines. 44 | 45 | * Defining a word for all current releases - [#359](https://github.com/nodejs/Release/issues/359) 46 | * (@BethGriggs) Will update the PR & try to get it merged in. 47 | 48 | ### nodejs/node 49 | 50 | * v10.20.0 release - [#31984](https://github.com/nodejs/node/pull/31984) 51 | * (@BethGriggs) Pushing to get release out for mid-March. 52 | * (@MylesBorins) Tweet about/question community about usage of 10.x and ask about feature requests. 53 | * (@MylesBorins) Fast follow this release with a semver patch release. 54 | * (@MylesBorins) Do a triage of open issues/PRs labelled `v10.x`. 55 | 56 | ## Q&A, Other 57 | 58 | * (@MylesBorins) increase RC timelines for `v12.x` (?) 59 | * (@BethGriggs) `v10.19.0` aim for mid-March but may change based on feedback. 60 | * (@BethGriggs) Release training/sessions are still happening on Tuesdays - can be found in the nodejs.org calendar. 61 | 62 | ## Upcoming Meetings 63 | 64 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 65 | 66 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. -------------------------------------------------------------------------------- /doc/meetings/2020-03-12.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2020-03-12 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=eTMv2pQIKfU 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/546 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1AuGvlqPg_XVihWPFOaOJKYeXD8wDZN3DKyQeYQFtY9w/edit 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Darcy Clarke (@darcyclarke) 13 | * Michael Zasso (@targos) 14 | * Myles Borins (@mylesborins) 15 | * Richard Lau (@richardlau) 16 | * Shelley Vohr (@codebytere) 17 | 18 | ## Agenda 19 | 20 | ## Announcements 21 | 22 | * Nominating Richard Lau (@richardlau) for the LTS and backporters team [#550](https://github.com/nodejs/Release/issues/550) 23 | 24 | ### nodejs/Release 25 | 26 | * Working out a policy around reverts for LTS branches [#535](https://github.com/nodejs/Release/issues/535) 27 | * Discussed last meeting - no specific actions. 28 | * Should it be reverted on master first, and then bubble down to LTS? 29 | * Consensus was that we should decide on a case-by-case basis. 30 | * Documentation on what we should do if a release has a confirmed bug. 31 | * Potentially including raising an issue on Release repository when something goes wrong. 32 | * We should aim to revert PRs in master as soon as possible. 33 | 34 | * Dropping the backporters team - [#547](https://github.com/nodejs/Release/issues/547) 35 | * Myles suggestion in [#547](https://github.com/nodejs/Release/issues/547#issuecomment-596644900) 36 | * We’re currently mixing the model of IAM and working streams. 37 | * We want to encourage more people backporting. 38 | * Should more than just releasers/backporters land on staging branches? 39 | * At the moment it’s a small group so we don’t conflict with each other when landing PRs on staging branches and backports. 40 | * Bottleneck is the time it takes for backport PRs. 41 | * Do we want the LTS team to be able to have an opinion on what should land without having access to land PRs on staging branches? 42 | * The questions we’re trying to answer are: 43 | * Who has permission to land things on the branches? 44 | * And who can participate in the discussions? 45 | 46 | ## Q&A, Other 47 | 48 | * The definition of done is currently when a commit lands on master - maybe we should change this? 49 | * (Shelley) Checks API to show if a PR will land cleanly on LTS branches. 50 | * (Richard) Is there a risk of alienating drive-by contributors? 51 | * (Shelley) Doesn’t need to block merge. 52 | * (Myles) We could show through labels - we already use `backport-requested` labels. 53 | * (Myles) We want to avoid premature backports. 54 | * (Beth) Does this mean backports could be raised before the LTS team has audited eligibility? 55 | * (Richard) We should work on the flow. 56 | * **Action**: Raise an issue to discuss flow and/or prototype. 57 | 58 | * Create an offboarding document [#542](https://github.com/nodejs/Release/issues/542) 59 | * `node-core-utils` now has an option for landing backports `git node land --backport` 60 | * Shelley is working on automating the steps involved with creating release commits in `node-core-utils` 61 | * Call for releasers to try it out and review. 62 | 63 | ## Upcoming Meetings 64 | 65 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 66 | 67 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 68 | 69 | 70 | -------------------------------------------------------------------------------- /doc/meetings/2020-03-26.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2020-03-26 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=kE1mY_k5oW4 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/554 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/13UUieF1pladFX4ZGk5FSCI6Xwy1MWjF_wnm6p8c4JGw 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Darcy Clarke (@darcyclarke) 13 | * Richard Lau (@richardlau) 14 | * Ruy Adorno (@ruyadorno) 15 | * Shelley Vohr (@codebytere) 16 | * Michaël Zasso (@targos) 17 | * Myles Borins (@MylesBorins) 18 | 19 | ## Agenda 20 | 21 | ## Announcements 22 | 23 | *Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 24 | 25 | ### nodejs/Release 26 | 27 | * Release cadence due to COVID-19 Pandemic [#553](https://github.com/nodejs/Release/issues/553) 28 | * Extra importance on stability to reduce impact on downstream consumers. 29 | * Agreed to keep v14.x release as planned. 30 | * v13.x to keep the same cadence to keep getting new features out to users. 31 | * Updated the v13.x, v12.x, v10.x release schedules. 32 | * v12.16.2 and v10.20.0 delayed until 7th April 2020. 33 | * [Drafting formal communications](https://docs.google.com/document/d/1Uf6ANHYJLVQpecgWCFGm94ZbvtYC8Ou0jYF8BtuLHSs/edit) 34 | 35 | * Suggestion: drop backporters team? [#547](https://github.com/nodejs/Release/issues/547) 36 | * Restructuring the Release teams will hopefully have a side effect that more people can get involved. 37 | * First step to rename the CITGM team to `release-automation` team that has permissions on `changelog-maker`, `branch-diff`, `node-core-utils`. 38 | * (Action) To create an issue covering the change. 39 | 40 | * Working out a policy around reverts for LTS branches [#535](https://github.com/nodejs/Release/issues/535) 41 | * (Action) Create issue to cover writing a “Broken Release” action plan. 42 | 43 | * Publish a debug version when making a new release [#555](https://github.com/nodejs/Release/issues/555) 44 | * Release team recommendation that this is first handled under unofficial-builds project. 45 | * @MylesBorins mentions that he may be able to support storage via Google Credits. 46 | 47 | ## Q&A, Other 48 | 49 | ## Upcoming Meetings 50 | 51 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 52 | 53 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 54 | 55 | 56 | -------------------------------------------------------------------------------- /doc/meetings/2020-04-09.md: -------------------------------------------------------------------------------- 1 | # Node.js Release Working Group Meeting 2020-04-09 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=6ZAAIHiaRdc 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/564 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1usc9LfhioWNq1d3YmiLlsrdcRmDEXpuZjMFb5Ue7Gpo 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Michael Zasso (@targos) 13 | * Myles Borins (@MylesBorins) 14 | * Richard Lau (@richardlau) 15 | * Ruben Bridgewater (@BridgeAR) 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | * All new releases are now notarized on macOS. 22 | 23 | ### nodejs/Release 24 | 25 | * Release cadence due to COVID-19 Pandemic [#553](https://github.com/nodejs/Release/issues/553) 26 | * Blog available at https://nodejs.org/en/blog/announcements/adjusted-release-schedule-covid/ 27 | * Continue to review the schedule. 28 | 29 | ## Q&A, Other 30 | 31 | * Node.js 14 - [#567](https://github.com/nodejs/Release/issues/567) 32 | * Due 21st April. 33 | * Build updating toolchains and compilers. 34 | * Foundation requesting a blog/marketing. 35 | * Node.js 13 - [#487](https://github.com/nodejs/Release/issues/487) 36 | * 2 more releases. 37 | * Last release after Node.js 14 will be patches only. 38 | * Node.js 12 - [#494](https://github.com/nodejs/Release/issues/494) 39 | * Patch release due in April 40 | * No volunteers as yet, but will try to land commits on staging. 41 | * Make a call if there’s enough on staging to push out a release in April. 42 | * Node.js 10 - [#504](https://github.com/nodejs/Release/issues/504) 43 | * Final release scheduled for early May, if required. 44 | 45 | * OpenSSL 1.1.1f - may require releases of v10.x and v12.x. 46 | 47 | * Action to rename CITGM team to release-automation to go ahead. - [#557](https://github.com/nodejs/Release/issues/557) 48 | 49 | * Drop backporters team - [#547](https://github.com/nodejs/Release/issues/547) 50 | * We do not have clear criteria for joining the LTS team. 51 | * Nomination or self-nomination. 52 | * In the proposal LTS would take the place of the `backporters` team. 53 | 54 | * Changelog changes - [#568](https://github.com/nodejs/Release/issues/568) 55 | * Ideal if the author could write the notable change section, but unlikely to happen based on the usage of the notable change label. 56 | * Suggestion to create a Google doc to collaborate on notable changes. 57 | * Suggestion to separate out test changes, and some doc changes to make the changelog more readable for end users. 58 | * Remove labels from individual commits that are not major or minor. 59 | * Suggestion to add semverness to the commit message. 60 | 61 | 62 | ## Upcoming Meetings 63 | 64 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 65 | 66 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 67 | 68 | 69 | -------------------------------------------------------------------------------- /doc/meetings/2020-05-07.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2020-05-07 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=RumIGFMlW-I 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/575 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1e1rBRaB3f_rmByQpYKmEMcrnsQBmKOQK8k03YB-G8d8 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Michaël Zasso (@targos) 13 | * Myles Borins (@MylesBorins) 14 | * Richard Lau (@richardlau) 15 | * Ruben Bridgewater (@BridgeAR) 16 | * Ruy Adorno (@ruyadorno) 17 | * Shelley Vohr (@codebytere) 18 | 19 | ## Agenda 20 | 21 | ## Announcements 22 | 23 | ### nodejs/Release 24 | 25 | * Release plan - v14.x Current [#567](https://github.com/nodejs/Release/issues/567) 26 | * Releasers scheduled up until June. 27 | * Regression on Windows on v14.1.0 [nodejs/node#33166](https://github.com/nodejs/node/issues/33166) 28 | 29 | ## Q&A, Other 30 | 31 | * Changelog changes - [#568](https://github.com/nodejs/Release/issues/568) 32 | * Demonstrated in @targos [v12.17.0-proposal](https://github.com/nodejs/node/pull/33197). 33 | * Includes pinging PR authors to provide descriptions. 34 | * May need to open drafts a bit earlier. 35 | * All agreed it is a great improvement. 36 | * Formalize this format in `releases.md`. 37 | * Potentially edit `changelog-maker` to output the changelog in this format. 38 | 39 | * ESM unflagging in v12.x 40 | * Concern there is no escape hatch and may change behavior. 41 | * Okay with the risk. 42 | * Modules can release fixed versions. 43 | * Potential to add a flag to revert the unflagging of ESM, if necessary. 44 | 45 | * Morocco time zone changes - [#576](https://github.com/nodejs/Release/issues/576) 46 | * Requires a patch on all release lines. 47 | * @codebytere volunteered. 48 | * Will not do a dedicated release, but will bundle up with other changes. 49 | * Potentially automate this. 50 | 51 | * Nominating @BridgeAR for LTS team - [#565](https://github.com/nodejs/Release/issues/565) 52 | * Needs to be added to the team and the README updated. 53 | 54 | * Release automation, is there a specific provider we should use? 55 | * Personal preference/resources is okay. 56 | * If/when we choose to integrate we’d coordinate with @nodejs/build. 57 | 58 | * Release session at OpenJS Summit? 59 | * Agreed that we do not need the additional time. 60 | * Maybe publicize the mentoring sessions. 61 | 62 | ## Upcoming Meetings 63 | 64 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 65 | 66 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. -------------------------------------------------------------------------------- /doc/meetings/2020-05-21.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2020-05-21 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=yh0_euMCJzw 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/579 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1RM6m2obvMUSrV2cY5tQJX8UMGVvS-dDmuhNQzevrazM 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Myles Borins (@MylesBorins) 13 | * Richard Lau (@richardlau) 14 | * Ruy Adorno (@ruyadorno) 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | *Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 21 | 22 | ### nodejs/Release 23 | 24 | * Release plan - v14.x Current [#567](https://github.com/nodejs/Release/issues/567) 25 | * Schedule covered up until mid-June 26 | * Imminent issue for Morocco users (tzdata2020a) [#576](https://github.com/nodejs/Release/issues/576) 27 | * Likely missed the window to avoid impact 28 | * Now aiming for it to flow into the next release on each release line 29 | * Will update the issue and ask if there are any objections 30 | * npm v7 in Node.js 14 - [nodejs/tsc#869](https://github.com/nodejs/TSC/issues/869) 31 | * A few subtle but potentially breakings changes for the ecosystem 32 | * npm is widely used in build/deploy pipelines, we need to be cautious 33 | * (Ruy) beta is aiming for summer 34 | * Suggestion to wait until we can get feedback from beta before making any decisions 35 | * Users can update npm - this is just about what gets bundled by default 36 | * Interested in whether npm v6 will be maintained 37 | 38 | ## Q&A, Other 39 | 40 | * Many documentation issues in the release repository 41 | * CITGM membership audit to be done before we rename to ‘release-automation’ 42 | 43 | ## Upcoming Meetings 44 | 45 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 46 | 47 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 48 | 49 | -------------------------------------------------------------------------------- /doc/meetings/2020-07-02.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2020-07-02 2 | 3 | ## Links 4 | 5 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/589 6 | * **Minutes Google Doc**: https://docs.google.com/document/d/1ra7sb0afuc2MI064BETPhmChnVCWxtuUQtw9FLOW5Hg 7 | 8 | ## Present 9 | 10 | * Beth Griggs (@BethGriggs) 11 | * Darcy Clarke (@darcyclarke) 12 | * Myles Borins (@MylesBorins) 13 | * Richard Lau (@richardlau) 14 | * Ruy Adorno (@ruyadorno) 15 | 16 | ### nodejs/Release 17 | 18 | * Release plan - v14.x Current [#567](https://github.com/nodejs/Release/issues/567) 19 | * npm v6 patch update 20 | * If there is an update soon, it should be able to make it into LTS releases due 21st July. 21 | * npm v7 22 | * @richardlau suggested landing the beta (when it is released) on master to enable it to be built into nightlies. 23 | * ETA for release is September 24 | * v15.x - should go out with npm v7. 25 | * v14.x - Tentative as to whether it should land just before it enters LTS. 26 | * Having the beta on master gives it more time to bake and gather user feedback to enable us to make this call. 27 | * v12.x - Tentative as to whether it should land just before maintenance. 28 | * Suggestion to extend Active LTS by a short while. 29 | * Add npm to our maintenance exceptions, like N-API. 30 | 31 | -------------------------------------------------------------------------------- /doc/meetings/2020-07-16.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2020-07-16 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=PtzHFPHfXd4 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/593 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1zR5W9f24tldrXCfuCYgYms1FrK8oQfEN0oCaZvsat2k 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Danielle Adams (@danielleadams) 13 | * Darcy Clarke (@darcyclarke) 14 | * Myles Borins (@MylesBorins) 15 | * Richard Lau (@richardlau) 16 | * Ruy Adorno (@ruyadorno) 17 | 18 | ## Agenda 19 | 20 | ## Announcements 21 | 22 | * Welcome to new collaborators 23 | * Danielle, Ruy, Stewart 24 | * Upcoming v14.x release with a V8 8.4 25 | 26 | ### nodejs/Release 27 | 28 | * Release plan - v14.x Current [#567](https://github.com/nodejs/Release/issues/567) 29 | * Edited schedule to include pairing with new releasers. 30 | * Release plan - v12.x LTS 31 | * Upcoming v12.x on 21st July. 32 | * August v12.x release needs a volunteer. 33 | * Release plan - v10.x LTS 34 | * Upcoming v10.x on 21st July. 35 | * Agreed to leave the schedule issue open. 36 | * v14.x V8 update prior to LTS 37 | * (Action) Need to figure out V8 timelines. 38 | * Need to consider if it is worth delaying v15.x. 39 | * npm 7 40 | * Working on a breaking changes document. 41 | * Key breaking change is to peer dependencies. 42 | * Considering a legacy install flag. 43 | * Considering both an npm 7 and npm 8 release. 44 | * Still aim to land the beta in master as unstable. 45 | * (Action) Open an issue in core to open the discussion. 46 | -------------------------------------------------------------------------------- /doc/meetings/2020-08-13.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2020-08-13 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=u0FEOS_TgSw 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/599 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1I5ZJ5spDLIPEJYEOi5uOIfmAb0e9w-7VxFf2wloMJMg 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Myles Borins (@MylesBorins) 13 | * Richard Lau (@richardlau) 14 | * Ruy Adorno (@ruyadorno) 15 | * Darcy Clarke (@darcyclarke) 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | * v14.8.0 came out with top-level await 🎉 22 | 23 | ### nodejs/node 24 | 25 | * Special treatment for package.json resolution and exports? [#33460](https://github.com/nodejs/node/issues/33460) 26 | * A user has raised a concern in v12.x. 27 | * Discussed in previous release and TSC meetings. 28 | * (Richard) Is there more we could have done? 29 | * Potentially better error messages? 30 | * An improvement to how we communicated the change? 31 | * (Myles) More disruptive to revert the removal of the flag now. 32 | * (Action) Richard to respond in the issue. 33 | 34 | ### nodejs/Release 35 | 36 | * "Current" should include v12.13 - [#495](https://github.com/nodejs/Release/issues/495) 37 | * Agreed LTS transition can happen 1 week after the new current is released. 38 | * (Action) Beth to update PR. 39 | * Review the release schedules 40 | * Rescheduled August v12.x minor. -------------------------------------------------------------------------------- /doc/meetings/2020-08-27.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2020-08-27 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=v_kKaF3uBQA 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/606 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1ACjcYd3vh7CM1Bws2OpTriNHC-OVGqVGFjgryQ9twVU 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Myles Borins (@MylesBorins) 13 | * Richard Lau (@richardlau) 14 | * Ruy Adorno (@ruyadorno) 15 | * Shelley Vohr (@codebytere) 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | * v14.9.0 released today! 22 | 23 | 24 | ### nodejs/node 25 | 26 | * Special treatment for package.json resolution and exports? [#33460](https://github.com/nodejs/node/issues/33460) 27 | * Action to post a comment on the issue. 28 | 29 | 30 | ### nodejs/Release 31 | 32 | * Confusion regarding “Maintenance LTS” status 33 | [#605](https://github.com/nodejs/Release/issues/605) 34 | * Terminology is subjective. 35 | * End-of-life means no more fixes. 36 | * Beth to bring to Package Maintenance to see if our recommendations align (or at least do not contradict). 37 | * Proposal: Slack channel for Release WG? [#607](https://github.com/nodejs/Release/issues/607) 38 | * Myles created a `#nodejs-release` channel in the OpenJS Slack (https://openjs-foundation.slack.com/). 39 | * Sign up via https://slack-invite.openjsf.org. 40 | * Release plan - v14.x Current [#567](https://github.com/nodejs/Release/issues/567) 41 | * Scheduled until October. 42 | -------------------------------------------------------------------------------- /doc/meetings/2020-09-10.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2020-09-10 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=VL81-HzFCH8 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/609 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1cLn6gMwS9twX9B-hz3YQmMEJ4toiw5XnCkkLuh0Ab2s 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Richard Lau (@richardlau) 13 | * Michael Zasso (@targos) 14 | * Myles Borins (@MylesBorins) 15 | * Ruy Adorno (@ruyadorno) 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | * v14.10.1 due out today to fix a regression in v14.10.0. 22 | * Security releases due next Tuesday. 23 | * Major cut-off for v15.0.0 is 22nd September 2020. 24 | 25 | ### nodejs/node 26 | 27 | * doc: update backport requirements on LTS lines [#35058](https://github.com/nodejs/node/pull/35058) 28 | * Audit between Active LTS and Maintenance? 29 | * Concern we’re adding too much process to solve a rare problem. 30 | * Add a note to the backporting guide? 31 | * Agreed to just delete the `backport-requested-vN.x` label when a release transitions to maintenance. 32 | * Special treatment for package.json resolution and exports? [#33460](https://github.com/nodejs/node/issues/33460) 33 | * Action to post a comment on the issue. 34 | 35 | ### nodejs/Release 36 | 37 | * Release plan - v14.x Current [#567](https://github.com/nodejs/Release/issues/567) 38 | * Scheduled up until October. 39 | * Release plan - v12.x Active LTS [#494](https://github.com/nodejs/Release/issues/494) 40 | * No volunteers as yet. 41 | * Richard tentatively volunteered. 42 | * Dates would need to be changed to account for the onboarding rules around promoting an LTS release. 43 | 44 | ## Q&A, Other 45 | 46 | * Node.js v15.0.0 47 | * Major cut-off is 22nd September 2020. 48 | * Ran a few test builds. 49 | * Release candidates coming soon. 50 | * `umask()` runtime deprecation may cause ecosystem disruption. 51 | * Consider hiding the warning in dependencies. 52 | * Consider reverting the runtime deprecation? 53 | 54 | * Should we reconsider the Active LTS and Maintenance timeframes? 55 | * Already have less availability to produce Node.js 12 releases. 56 | * Continue to evaluate. 57 | * No immediate changes. 58 | 59 | -------------------------------------------------------------------------------- /doc/meetings/2020-09-24.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2020-09-24 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=eas8a3c4oEU 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/611 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1OZOOMYOVqrWJOu7AGr5QWo5nz1sduinMIaVf5gDcd20 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Danielle Adams (@danielleadams) 13 | * Michael Zasso (@targos) 14 | * Richard Lau (@richardlau) 15 | * Ruy Adorno (@ruyadorno) 16 | * Shelley Vohr (@codebytere) 17 | 18 | ## Agenda 19 | 20 | ## Announcements 21 | 22 | * Security releases went out in September. 23 | * https://nodejs.org/en/blog/vulnerability/september-2020-security-releases/ 24 | * Node.js 15 is due to be released 20th October. 25 | * First release candidate is out - https://nodejs.org/download/rc/v15.0.0-rc.0/ 26 | 27 | ### nodejs/Release 28 | 29 | * Release plan - v14.x Current [#567](https://github.com/nodejs/Release/issues/567) 30 | * Potentially squeeze an extra release in next week to pick up modules changes to allow more baking time between them landing in v14.x and v12.x. 31 | * Release plan - v12.x Active LTS [#494](https://github.com/nodejs/Release/issues/494) 32 | * Shelley volunteered for v12.19.0. 33 | * Two further releases scheduled until maintenance, we will readdress timings once the modules changes have landed. 34 | * Release plan - v10.x Maintenance [#504](https://github.com/nodejs/Release/issues/504) 35 | * N-api backport: https://github.com/nodejs/node/pull/35266 36 | * Review PRs labeled `lts-watch-v10.x` in an effort to try and build up a few commits on staging. 37 | * If no further PRs in ~1month, we’ll do a release for just the two open v10.x backport PRs. 38 | 39 | ## Q&A, Other 40 | 41 | * Zoom links in the Node.js Foundation Calendar entry are incorrect 42 | * Richard: CITGM will be fixed to unbreak Windows on the CI. May start seeing “new” failures that we weren’t previously aware of as the CI on Windows was exiting early and not publishing results. 43 | -------------------------------------------------------------------------------- /doc/meetings/2020-10-08.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2020-10-08 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=IB3JFPA1teU 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/615 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1dSWepXPFXC6BnugLANFkTt_kfUhI_ugcDo2Fmk5f_xo 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Richard Lau (@richardlau) 13 | * Ruy Adorno (@ruyadorno) 14 | * Michael Zasso (@targos) 15 | * Myles Borins (@MylesBorins) 16 | * Shelley Vohr (@codebytere) 17 | 18 | ## Agenda 19 | 20 | ## Announcements 21 | 22 | * Second Node.js 15 release candidate is available - https://nodejs.org/download/rc/v15.0.0-rc.1/ 23 | * v14.13.1 was released yesterday - https://nodejs.org/en/blog/release/v14.13.1/ 24 | 25 | ### nodejs/Release 26 | 27 | * Release plan - v15.x Current 28 | * Create a release plan issue with a two-week cadence. 29 | * Release plan - v14.x Current [#567](https://github.com/nodejs/Release/issues/567) 30 | * Next release is 27th October - First LTS Release. 31 | * Create the Active LTS release plan (1 minor per quarter). 32 | * Release plan - v12.x [#494](https://github.com/nodejs/Release/issues/494) 33 | * Timeline for final v12.x semver minor [#616](https://github.com/nodejs/Release/issues/616) 34 | * Agreed to extend Active LTS by 1 month until the end of November. (PR to be opened). 35 | * Final semver minor to be in November, ETA 2020-11-17. 36 | * Release plan - v10.x [#504](https://github.com/nodejs/Release/issues/504) 37 | * v10.24.0 scheduled for 2020-10-27. Mainly for N-API updates (N-API 7 and a missing build variable). 38 | 39 | ## Q&A, Other 40 | * For awareness Windows installers on the most recent releases are being flagged as unsafe, most probably due to the change in signing certificate (the old one was expiring, https://github.com/nodejs/build/issues/2415): https://github.com/nodejs/node/issues/35539 41 | -------------------------------------------------------------------------------- /doc/meetings/2020-11-05.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2020-11-05 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=FGogMwqkFxQ 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/626 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1ZqjUIvR053mpCG5YaTqrQdP63LdBGcso9W4RmtBQFXk 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Danielle Adams (@danielleadams) 13 | * Myles Borins (@MylesBorins) 14 | * Richard Lau (@richardlau) 15 | * Ruy Adorno (@ruyadnorno) 16 | * Tierney Cyren (@bnb) 17 | 18 | ## Agenda 19 | 20 | ## Announcements 21 | 22 | * None. 23 | 24 | ### nodejs/Release 25 | 26 | * Release plan - v15.x Current [#621](https://github.com/nodejs/Release/issues/621) 27 | * Scheduled until December. 28 | * Release plan - v14.x Active LTS [#567](https://github.com/nodejs/Release/issues/567) 29 | * Action to update the release plan. 30 | * Ruy expressed interest in doing a v14.x release. 31 | * Release plan - v12.x Active LTS [#494](https://github.com/nodejs/Release/issues/494) 32 | * Myles is preparing the next v12.x - delayed by 1 week. 33 | * Release plan - v10.x Maintenance [#504](https://github.com/nodejs/Release/issues/504) 34 | * No release needed at this time. 35 | 36 | ## Q&A, Other 37 | 38 | * Changelog changes [#568](https://github.com/nodejs/Release/issues/568) 39 | * Would like to have but hope they’re implemented in `changelog-maker`. 40 | * Release WG structure changes 41 | * Aim should open a proposal and try to move forward on that. 42 | 43 | ## Upcoming Meetings 44 | 45 | * **Node.js Foundation Calendar**: https://nodejs.org/calendar 46 | -------------------------------------------------------------------------------- /doc/meetings/2020-12-03.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2020-12-03 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=Vdf2eejrYIY 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/630 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/14osmYWWjSEvUbqVF-1z6NYr8jbE4x2WF6k4uZtFlhWo 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Danielle Adams (@danielleadams) 13 | * Richard Lau (@richardlau) 14 | * Shelley Vohr (@codebytere) 15 | 16 | ## Agenda 17 | 18 | ### nodejs/Release 19 | 20 | * Release plan - v15.x Current [#621](https://github.com/nodejs/Release/issues/621) 21 | * Volunteers up until January. 22 | * Release plan - v14.x Active LTS [#567](https://github.com/nodejs/Release/issues/567) 23 | * (Beth) Working on a release, date TBD but aiming for December. 24 | * Release plan - v12.x Maintenance [#494](https://github.com/nodejs/Release/issues/494) 25 | * No pressing patches requiring release at this time. 26 | * Release plan - v10.x Maintenance [#504](https://github.com/nodejs/Release/issues/504) 27 | * No pressing patches requiring release at this time. 28 | 29 | ## Q&A, Other 30 | 31 | * Revamping the LTS Schedule - https://github.com/nodejs/node/discussions/36165 32 | * Initial discussion within Release WG about the various options presented. 33 | * Concerns regarding time to upgrade between versions already being too short. 34 | * Would be good to obtain Node.js download statistics (work in progress). 35 | * (Danielle) Offer to obtain some usage stats. 36 | * Suggestion to review LTS policies of other projects (Angular, etc.). 37 | * Would like to hear more about the problem statement with examples of the problematic patches. 38 | * It’s not clear how the options presented solve the issues mentioned as we’d still need to create security patches for the oldest release line (which is likely to have diverged). 39 | * Only considering changing the LTS policy for future versions. 40 | * It would be preferable to have any changes agreed a couple of months prior to Node.js 16 to allow time to socialise. 41 | * (Beth) Offer to generate some timeline images to make it easier to interpret the suggestions. 42 | -------------------------------------------------------------------------------- /doc/meetings/2021-01-14.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2021-01-14 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=12LHRUmUFKo 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/638 7 | 8 | ## Present 9 | 10 | * Beth Griggs (@BethGriggs) 11 | * Danielle Adams (@danielleadams) 12 | * Richard Lau (@richardlau) 13 | * Ruy Adorno (@ruyadorno) 14 | 15 | ## Agenda 16 | 17 | ### nodejs/Release 18 | 19 | * Set up Release WG meetings [#637](https://github.com/nodejs/Release/issues/637) 20 | * Doodle results so far indicate that 1500 UTC is a suitable time. 21 | * (Action) Beth to update all calendar invites to be 1500 UTC. 22 | * Backporting Release key README changes to nodejs/node version branches [#595](https://github.com/nodejs/Release/issues/595) 23 | * Easiest way to ensure we do not forget is to cherry-pick the key on to all active release branches after it has landed on main. 24 | * (Action) Richard to raise a PR to document. 25 | * Release plan - v15.x Current [#621](https://github.com/nodejs/Release/issues/621) 26 | * Scheduled up until mid-February. 27 | * Release plan - v14.x Active LTS [#567](https://github.com/nodejs/Release/issues/567) 28 | * Delayed semver minor release to February to account for release candidate time. 29 | * Aim to release npm 6 patch update on 2021-01-26 30 | * Release plan - v12.x Maintenance [#494](https://github.com/nodejs/Release/issues/494) 31 | * Aim to release npm 6 patch update on 2021-01-26 32 | * Release plan - v10.x Maintenance [#504](https://github.com/nodejs/Release/issues/504) 33 | * Aim to release npm 6 patch update on 2021-01-26 34 | 35 | 36 | ## Q&A, Other 37 | 38 | * CITGM is showing a number of failures. 39 | * We possibly need to spend some time auditing the flaky and skipped modules. 40 | -------------------------------------------------------------------------------- /doc/meetings/2021-02-11.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2021-02-11 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=n34256avSuU 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/645 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1GfcEbIdD5a4W9QU3fhqh5m3BjEUyEW25KgqagqniB5A 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Danielle Adams (@danielleadams) 13 | * Richard Lau (@richardlau) 14 | * Ruy Adorno (@ruyadorno) 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | * Node.js v14.15.5, v12.20.2, v10.23.3 releases. 21 | 22 | ### nodejs/Release 23 | 24 | * Release plan - v15.x Current [#621](https://github.com/nodejs/Release/issues/621) 25 | * Volunteers for all releases up until the end of March. 26 | * Release plan - v14.x Active LTS [#567](https://github.com/nodejs/Release/issues/567) 27 | * Aiming to do a semver minor in February. 28 | * Release plan - v12.x Maintenance [#494](https://github.com/nodejs/Release/issues/494) 29 | * No pressing patches requiring release at this time. 30 | * Release plan - v10.x Maintenance [#504](https://github.com/nodejs/Release/issues/504) 31 | * No pressing patches requiring release at this time. 32 | * doc: add offboarding releasers guidance [#644](https://github.com/nodejs/Release/pull/644) 33 | * Leave open until we have gathered further reviews. 34 | 35 | ## Q&A, Other 36 | 37 | * Consider endorsing/using Rekor as release ledger [#642](https://github.com/nodejs/Release/issues/642) 38 | * (Action) Ask if the members of the Rekor project could provide an overview for the Node.js Release Working Group. 39 | -------------------------------------------------------------------------------- /doc/meetings/2021-02-25.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2021-02-25 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=Jzm5RmGkgBk 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/648 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1b8xjkbMXPoh-ylHxsdNHqIcEIHVXW2LqEOOioYyssr8 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Danielle Adams (@danielleadams) 13 | * Michael Zasso (@targos) 14 | * Richard Lau (@richardlau) 15 | * Ruy Adorno (@ruyadorno) 16 | * Tierney Cyren (@bnb) 17 | 18 | ## Agenda 19 | 20 | ## Announcements 21 | 22 | * Security releases went out on all active release lines. 23 | * https://nodejs.org/en/blog/vulnerability/february-2021-security-releases/ 24 | 25 | ### nodejs/Release 26 | 27 | * doc: add offboarding releasers guidance [#644](https://github.com/nodejs/Release/pull/644) 28 | * Need to gather a few more reviews. 29 | * Release plan - v15.x Current [#621](https://github.com/nodejs/Release/issues/621) 30 | * Volunteers for all releases up until April. 31 | * Release plan - v14.x Active LTS [#567](https://github.com/nodejs/Release/issues/567) 32 | * SemVer minor release planned, ideally in the March/April timeframe. 33 | * (Action) Land open backport PRs on `v14.x-staging`. 34 | * Release plan - v12.x Maintenance [#494](https://github.com/nodejs/Release/issues/494) 35 | * (Action) Agreed we should do a SemVer minor to get the open backports PRs out, but after Node.js 14 minor. 36 | * Release plan - v10.x Maintenance [#504](https://github.com/nodejs/Release/issues/504) 37 | * No pressing patches requiring release at this time. 38 | * Proposal: New Release Model [#37504](https://github.com/nodejs/node/discussions/37504) 39 | * Release Working Group owns the release policy definition. 40 | * Concern that it would cause more complicated parsing of versions compared to SemVer. 41 | * Backporting to LTS could be improved by either reducing the Active LTS timeframe or making it more of an ‘opt-in’. 42 | * Prefer to tweak the current system rather than radically change it. 43 | * ‘opt-in’ would save a large portion of the effort in preparing a release. 44 | * Impact on consumers. 45 | * (Action) Can we look to the OpenJS Surveys for feedback? 46 | * Surveys/Twitter polls/etc. would still not be representative of all the Node.js consumers. 47 | * There is a demand for features being backported to LTS, from both consumers and contributors. 48 | * Hard to quantify this demand. 49 | * Node.js 16 is only a month and a half away, it’s too late to change for Node.js 16. 50 | * Per our documented process, test/release candidate builds for Node.js 16 would be starting imminently. 51 | * We cannot change course for Node.js 16 based on the proposal, as we do not know when (if at all) any of the proposed changes would be agreed. 52 | * There would not have been adequate time to socialise the change for Node.js 16. 53 | * Keeping the existing model for Node.js 16 relieves the pressure and enables more time to discuss, refine, and socialise the proposal. 54 | * Build and Infrastructure changes. 55 | * Non-zero cost to the Node.js Build Working Group. 56 | * The proposal includes automation, but we need persons to write and maintain that automation. 57 | * We would need a plan on how the two versioning schemes could coexist. 58 | * Proposal should be raised at the Node.js Package Maintenance Working Group too. 59 | * Node.js is an impactful project - by aggressively pushing changes, are we encouraging the ecosystem to evolve in the same way? 60 | * Moving to a release model without emphasis on the SemVer maybe even more complicated to explain. 61 | * Node.js 16 preparations are starting. 62 | * (Beth) Offered pairing for preparation of the major release. 63 | * (Action) Set up a Doodle to find a good time. 64 | 65 | ## Q&A, Other 66 | 67 | * Would it be worth gathering feedback from releasers on the pain-points of preparing a release? 68 | -------------------------------------------------------------------------------- /doc/meetings/2021-03-11.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2021-03-11 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=XDsra0Gw8UM 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/651 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/185beaLWjKvwS68-TWAQ0LalurUlEht8gwqkXw_23yLs 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGrigg) 12 | * Michael Zasso (@targos) 13 | * Myles Borins (@MylesBorins) 14 | * Richard Lau (@richardlau) 15 | * Ruy Adorno (@ruyadorno) 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | * Node.js 16 [#37678](https://github.com/nodejs/node/pull/37678) 22 | * Branches and working draft proposal created. 23 | 24 | ### nodejs/Release 25 | 26 | * Release plan - v15.x Current [#621](https://github.com/nodejs/Release/issues/621) 27 | * Volunteers for all releases up until April. 28 | * Release plan - v14.x Active LTS [#567](https://github.com/nodejs/Release/issues/567) 29 | * Collaborative effort to build up commits on the staging branch. 30 | * Opt-in rather than triaging the whole list. 31 | * Still aiming for the next release to be a minor. 32 | * Should we change the policy to be opt-in? 33 | * Release candidate builds are not well tested - perhaps we could be less strict on the release candidate phase? 34 | * Ask collaborators for feedback on which minors should be included in the next Node.js 14 release. 35 | * (Action) Beth to open a draft proposal for the Node.js 14 minor. 36 | * Release plan - v12.x Maintenance [#494](https://github.com/nodejs/Release/issues/494) 37 | * Aim to include the fs Promises performance improvement when the backport is available. 38 | * Minor planned for the next release. 39 | * Release plan - v10.x Maintenance [#504](https://github.com/nodejs/Release/issues/504) 40 | * No pressing patches requiring release at this time. 41 | * npm@7 in Node.js 14 [#37689](https://github.com/nodejs/node/discussions/37689) 42 | * Consensus is that it is too risky to bring back to Node.js 14. 43 | * npm@6 is in a maintenance state. 44 | * Potentially revisit this discussion before Node.js 14 goes into maintenance. 45 | * Accidental breaking change on v15.7.0 [#37705](https://github.com/nodejs/node/issues/37705) 46 | * A PR has been opened to fix and it should be picked up in the next Node.js 15 release. 47 | * Should we start to treat every addition of a non-writable property to a public object as major? 48 | 49 | ## Q&A, Other 50 | 51 | * Major release process updates. 52 | * Need a build/infrastructure major release checklist. 53 | * Is the major cut-off still necessary? 54 | * In the past few releases, we’ve accepted almost all the majors past the cut-off. 55 | * When there was an objection, the major was reverted. 56 | * Code tends to get frozen 1-week before the release. 57 | * What’s the benefit of a major sitting unreleased on the main branch for 6 months? 58 | * Minor extra testing from contributors. 59 | * (Action) Open a PR for suggested policy changes. 60 | -------------------------------------------------------------------------------- /doc/meetings/2021-04-22.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2021-04-22 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=KYwk6jDAZHE 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/659 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1zxMiU2I26j63SvKKbFjkeWo5jMltZ87s2dQ6Q9aKciU 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Danielle Adams (@danielleadams) 13 | * Michael Zasso (@targos) 14 | * Parris Lucas (@GrooveCS) 15 | * Richard Lau (@richardlau) 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | * Node.js 16 was released on 20th April 2021. 22 | * Prebuilt binaries for Apple Silicon. 23 | * Release CI server required rebuilding before the release. 24 | 25 | ### nodejs/Release 26 | 27 | * Release plan - v16.x Current [#658](https://github.com/nodejs/Release/issues/658) 28 | * New draft/proposed schedule looks good. 29 | * Release plan - v15.x Current [#621](https://github.com/nodejs/Release/issues/621) 30 | * Node.js 15 releases now on an as need basis - critical and security issues only. 31 | * Release plan - v14.x Active LTS [#567](https://github.com/nodejs/Release/issues/567) 32 | * Danielle volunteered. 33 | * Exact timing dependent on availability/time it takes to prepare. 34 | * Okay in this instance to skip the longer release candidate phase to ensure we get the release out. 35 | * Release plan - v12.x Maintenance [#494](https://github.com/nodejs/Release/issues/494) 36 | * No pressing patches requiring release at this time. 37 | * Release plan - v10.x Maintenance [#504](https://github.com/nodejs/Release/issues/504) 38 | * End-of-Life after April 2021. 39 | 40 | ## Q&A, Other 41 | 42 | * Extended the schedule for Node.js 17, 18. 43 | * Same pattern of dates as before. 44 | * Imminent issue for Morocco users (tzdata2020a) - [#576](https://github.com/nodejs/Release/issues/576) 45 | * Can we close this as the issue is no longer imminent? 46 | * Manual backports with compatibility patches [#468](https://github.com/nodejs/Release/issues/468) 47 | * Are we still considering this approach? Should we close? 48 | * Myles added branch protection on staging branches. 49 | * Should we have a Node.js releasers email alias? 50 | * Useful when needing to coordinate security releases. 51 | * (Action) Open an issue to indicate who would like to be on the alias. -------------------------------------------------------------------------------- /doc/meetings/2021-05-20.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2021-05-20 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=t9Skhk8fz24 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/669 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1c9QIi1wV8lkVK8oqsvQHwLYDQfBwXfEd5rtcP-V6fSA/edit 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Danielle Adams (@danielleadams) 13 | * Michael Zasso (@targos) 14 | * Richard Lau (@richardlau) 15 | * Ruy Adorno (@ruyadorno) 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | ### nodejs/Release 22 | 23 | * Release plan - v16.x Current [#658](https://github.com/nodejs/Release/issues/658) 24 | * Volunteers up until the end of June. 25 | * Release plan - v14.x Active LTS [#567](https://github.com/nodejs/Release/issues/567) 26 | * v14.17.0 was released 2021-05-11 27 | * Keep the rest of the schedule as is. 28 | * Release plan - v12.x Maintenance [#494](https://github.com/nodejs/Release/issues/494) 29 | * No pressing patches requiring release at this time. 30 | 31 | ## Q&A, Other 32 | 33 | * Transfer canterberry/nodejs-keys into nodejs/keys [nodejs/node#456](https://github.com/nodejs/admin/issues/456) 34 | * Previously discussed in the Release WG and we agreed it was good to pursue. 35 | * No objections to the transfer of the repository. 36 | * `nodejs/release-keys` preferred naming. 37 | * After this happens, we should update related documentation. 38 | * Node.js releasers email alias? [#663](https://github.com/nodejs/Release/issues/663) 39 | * Named alias to be more specific `security-release` to ensure it’s only used for the purpose of sourcing releasers for security releases. 40 | * Trim active releasers list [#499](https://github.com/nodejs/admin/issues/456) 41 | * (Action) Richard to try and match keys to releasers. 42 | -------------------------------------------------------------------------------- /doc/meetings/2021-06-17.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2021-06-17 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=P3v0IpXwpXY 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/678 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1rIjBFGzWYIyO52m3YeXhGsCdBWZsXyTKo1XqH0P4kGM/edit 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Danielle Adams (@danielleadams) 13 | * Michael Zasso (@targos) 14 | * Richard Lau (@richardlau) 15 | * Ruy Adorno (@ruyadorno) 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | ### nodejs/Release 22 | 23 | * Release plan - v16.x Current [#658](https://github.com/nodejs/Release/issues/658) 24 | * Volunteers up until the end of June. 25 | * v16.4.0 slightly deferred due to the npm update. 26 | * Release plan - v14.x Active LTS [#567](https://github.com/nodejs/Release/issues/567) 27 | * Probably aim for July for the next patch update - to include the ICU fix/revert. 28 | * Michael volunteered for the next minor release. 29 | * Release plan - v12.x Maintenance [#494](https://github.com/nodejs/Release/issues/494) 30 | * Richard has volunteered for an upcoming patch release. 31 | 32 | ## Q&A, Other 33 | 34 | * deps: update ICU to 69.1 [#nodejs/node#38178](https://github.com/nodejs/node/pull/38178#issuecomment-863116223) 35 | * Changed the minimum ICU version in an LTS line (14.x) and that has broken building against the system ICU. 36 | * v14.0.0 went out with a minimum ICU req. of ICU 65, v14.6.0 bumped the minimum ICU to 67 as part of a V8 update: [nodejs/node#34356](https://github.com/nodejs/node/pull/34356) 37 | * Let’s try to patch the V8 update that caused ICU to stop building, or, failing that, open a revert PR. 38 | * Richard to open an issue to discuss the general policy for ICU updates. 39 | -------------------------------------------------------------------------------- /doc/meetings/2021-07-01.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2021-07-01 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=YiXoO6HEHtk 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/681 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1WSib2Z6msdXCHUvIvmbXRMxS1Fdu_oBtgpkrVTDXwkI 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Michael Zasso (@targos) 13 | * Richard Lau (@richardlau) 14 | 15 | ## Announcements 16 | 17 | * Node.js security releases today (2021-07-01). 18 | * https://nodejs.org/en/blog/vulnerability/july-2021-security-releases/ 19 | 20 | ## Agenda 21 | 22 | * Release plan - v16.x Current [#658](https://github.com/nodejs/Release/issues/658) 23 | * Volunteers up until the end of July. 24 | * Release plan - v14.x Active LTS [#567](https://github.com/nodejs/Release/issues/567) 25 | * Probably aim for July for the next patch update - to include the ICU fix/revert. Richard volunteered to do this in July. 26 | * Michael volunteered for the next minor release in August. 27 | * Release plan - v12.x Maintenance [#494](https://github.com/nodejs/Release/issues/494) 28 | * Richard has volunteered for an upcoming patch release, likely in July. 29 | * Not working release-key import [nodejs/node#39114](https://github.com/nodejs/node/issues/39114) 30 | * sks-keyservers stopped publishing DNS entries 31 | * Some of our keys are available on alternative key servers. 32 | * In the process of moving and updating keys in https://github.com/nodejs/release-keys. 33 | * Releasers to check their keys are up-to-date in https://github.com/nodejs/release-keys. 34 | * We will need to amend/update any guidance and onboarding documentation. 35 | * @nodejs/releasers to have write access to https://github.com/nodejs/release-keys. 36 | -------------------------------------------------------------------------------- /doc/meetings/2021-08-12.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2021-08-12 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=3u6Glh840hQ 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/687 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1ASrbr8psKbUwXZ9dSI4iWiMy17UkyQaeeML9Nq_EwBo 8 | 9 | ## Present 10 | 11 | * Richard Lau (@richardlau) 12 | * Beth Griggs (@BethGriggs) 13 | * Michael Zasso (@targos) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | * August 2021 Security releases: 20 | * [Node.js v12.22.5 (LTS)] https://nodejs.org/en/blog/release/v12.22.5/ 21 | * [Node.js v14.17.5 (LTS)] - https://nodejs.org/en/blog/release/v14.17.5/ 22 | * [Node.js v16.6.2 (Current)] - https://nodejs.org/en/blog/release/v16.6.2/ 23 | * Note: Potential regression in these releases for building against shared c-ares. 24 | 25 | 26 | ### nodejs/Release 27 | 28 | * Release plan - v16.x Current [#658](https://github.com/nodejs/Release/issues/658) 29 | * Scheduled up until the end of August. 30 | * Release plan - v14.x Active LTS [#567](https://github.com/nodejs/Release/issues/567) 31 | * Semver minor needs time for the release candidate phase, aiming for September. 32 | * Release plan - v12.x Maintenance [#494](https://github.com/nodejs/Release/issues/494) 33 | * One commit on the staging branch, waiting until there is a more pressing need for a release. 34 | * Release key servers [nodejs/node#39731](https://github.com/nodejs/node/pull/39731) 35 | * Instructions need to be updated - it doesn't make sense to update to use another sks keyservers. 36 | * Match what the Docker Team is doing by pointing to keys.openpgp.org as proposed in #39227. 37 | * Probably longer term we'll switch over to https://github.com/nodejs/release-keys when it is ready. 38 | * Actions: 39 | * Check all releasers keys are in keys.openpgp.org 40 | * Merge Node.js core instructions update - [#39227](https://github.com/nodejs/node/pull/39227) 41 | * Create a GitHub action to publish keys in the release-keys repository to our target key server. -------------------------------------------------------------------------------- /doc/meetings/2021-09-23.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2021-09-23 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=KtITpNuU_K8 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/695 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1F52S4X-bXme939W2pZ8CqByCTxAnwz0nhzCg9J8ULXA/ 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Danielle Adams (@danielleadams) 13 | * Myles Borins (@MylesBorins) 14 | * Richard Lau (@richardlau) 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | * Node.js v16.10.0 release - https://nodejs.org/en/blog/release/v16.10.0/ 21 | * Preparation on Node.js 17 is due on 19th October 2021 22 | * Proposal - https://github.com/nodejs/node/pull/40119 23 | * Release candidate - https://nodejs.org/download/rc/v17.0.0-rc.0 24 | 25 | ### nodejs/Release 26 | 27 | * npm@8 - https://github.com/nodejs/node/issues/40168 28 | * Release is planned in two weeks’ time. 29 | * Most significant breaking change is dropping support for Node.js 10. 30 | * No objections so far to including npm@8 in Node.js 16. 31 | * Release plan - v16.x Current [#658](https://github.com/nodejs/Release/issues/658) 32 | * Promoted to long-term support on 26th October 2021. 33 | * Release plan - v14.x Active LTS [#567](https://github.com/nodejs/Release/issues/567) 34 | * v14.18.0 - https://github.com/nodejs/node/pull/39990 35 | * Drop the last patch release before maintenance due to timings. 36 | * Release plan - v12.x Maintenance [#494](https://github.com/nodejs/Release/issues/494) 37 | * No pressing patches requiring release at this time. 38 | * Plans to restart some release mentoring sessions. 39 | -------------------------------------------------------------------------------- /doc/meetings/2021-11-04.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2021-11-04 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=69SA3p1UPtA 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/709 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1ilhK_WWlChCD7Lc3ywJaV2V4Mmze2bN-ZhQE9fxaAjk 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Bradley Farias (@bmeck) 13 | * Myles Borins (@MylesBorins) 14 | * Richard Lau (@richardlau) 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | ### nodejs/Release 21 | 22 | * Release plan - v17.x Current [#703](https://github.com/nodejs/Release/issues/703) 23 | * Deferred the scheduled release due to CI instability. 24 | * Release plan - v16.x Active LTS [#658](https://github.com/nodejs/Release/issues/658) 25 | * Schedule a patch release for November. 26 | * Aim for a minor release in January. 27 | * Need to add a release candidate column. 28 | * Ideally 1-2 weeks for minor releases. 29 | * Release plan - v14.x Maintenance LTS [#567](https://github.com/nodejs/Release/issues/567) 30 | * Few items on the staging branch, but nothing pressing. 31 | * Need to land some commits to improve CI stability. 32 | * Patch release in November. 33 | * Potential minor release in January. 34 | * Release plan - v12.x Maintenance [#494](https://github.com/nodejs/Release/issues/494) 35 | * Uncomfortable landing semver minors at this point in Node.js 12’s lifecycle. 36 | * Leaning towards not shipping https://github.com/nodejs/node/pull/40508 on Node.js 12. 37 | * Reduced impact of these changes due to the short amount of support time left. 38 | * Potentially update c-ares after it has baked in other release lines. 39 | * Plan for an upcoming patch release this year (date TBD). 40 | * Onboarding sessions 41 | * (Action) Doodle poll for onboarding sessions. 42 | * Release keys 43 | * PR to update instructions is blocked on a couple of unverified keys. 44 | * I propose we land to fix the instructions, and open issues to get the last keys verified. 45 | * Most recently active releasers have verified their keys, so the impact of the unverified keys should be minimal. 46 | * FreeBSD release binaries 47 | * Shortage of volunteers committed to maintaining the platform (keeping CI green, infrastructure, etc.). 48 | * Until the volunteer situation changes we’ll be unlikely to add FreeBSD release binaries. 49 | -------------------------------------------------------------------------------- /doc/meetings/2021-12-02.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2021-12-02 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=eQnCGn_iN7Q 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/713 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1UZHWz8sCncBzAv-rdBUsHtIPaQJULeih8ttumT6cjck 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Michael Zasso (@targos) 13 | * Richard Lau (@richardlau) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | * New releases: 20 | * v17.2.0 - https://nodejs.org/en/blog/release/v17.2.0/ 21 | * v16.13.1 - https://nodejs.org/en/blog/release/v16.13.1/ 22 | * v14.18.2 - https://nodejs.org/en/blog/release/v14.18.2/ 23 | * Planning for Node.js 18 platform requirements - [nodejs/build#2815](https://github.com/nodejs/build/issues/2815) 24 | 25 | ### nodejs/Release 26 | 27 | * Move to monthly Release WG meetings? [#711](https://github.com/nodejs/Release/issues/711) 28 | * No objections. 29 | * (Action) Beth to update the calendar. 30 | * Node.js releaser’s email alias? [#663](https://github.com/nodejs/Release/issues/663) 31 | * No immediate desire, but could be useful for coordinating security releases. 32 | * Proposal to rename CITGM team to `release-automation` [#557](https://github.com/nodejs/Release/issues/557) 33 | * (Action) Audit CITGM team membership. 34 | * It’s good for membership to reflect the number of active maintainers. 35 | * Revisit the rename after we’ve completed the audit. 36 | * doc: simplify major release preparation [nodejs/node#40816](https://github.com/nodejs/node/issues/40816) 37 | * (Action) If there are no objections by next week then we’ll land the PR. 38 | * Release plan - v17.x Current [#703](https://github.com/nodejs/Release/issues/703) 39 | * Drop the 2021-12-28 release due to holidays. 40 | * Release plan - v16.x Active LTS [#658](https://github.com/nodejs/Release/issues/658) 41 | * Danielle has volunteered for January minor release. 42 | * Plan for a patch release in February. 43 | * Release plan - v14.x Maintenance (LTS) [#567](https://github.com/nodejs/Release/issues/567) 44 | * (Action) Review open minor PRs and indicate approval for landing on Node.js 14. 45 | * Release plan - v12.x Maintenance [#494](https://github.com/nodejs/Release/issues/494) 46 | * npm needs to be patched to address some warnings. 47 | * We should hold off on the release until the npm patch is ready to save doing multiple maintenance releases. 48 | * (Action) Open a PR to backport root certificates to both Node.js 12 and 14 to drive discussion. -------------------------------------------------------------------------------- /doc/meetings/2022-01-13.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2022-01-13 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=1SIp9nsJRII 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/719 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1OZY8BDg9yUgOZiBOkmDnvzDl3ibo1IyXj65Q5xiTT00 8 | 9 | ## Present 10 | 11 | * Michael Zasso (@targos) 12 | * Myles Borins (@MylesBorins) 13 | * Richard Lau (@richardlau) 14 | * Ruy Adorno (@ruyadorno) 15 | 16 | ## Agenda 17 | 18 | ### nodejs/Release 19 | 20 | * Imminent issue for Morocco users (tzdata2020a) [#576](https://github.com/nodejs/Release/issues/576) 21 | * Issue was for previous timezone update applied to releases except not to v12.x (which is why it is still open). 22 | * Comment added about upcoming 22 Feb 2022 DST change for Jordan and asking for timezone updates. 23 | * Some concern over newer timezone db updates dropping historical data/merging timezones. 24 | * Our maintaining guide https://github.com/nodejs/node/blob/master/doc/guides/maintaining-icu.md#time-zone-data actually pulls timezone data from ICU’s icudata GitHub repo and that diverges from upstream tz db by keeping historical data so risk to LTS should be less than for upstream tz 25 | * (Michael) For 16 and 14 can we backport the latest ICU update? 26 | * Worth trying as long as CI (including V8 CI) is happy with unchanged minimum ICU and the update 27 | * Plan to open PRs to update each LTS line and run CI’s. Aim to get these into releases planned for later this month/beginning Feb. 28 | * Release plan - v17.x Current [#703](https://github.com/nodejs/Release/issues/703) 29 | * Release plan - v16.x Active LTS [#658](https://github.com/nodejs/Release/issues/658) 30 | * Release plan - v14.x Maintenance LTS [#567](https://github.com/nodejs/Release/issues/567) 31 | * Proposal to rename CITGM team to `release-automation` [#557](https://github.com/nodejs/Release/issues/557) 32 | * Release plan - v12.x Maintenance [#494](https://github.com/nodejs/Release/issues/494) 33 | -------------------------------------------------------------------------------- /doc/meetings/2022-02-10.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2022-02-10 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=IWJyJDbCfc4 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/722 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1wd21zd4fmL04-KO5N45I5poHo-25kkTeikRdB1epd5I 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Danielle Adams (@danielleadams) 13 | * Myles Borins (@MylesBorins) 14 | * Richard Lau (@richardlau) 15 | * Ruy Adorno (@ruyadorno) 16 | 17 | ## Agenda 18 | 19 | ### nodejs/Release 20 | 21 | * Release plan - v17.x Current [#703](https://github.com/nodejs/Release/issues/703) 22 | * Release plan - v16.x Active LTS [#658](https://github.com/nodejs/Release/issues/658) 23 | * Imminent issue for Morocco users (tzdata2020a) [#576](https://github.com/nodejs/Release/issues/576) 24 | * Release plan - v14.x Maintenance LTS [#567](https://github.com/nodejs/Release/issues/567) 25 | * Proposal to rename CITGM team to `release-automation` [#557](https://github.com/nodejs/Release/issues/557) 26 | * Release plan - v12.x Maintenance [#494](https://github.com/nodejs/Release/issues/494) 27 | 28 | ## Q&A, Other 29 | 30 | * what to do for breaking releases? Releasers? Contributors? (brought up in TSC meeting recently) 31 | -------------------------------------------------------------------------------- /doc/meetings/2022-03-10.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2022-03-10 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=1RxlsH0T0gU 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/732 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1o9VNtgy_I4RAIBdVv2aYQk0G1nM98ioeSrOAV4w8OF4 8 | 9 | ## Present 10 | 11 | * Bryan English (@bengl) 12 | * Michael Zasso (@targos) 13 | * Juan José Arboleda (@juanarbol) 14 | * Richard Lau (@richardlau) 15 | * Ruy Adorno (@ruyadorno) 16 | * Myles Borins (@MylesBorins) 17 | * Stewart Addison 18 | 19 | ## Agenda 20 | -------------------------------------------------------------------------------- /doc/meetings/2022-04-14.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2022-04-07 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=Y_1tB3YRG2A 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/735 7 | 8 | ## Present 9 | 10 | * Beth Griggs (@BethGriggs) 11 | * Bryan English (@bengl) 12 | * Danielle Adams (@danielleadams) 13 | * Juan Arboleda (@soyjuanarbol) 14 | * Richard Lau (@richardlau) 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | * Node.js 18 is due to be released on the 19th April. 21 | * Latest release candidate is available - https://nodejs.org/download/rc/v18.0.0-rc.3/. 22 | 23 | ### nodejs/Release 24 | 25 | * Process for unintentional breaking changes [#728](https://github.com/nodejs/Release/issues/728) 26 | * The specific issue/PR that raised this has been addressed. 27 | * Some process documentation would be helpful. 28 | * Let’s untag from the agenda and add a comment stating our intent to create some guidance. 29 | * Create a guide on ‘What to do when a release is broken? [#558](https://github.com/nodejs/Release/issues/558) 30 | * Should form part of the same release guide. 31 | * Working out a policy around reverts for LTS branches [#535](https://github.com/nodejs/Release/issues/535) 32 | * Should form part of the same release guide. 33 | * Proposal to rename CITGM team to `release-automation` [#557](https://github.com/nodejs/Release/issues/557) 34 | * Plan was to grant releasers access to the automation repositories. 35 | * (Action) To confirm whether the access has been added. 36 | * Bryan worked on a fix for `branch-diff` - it would be good for us to have access to be able to merge it. 37 | * Release plan - v18.x Current [#737](https://github.com/nodejs/Release/issues/737) 38 | * Node.js 18 release plan issue has been following our typical schedule for current releases. 39 | * Release plan - v17.x Current [#703](https://github.com/nodejs/Release/issues/703) 40 | * No future releases planned - let’s close the issue. 41 | * Release plan - v16.x Active LTS [#658](https://github.com/nodejs/Release/issues/658) 42 | * Danielle has been working on the semver minor release. 43 | * Release plan - v14.x Maintenance LTS [#567](https://github.com/nodejs/Release/issues/567) 44 | * Juan volunteered to do the next patch release. 45 | * Release plan - v12.x Maintenance [#494](https://github.com/nodejs/Release/issues/494) 46 | * Issue closed as no further planned releases. 47 | 48 | -------------------------------------------------------------------------------- /doc/meetings/2022-05-05.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2022-05-05 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=P1-S1tTIM1M 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/743 7 | 8 | ## Present 9 | 10 | * Michaël Zasso (@targos) 11 | * Bryan English (@bengl) 12 | * Richard Lau (@richardlau) 13 | * Ruy Adorno (@ruyadorno) 14 | * Juan Arboleda (@juanarbol) 15 | * Beth Griggs (@BethGriggs) 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | * Node.js 14.19.2 released by Juan. 22 | * Node.js 18.1.0 released. 23 | 24 | ### nodejs/Release 25 | 26 | * Automate timezone updates [#43134](https://github.com/nodejs/node/issues/43134) 27 | * Moved to nodejs/node for more visibility. 28 | * Periodic Table does not have an element starting with "J" or "Q" or "W" [#304](https://github.com/nodejs/Release/issues/304) 29 | * Suggestions in the issue. Let’s collate the suggestions and arrange a poll. 30 | * End-of-Life dates of Node.js 16 and OpenSSL 1.1.1 do not align [#1222](https://github.com/nodejs/tsc/issues/1222) 31 | * OpenSSL 1.1.1 will not receive updates after September 2023. 32 | * Options are: 33 | * Bring forward End-of-Life date for Node.js 16 as we did for Node.js 8. 34 | * Upgrade OpenSSL 1.1.1 to OpenSSL 3 during the release. There are known compatibility issues identified in Node.js 17 and 18. 35 | * If there are no objections from the release group, then we just need to create a blog post and/or update the schedule once the decision is made. 36 | * Release plan - v18.x Current [#737](https://github.com/nodejs/Release/issues/737) 37 | * Leave the schedule as is but need a volunteer. 38 | * Release plan - v17.x Current [#703](https://github.com/nodejs/Release/issues/703) 39 | * Use this as Rafael’s onboarding release. Beth will pair on the release. 40 | * Release plan - v16.x Active LTS [#658](https://github.com/nodejs/Release/issues/658) 41 | * Juan volunteered. Beth will pair on the release. 42 | * Release plan - v14.x Maintenance LTS [#567](https://github.com/nodejs/Release/issues/567) 43 | * Richard volunteered. 44 | 45 | ## Q&A, Other 46 | 47 | * @releasers granted merge access to `changelog-maker` and `branch-diff`. -------------------------------------------------------------------------------- /doc/meetings/2022-06-16.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2022-06-16 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=iOLMyWpCcd0 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/754 7 | 8 | ## Present 9 | 10 | * Beth Griggs (@BethGriggs) 11 | * Danielle Adams (@danielleadams) 12 | * Juan Arboleda (@juanarbol) 13 | * Richard Lau (@richardlau) 14 | 15 | ## Agenda 16 | 17 | ## Announcements 18 | 19 | * Default nodejs/node branch is now main. 20 | * Node.js 18.4.0 released. 21 | 22 | ### nodejs/Release 23 | 24 | * Periodic Table does not have an element starting with "J" or "Q" or "W" [#304](https://github.com/nodejs/Release/issues/304) 25 | * Should we still do the poll? 26 | * If we have a poll, we need to approve the poll options in the release group. 27 | * If we have a GitHub poll, should it be in `nodejs/node` or `nodejs/release`. 28 | * `nodejs/node` will have more visibility. 29 | * Rename 18.x LTS to Hafnium [#753](https://github.com/nodejs/Release/pull/753) 30 | * Hydrogen is already picked and written in release notes. 31 | * No compelling reason to switch at this point. 32 | * Linear history for this repository? [#13](https://github.com/nodejs/release-keys/issues/13) 33 | * It has the opposite defaults compared to the other repositories in the GitHub organization. 34 | * Let’s leave it as is and merge the open pull requests. 35 | * Release plan - v18.x Current [#737](https://github.com/nodejs/Release/issues/737) 36 | * Juan volunteered. 37 | * Release plan - v16.x Active LTS [#658](https://github.com/nodejs/Release/issues/658) 38 | * Danielle has volunteered for the next patch release. 39 | * Release plan - v14.x Maintenance LTS [#567](https://github.com/nodejs/Release/issues/567) 40 | * No pressing patches requiring release at this time. 41 | -------------------------------------------------------------------------------- /doc/meetings/2022-06-30.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2022-06-30 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=NSNE1mIUfgc 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/758 7 | 8 | ## Present 9 | 10 | * Beth Griggs (@BethGriggs) 11 | * Juan Arboleda (@juanarbol) 12 | * Michael Zasso (@targos) 13 | * Rafael Gonzaga (@rafaelgss) 14 | * Richard Lau (@richardlau) 15 | * Ruy Adorno (@ruyadorno) 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | * Node.js security releases announced for the week of 5th July. 22 | 23 | ### nodejs/Release 24 | 25 | * Periodic Table does not have an element starting with "J" or "Q" or "W" [#304](https://github.com/nodejs/Release/issues/304) 26 | * Reviewed the candidate names for “J” and the only option those present in the meeting felt was suitable was “Jod”. 27 | * Node 16.14.2 highWaterMark:0 doesn't handle backpressure [nodejs/node#42457](https://github.com/nodejs/node/issues/42457). 28 | * We will defer to the streams team for advice. 29 | * Richard [commented](https://github.com/nodejs/node/issues/42457#issuecomment-1171291924) on the PR indicating that we can pull the revert or patch into a release in July if the decision is made. 30 | * Grant release team maintainer access to release-related tooling [#557](https://github.com/nodejs/Release/issues/557) 31 | * Release plan - v18.x Current [#737](https://github.com/nodejs/Release/issues/737) 32 | * Rafael is working on the security release, the regular current release is deferred. 33 | * Release plan - v16.x Active LTS [#658](https://github.com/nodejs/Release/issues/658) 34 | * Danielle is working on the security release. A minor release is scheduled for July. 35 | * Release plan - v14.x Maintenance LTS [#567](https://github.com/nodejs/Release/issues/567) 36 | * Juan working on the security release. No pressing patches require release at this time. -------------------------------------------------------------------------------- /doc/meetings/2022-07-28.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2022-07-28 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=IVLG7kCtYiE 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/764 7 | 8 | ## Present 9 | 10 | * Beth Griggs (@BethGriggs) 11 | * Danielle Adams (@danielleadams) 12 | * Rafael Gonzaga (@rafaelgss) 13 | * Richard Lau (@richardlau) 14 | * Ruy Adorno (@ruyadorno) 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | ### nodejs/Release 21 | 22 | * New meeting host [#740](https://github.com/nodejs/Release/issues/740) 23 | * Ruy volunteered to get set up to host some of the meetings. 24 | * Periodic Table does not have an element starting with "J" or "Q" or "W" [#304](https://github.com/nodejs/Release/issues/304) 25 | * (Action) PR ‘Jod’ to codenames file as no further suggestions or objections. 26 | * Major release rotation [#765](https://github.com/nodejs/Release/issues/765) 27 | * Proposed schedule. 28 | * Concern around how far in advance a rotation schedule is practical. 29 | * Need pairing and support for releasers new to majors. 30 | * (Proposal) The quarter before the release we open a preparation issue for the next major release. 31 | * Add the last EOL release(s) to the graph? [#761](https://github.com/nodejs/Release/issues/761) 32 | * No strong opinions on adding EOL releases to the graph. 33 | * Concern about making the graph cluttered. 34 | * Suggestion to add EOL release information to the website’s release page. 35 | * Release plan - v18.x Current [#737](https://github.com/nodejs/Release/issues/737) 36 | * Danielle and Rafael volunteered for upcoming releases. 37 | * Release plan - v16.x Active LTS [#658](https://github.com/nodejs/Release/issues/658) 38 | * Michaël is preparing the next minor release. It is likely to be the last full semver-minor release of Node.js 16 before it goes into maintenance. 39 | * Release plan - v14.x Maintenance LTS [#567](https://github.com/nodejs/Release/issues/567) -------------------------------------------------------------------------------- /doc/meetings/2022-08-25.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2022-08-25 2 | 3 | ## Links 4 | 5 | * **Recording**: 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/774 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1OKukl_wpMd6dQOgxTC7MQ8HhJLHD7yo38Q_NrXsy3ro 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Rafael Gonzaga (@RafaelGSS) 13 | * Richard Lau (@richardlau) 14 | * Ruy Adorno (@ruyadorno) 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | * Release v18.8.0 came out yesterday: https://nodejs.org/en/blog/release/v18.8.0/ 21 | 22 | ### nodejs/Release 23 | 24 | * Imminent issue for chilean users (tzdata2022b) [#773](https://github.com/nodejs/Release/issues/773) 25 | * it looks like there’s a PR in a mergeable state 26 | * send a message to release channel and see if we can find more volunteers 27 | 28 | * Remove limitation on the frequency of semver-minor LTS relesease [#772](https://github.com/nodejs/Release/issues/772) 29 | * Beth: summarizing a bit of the conversation in the issue, we should stop holding off minor releases and just have a cadence of monthly releases (minor or patch) that lands commits that have been landed past a certain point in time (maybe a 4 weeks baking time?) 30 | * Ruy: is there a way to automate the baking time 31 | * Beth: we can just target branch-diff using a release that has landed for around that time, given the typical cadence of current that would be around 2 releases backwards 32 | 33 | * Major release rotation? [#765](https://github.com/nodejs/Release/issues/765) 34 | * Rafael and Ruy are available to participate and Beth can mentor, and transfer the knowledge from the previous major releases 35 | 36 | * New meeting host [#740](https://github.com/nodejs/Release/issues/740) 37 | 38 | * Release plan - v18.x Current [#737](https://github.com/nodejs/Release/issues/737) 39 | 40 | * Release plan - v16.x Active LTS [#658](https://github.com/nodejs/Release/issues/658) 41 | 42 | * Release plan - v14.x Maintenance LTS [#567](https://github.com/nodejs/Release/issues/567) 43 | 44 | * Periodic Table does not have an element starting with "J" or "Q" or "W" [#304](https://github.com/nodejs/Release/issues/304) 45 | * Removed from the agenda 46 | 47 | * Create an issue for tracking a possible collaborator summit session 48 | 49 | -------------------------------------------------------------------------------- /doc/meetings/2022-09-22.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2022-09-22 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/LzpreTUDLAg 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/782 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1BZ0SfCBwRBJAYfLHC9naQ33CTNWTnF_pfwTSm6BRkEg 8 | 9 | ## Present 10 | 11 | * Release team: @nodejs/release 12 | * LTS team: @nodejs/lts 13 | * Richard Lau (@richardlau) 14 | * Michael Zasso (@targos) 15 | * Rafael Gonzaga (@rafaelgss) 16 | * Juan Arboleda (@soyjuanarbol) 17 | * Ruy Adorno (@ruyadorno) 18 | * Danielle Adams (@adamzdanielle) 19 | 20 | ## Agenda 21 | 22 | ## Announcements 23 | 24 | *Extracted from **Release-agenda** labeled issues and pull requests from the **nodejs org** prior to the meeting. 25 | 26 | ### nodejs/Release 27 | 28 | * Plans for npm 9 [#778](https://github.com/nodejs/Release/issues/778) 29 | * Consensus on landing it on v19 first and waiting for baking time before landing it on v18 LTS 30 | * Imminent issue for chilean users (tzdata2022b) [#773](https://github.com/nodejs/Release/issues/773) 31 | * PR already landed on main 32 | * Needs backporting, let’s move/create an issue on nodejs/node to get some volunteers 33 | * Remove limitation on the frequency of semver-minor LTS releases [#772](https://github.com/nodejs/Release/issues/772) 34 | * We have consensus on implementing the changes proposed in the linked thread 35 | * Let’s communicate the change by adding semver-minor releases to upcoming LTS v18 schedule 36 | * General consensus is to switch to using second-to-last current release as a target, this should give us generally a 4-weeks period of baking time, it’s also up to the releaser to be mindful about it in case that two releases happened within a shorter period of time 37 | * Important: Security releases should not count as they usually don’t respect the scheduled 2-week period 38 | * Major release rotation? [#765](https://github.com/nodejs/Release/issues/765) 39 | * Mostly solved, we have Rafael and Ruy lined up for the v19 major release 40 | * We can encourage folks to pair on major releases in order to have a backup + knowledge sharing 41 | * Release plan - v18.x Current [#737](https://github.com/nodejs/Release/issues/737) 42 | * Release plan - v16.x Active LTS [#658](https://github.com/nodejs/Release/issues/658) 43 | * Release plan - v14.x Maintenance LTS [#567](https://github.com/nodejs/Release/issues/567) 44 | * TODO: 45 | * Update the v18.x schedule to add the LTS table, move old table to hidden “Current” detail 46 | * Add v19.x schedule 47 | 48 | ## Q&A, Other 49 | 50 | ## Upcoming Meetings 51 | 52 | * **Node.js Project Calendar**: 53 | 54 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 55 | 56 | -------------------------------------------------------------------------------- /doc/meetings/2022-10-01.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2022-10-01 2 | 3 | > Special session at the Collaborator Summit, Dublin 2022 4 | 5 | ## Links 6 | 7 | * **GitHub Issue**: https://github.com/openjs-foundation/summit/issues/331 8 | * **Minutes Google Doc**: https://docs.google.com/document/d/1BZ0SfCBwRBJAYfLHC9naQ33CTNWTnF_pfwTSm6BRkEg 9 | 10 | ## Present 11 | 12 | * Ruy Adorno (@ruyadorno) 13 | * Beth Griggs (@BethGriggs) 14 | * Michael Zasso (@targos) 15 | * Rafael Gonzaga (@rafaelgss) 16 | * Danielle Adams (@adamzdanielle) 17 | * Orta (@orta) 18 | 19 | ## Agenda 20 | 21 | - Intro 22 | - Security Release lhttp update 23 | - Node.js v19 coming up 24 | - Monthly LTS minor release 25 | - Improving state of CITGM tests 26 | - Security Patch validation (https://github.com/nodejs/node/pull/44806) 27 | - Better release notes 28 | 29 | ### Intro 30 | 31 | We need to also attract contributions to the build WG which currently lacks collaborators to help improve the state of CI 32 | 33 | ### Security Release llhttp update 34 | 35 | https://github.com/nodejs/llhttp 36 | llhttp is a dependency that gets many security reports and has currently one collaborator 37 | There’s no documentation on how to maintain it 38 | We need to attract more collaborators to help with the work 39 | 40 | ### Node.js v19 coming up 41 | 42 | Heads up to collaborators, now is the time to land breaking changes in time to land on node19 43 | There’s an RC build available if anyone wants to check out the first pre built version of node19: https://nodejs.org/download/rc/v19.0.0-rc.0/ 44 | V8 updates, should be ready in time for the release 45 | Reach out to OpenJS Foundation to sync about blog post 46 | 47 | ### Improving state of CITGM tests 48 | 49 | Try to pin to the latest stable version of packages 50 | Let’s reduce the number of packages we’re testing 51 | 52 | ### Monthly LTS minor release 53 | 54 | Michael worked on many minor releases this year and noticed there were areas that could be improved and one of the recurring pain points was having to skip all the minor-semver changes. 55 | 56 | In https://github.com/nodejs/Release/issues/772 we decided to tweak LTS releases to allow semver-minor commits to land on the monthly LTS release regularly. Adding an extra rule to add 4-weeks baking time. 57 | 58 | ### Better release notes 59 | 60 | Add bot automation to ask authors to add a comment with some description they’d like to see in the final changelog. 61 | 62 | ### Security Patch validation 63 | 64 | Have a way to build a binary from a private release job system and share that with reporters. 65 | 66 | Would be really nice to have a private CI test setup so that we can run tests on nodejs-private PRs. 67 | 68 | -------------------------------------------------------------------------------- /doc/meetings/2022-10-20.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2022-10-20 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/oixm4DKFl-g 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/791 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1icqSaYvhte82qITQ3ojD4FT3aZKW5wcg4HQ7jX5Rn3A 8 | 9 | ## Present 10 | 11 | * Rafael Gonzaga (@rafaelgss) 12 | * Juan Arboleda (@juanarbol) 13 | * Ruy Adorno (@ruyadorno) 14 | * Beth Griggs (@BethGriggs) 15 | * Bryan English (@bengl) 16 | * Richard Lau (@richardlau) 17 | * Darcy Clarke (@darcyclarke) 18 | * Kerem Kat (@krk) 19 | 20 | ## Agenda 21 | 22 | ## Announcements 23 | 24 | Release 19 went out earlier this week. Thanks Rafael, Ruy and Beth! 25 | 26 | ### nodejs/Release 27 | 28 | * Prune nodejs/citgm team [admin#737](https://github.com/nodejs/admin/issues/737) 29 | * Plans for npm 9 [#778](https://github.com/nodejs/Release/issues/778) 30 | * node v19 is out/Current 31 | * v9.0.0 is now out - `npm i -g npm@9` 32 | * not yet latest tag, the npm team is aiming for a phased rollout 33 | * notable re. Node.js 16 issue: https://github.com/nodejs/node/issues/44992 34 | * npm9 update PR should be open in between november - december 35 | * Imminent issue for chilean users (tzdata2022b) [#773](https://github.com/nodejs/Release/issues/773) 36 | * Richard will open PR later today to update v14.x. Can be removed from agenda. 37 | * Remove limitation on the frequency of semver-minor LTS release [#772](https://github.com/nodejs/Release/issues/772) 38 | * should change the language to be monthly vs. restricting minor 39 | * Major release rotation? [#765](https://github.com/nodejs/Release/issues/765) 40 | * Look into potentially automating a reminder for collaborators to sign up to lead major releases moving forward 41 | * Release plan - v18.x Current [#737](https://github.com/nodejs/Release/issues/737) 42 | * Action item: Update the schedule 43 | * Release plan - v16.x Active LTS [#658](https://github.com/nodejs/Release/issues/658) 44 | * Leave a placeholder in the list in case there’s a new matin 45 | * Release plan - v14.x Maintenance LTS [#567](https://github.com/nodejs/Release/issues/567) 46 | * Danielle is currently working on a release 47 | 48 | ## Q&A, Other 49 | 50 | ## Upcoming Meetings 51 | 52 | * **Node.js Project Calendar**: 53 | 54 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 55 | 56 | -------------------------------------------------------------------------------- /doc/meetings/2022-11-17.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2022-11-17 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/U-ws8D30PmA 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/800 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1hQw2179VLiutctvbiTX4zfKpA6OuNavDQTUEksrfR_U 8 | 9 | ## Present 10 | 11 | * Richard Lau (@richardlau) 12 | * Beth Griggs (@BethGriggs) 13 | * Juan Arboleda (@soyjuanarbol) 14 | * Ruy Adorno (@ruyadorno) 15 | * Danielle Adams (@danielleadams) 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | * Build migration is complete 22 | * [`v19.1.0`](https://nodejs.org/en/blog/release/v19.1.0/) released earlier this week 23 | 24 | ### nodejs/Release 25 | 26 | * Release plan - v19.x Current [#793]t(https://github.com/nodejs/Release/issues/793) 27 | * Release plan - v18.x Active LTS [#737](https://github.com/nodejs/Release/issues/737) 28 | * Release plan - v16.x Maintenance [#658](https://github.com/nodejs/Release/issues/658) 29 | * Release plan - v14.x Maintenance LTS [#567](https://github.com/nodejs/Release/issues/567) 30 | * Plans for npm 9 [#778](https://github.com/nodejs/Release/issues/778) 31 | * Sync with the npm team and see if they’re comfortable with that PR landing 32 | * Make sure all breaking changes listed by the npm team are listed in our changelog when it npm@9 lands 33 | * Major release rotation? [#765](https://github.com/nodejs/Release/issues/765) 34 | * Action item: Add notes to docs mentioning that 3 months prior a pair of releasers should volunteer to work on the upcoming next major release 35 | 36 | ## Upcoming Meetings 37 | 38 | * **Node.js Project Calendar**: 39 | 40 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 41 | 42 | -------------------------------------------------------------------------------- /doc/meetings/2023-01-12.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2023-01-12 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/NCApl6VSWcU 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/814 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1LC7GK2W9HGzLFY5UatSpm2f2pY5k83jfOhKbVsDmRyw 8 | 9 | ## Present 10 | 11 | * Release team: @nodejs/release 12 | * LTS team: @nodejs/lts 13 | * Rafael Gonzaga: (@RafaelGSS) 14 | * Richard Lau (@richardlau) 15 | * Beth Griggs (@BethGriggs) 16 | * Ruy Adorno (@ruyadorno) 17 | * Michael Zasso (@targos) 18 | 19 | ## Agenda 20 | 21 | ### nodejs/Release 22 | 23 | * No more scheduled meetings? [#812](https://github.com/nodejs/Release/issues/812) 24 | * Zoom recurring meetings have been reenabled 25 | * Need to update the calendar to go back to 4 weeks frequency instead of monthly 26 | * Make sure zoom link is included in the calendar invite 27 | * Plans for npm 9 [#778](https://github.com/nodejs/Release/issues/778) 28 | * Let’s open a backport PR to explicit our intention of landing it in the LTS line 29 | * Make sure there’s no potential impact to CI in the issue brought up by Jordan in https://github.com/nodejs/node/pull/45693 30 | * Major release rotation? [#765](https://github.com/nodejs/Release/issues/765) 31 | * We need to update the docs to mention that we should make a call for releasers 3 months in advance. 32 | * We can also automate that with a bot/Github Action if someone has the time to look into that. 33 | * Rafael added automation to the Release Team slack channel 34 | * Release plan - v19.x Current [#793](https://github.com/nodejs/Release/issues/793) 35 | * Michael signed up for a mid-February release 36 | * Release plan - v18.x Active LTS [#737](https://github.com/nodejs/Release/issues/737) 37 | * Let’s reach out to Juan and make sure he’s still able to handle the v18 release this month 38 | * Juan does not currently have a release key, even if he were to generate a new one it would not be something already in the README 39 | * Release plan - v16.x Maintenance [#658](https://github.com/nodejs/Release/issues/658) 40 | * Release plan - v14.x Maintenance LTS [#567](https://github.com/nodejs/Release/issues/567) 41 | * Ruy signed up for a v14 release some time in February in order to land the npm6 update: https://github.com/nodejs/node/pull/45936 42 | 43 | ### nodejs/nodejs-dependency-vuln-assessments 44 | 45 | * CVE-2022-3517 (npm) found on v14.x (Manual) [#88](https://github.com/nodejs/nodejs-dependency-vuln-assessments/issues/88) 46 | * Is addressed by https://github.com/nodejs/node/pull/45936 47 | 48 | ## Q&A, Other 49 | 50 | * Release keys issue: https://github.com/nodejs/release-keys/issues/21 51 | * Some releases may have been signed with the wrong key? 52 | * Rafael currently working on automating more steps in the Security Releases 53 | 54 | ## Upcoming Meetings 55 | 56 | * **Node.js Project Calendar**: 57 | 58 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 59 | 60 | -------------------------------------------------------------------------------- /doc/meetings/2023-02-09.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2023-02-09 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/AARWf6wInDc 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/823 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1Sd4yneHzM_vjegIF6Sp7-HPUg_97CgHJ22n5kD661ro 8 | 9 | ## Present 10 | 11 | * Rafael Gonzaga: (@RafaelGSS) 12 | * Richard Lau (@richardlau) 13 | * Juan Arboleda (@juanarbol) 14 | * Ruy Adorno (@ruyadorno) 15 | * Beth Griggs (@BethGriggs) 16 | * Michaël Zasso (@targos) 17 | 18 | ## Agenda 19 | 20 | ## Announcements 21 | 22 | * Richard: Security releases coming up next week, ref: https://nodejs.org/en/blog/vulnerability/february-2023-security-releases/ 23 | * Rafael working on a node-core-utils command to automate security releases, ref: https://github.com/nodejs/node-core-utils/pull/665 24 | 25 | ### nodejs/Release 26 | 27 | * Confusion around semver-minor commits [#820](https://github.com/nodejs/Release/issues/820) 28 | * Clarify that from the releasers point of view every semver-minor commit is picked up as a notable-change unless stated otherwise 29 | * Beth proposed a new bot that would comment and ask for a write-up when the notable-change label is added to a PR 30 | * Plans for npm 9 [#778](https://github.com/nodejs/Release/issues/778) 31 | * Let's try to chat with the npm cli team to align on future updates 32 | * Release plan - v19.x Current [#793](https://github.com/nodejs/Release/issues/793) 33 | * Postponing the next v19.x release since a new Security Release is scheduled for next week 34 | * Release plan - v18.x Active LTS [#737](https://github.com/nodejs/Release/issues/737) 35 | * Juan signed up for a v18.x release later this month 36 | * Release plan - v16.x Maintenance [#658](https://github.com/nodejs/Release/issues/658) 37 | * Aim for a march release, there's already a Security Release coming out this month 38 | * Release plan - v14.x Maintenance LTS [#567](https://github.com/nodejs/Release/issues/567) 39 | * Aiming for a tentive last release in march before it goes EOL 40 | 41 | ### nodejs/release-keys 42 | 43 | * v18 and v19 are signed by a public key not captured in this keyring [#21](https://github.com/nodejs/release-keys/issues/21) 44 | 45 | ### nodejs/nodejs-dependency-vuln-assessments 46 | 47 | * CVE-2022-3517 (npm) found on v14.x (Manual) [#88](https://github.com/nodejs/nodejs-dependency-vuln-assessments/issues/88) 48 | * The npm update that fixes these issues should be going out as part of the next week Security Release 49 | 50 | ## Upcoming Meetings 51 | 52 | * **Node.js Project Calendar**: 53 | 54 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 55 | 56 | -------------------------------------------------------------------------------- /doc/meetings/2023-03-09.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2023-03-09 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=aQUApH01jRA 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/830 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1htIwyXRwT61t89_z9SJTwaOOdE6yzCEAf0r5UqFKVKA 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Danielle Adams (@danielleadams) 13 | * Juan Jose (@juanarbol) 14 | * Michael Zasso (@targos) 15 | * Rafael Gonzaga (@RafaelGSS) 16 | * Richard Lau (@richardlau) 17 | 18 | ## Agenda 19 | 20 | ## Announcements 21 | 22 | * nodejs/nodejs.org rewrite in Next.js has landed. 23 | * The release post generation script now relies on the native fetch API so will need to be run on versions where it is available (Node.js 18+ by default). 24 | * Node.js 18.15.0 released by Juan this week. 25 | 26 | ### Release Schedules 27 | * Release plan - v19.x Current [#793](https://github.com/nodejs/Release/issues/793) 28 | * Michael volunteered for the April release. 29 | * Release plan - v18.x Active LTS [#737](https://github.com/nodejs/Release/issues/737) 30 | * Danielle volunteered for the next release. 31 | * Release plan - v16.x Maintenance [#658](https://github.com/nodejs/Release/issues/658) 32 | * Beth volunteered to put a draft proposal together with a TBD date until we get enough content. 33 | * Potential test runner PRs that we should review. 34 | * Release plan - v14.x Maintenance LTS [#567](https://github.com/nodejs/Release/issues/567) 35 | * We should plan for one more release to happen before EOL and consider what would be good to land (root certificate updates, or similar). 36 | 37 | ### nodejs/Release 38 | 39 | * Confusion around semver-minor commits [#820](https://github.com/nodejs/Release/issues/820) 40 | * Discussed at the last meeting. 41 | * PR opened to clarify the existing approach [nodejs/node#46592](https://github.com/nodejs/node/pull/46592) 42 | * (Action) Beth to add a comment and close. 43 | * Plans for npm 9 [#778](https://github.com/nodejs/Release/issues/778) 44 | * Desire to discuss aligning release dates in future. 45 | * Removing from the agenda. 46 | 47 | ### nodejs/release-keys 48 | 49 | * v18 and v19 are signed by a public key not captured in this keyring [#21](https://github.com/nodejs/release-keys/issues/21) 50 | * Keyring wasn’t updated, but should now be with Juan’s latest PR. 51 | * (Action) Beth to check which keys are in the keyring and also [nodejs/release-keys#23](https://github.com/nodejs/release-keys/issues/23). 52 | 53 | ## Q&A, Other 54 | 55 | * node-core-utils 56 | * Link to Rafael’s security prepare PR [nodejs/node-core-utils#665](https://github.com/nodejs/node-core-utils/pull/665) 57 | * Agreed to stick to a two-step approach initially until `git node land --security` functionality is added. 58 | * Richard tested for the last set of security releases and noted a small issue regarding changelog links (potentially unrelated to the PR). 59 | * (Richard) Suggestion to add an option to run individual steps such as regenerating the changelog. 60 | * Rafael volunteered to be assigned to this. 61 | * FYI of the PR for deprecation numbers [nodejs/node-core-utils#685](https://github.com/nodejs/node-core-utils/pull/685) 62 | * Node.js 20 63 | * Rafael is planning the proposal for early April. 64 | * Platforms support 65 | * (Action) Create an issue capturing platforms. 66 | * Reviewing toolchain requirements (gcc 10, C++ 20, etc.) 67 | * Proposal: notable-changes bot comment for summaries [#821](https://github.com/nodejs/Release/issues/821) 68 | * TSC label bot also suggested. 69 | * Beth to take a look at implementing both as it will involve similar logic. -------------------------------------------------------------------------------- /doc/meetings/2023-05-09.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2023-05-09 2 | 3 | ## Links 4 | 5 | * **Recording**: TBD 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/860 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1BryFu_HGM6Z_UJ7rXksHkOjxvbXr_P4ciseMY2XcLg8 8 | 9 | ## Present 10 | 11 | * Release team: @nodejs/release 12 | * LTS team: @nodejs/lts 13 | * Ruy Adorno @ruyadorno 14 | * Darcy Clarke @darcyclarke 15 | * Ulises Gascon @ulisesgascon 16 | * Danielle Adams @danielleadams 17 | * Rishit Dagli @Rishit-dagli 18 | * Harkunwar Kochar @harkunwarkochar 19 | * Wes Todd @wesleytodd 20 | 21 | ## Agenda 22 | 23 | * Overview of agenda & how the Release WG works 24 | * Overview of issues 25 | * Work & releases are organized in the “Releasers” WG repo (ref. https://github.com/nodejs/release/issues/) 26 | * Overview of “Release Process” 27 | * Documentation is great for reference purposes before the team cuts a new Node.js Version (ref. https://github.com/nodejs/node/blob/main/doc/contributing/releases.md) 28 | * A team member will walk through the steps (step-by-step) 29 | * Notably, there are many scripts that run to help with orchestrating the branch/release/tagging 30 | * When there is a “security” release there are often extra steps required for cutting a new release & private orchestration with the Releasers WG 31 | * Danielle #ftw - live updating release versions 32 | 33 | ### nodejs/Release 34 | 35 | * Release plan - v20.x Current [#855](https://github.com/nodejs/Release/issues/855) 36 | * Release plan - v19.x Maintenance [#793](https://github.com/nodejs/Release/issues/793) 37 | * Release plan - v18.x Active LTS [#737](https://github.com/nodejs/Release/issues/737) 38 | * Release plan - v16.x Maintenance [#658](https://github.com/nodejs/Release/issues/658) 39 | * Release plan - v14.x Maintenance LTS [#567](https://github.com/nodejs/Release/issues/567) 40 | 41 | ### nodejs/release-keys 42 | 43 | * v18 and v19 are signed by a public key not captured in this keyring [#21](https://github.com/nodejs/release-keys/issues/21) 44 | 45 | ## Q&A, Other 46 | 47 | * Would be great to automate checking for PRs that need manual backporting ahead of time 48 | 49 | ## Upcoming Meetings 50 | 51 | * **Node.js Project Calendar**: 52 | 53 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 54 | 55 | 56 | -------------------------------------------------------------------------------- /doc/meetings/2023-06-01.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2023-06-01 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/live/-3MgQkKCKJw 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/872 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1VOSFMLhS9DFOLuBMpTIiwa68qTO_pYfXu5r_G3287Bg 8 | 9 | ## Present 10 | 11 | * Release team: @nodejs/release 12 | * LTS team: @nodejs/lts 13 | * Rafael Gonzaga: @RafaelGSS 14 | * Richard Lau: @richardlau 15 | * Ruy Adorno: @ruyadorno 16 | * Juan José: @juanarbol 17 | 18 | ## Agenda 19 | 20 | ## Announcements 21 | 22 | * [Richard] Node.js 19 is now EOL, 20 is the Current version 23 | * [Rafael] PR to node-core-utils to improve/automate the security releases: https://github.com/nodejs/node-core-utils/pull/665 24 | 25 | ### nodejs/Release 26 | 27 | * Release plan - v20.x Current [#855](https://github.com/nodejs/Release/issues/855) 28 | * Release plan - v18.x Active LTS [#737](https://github.com/nodejs/Release/issues/737) 29 | * Release plan - v16.x Maintenance [#658](https://github.com/nodejs/Release/issues/658) 30 | 31 | ### nodejs/release-keys 32 | 33 | * v18 and v19 are signed by a public key not captured in this keyring [#21](https://github.com/nodejs/release-keys/issues/21) 34 | 35 | ## Q&A, Other 36 | 37 | * Looking for volunteers for v16.x and v18.x 38 | * OpenJS Collaborator Summit talks are available on Youtube: https://www.youtube.com/playlist?list=PLyspMSh4XhLO15jJD9Sj069fN18j12AbQ 39 | 40 | ## Upcoming Meetings 41 | 42 | * **Node.js Project Calendar**: 43 | 44 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 45 | 46 | -------------------------------------------------------------------------------- /doc/meetings/2023-06-29.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2023-06-29 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/m1pT4OLhsxo 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/879 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1HZ4WpgrAxzKo6tniB85xLoBHen-787lsbETuuqds8Ag 8 | 9 | ## Present 10 | 11 | * Release team: @nodejs/release 12 | * LTS team: @nodejs/lts 13 | * Richard Lau @richardlau 14 | * Juan Arboleda @juanarbol 15 | * Ruy Adorno @ruyadorno 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | *Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 22 | 23 | ### nodejs/Release 24 | 25 | * Session at the Collaborator Summit [#880](https://github.com/nodejs/Release/issues/880) 26 | * Promotion of the working group to find more releasers. 27 | * We can also promote WG participants that may not necessarily be working on releases. 28 | * [Juan] might invite some more folks to the meeting to share some ideas. 29 | * How to handle "experimental" status when adoption is significant? [TSC/#1397](https://github.com/nodejs/TSC/issues/1397) 30 | * It’s not unexpected that semver major versions will have breaking changes, the important bit is whether that is intentional and what is the proportion of that breakage. 31 | * Who will be working in the next major release? 32 | * [Ruy] No hurry but it is something that we need to start thinking about. 33 | * Release plan - v20.x Current [#855](https://github.com/nodejs/Release/issues/855) 34 | * [Juan] Going to sign up for a release mid-August. 35 | * Release plan - v18.x Active LTS [#737](https://github.com/nodejs/Release/issues/737) 36 | * Danielle is currently working on it, aiming to release next week. 37 | * Release plan - v16.x Maintenance [#658](https://github.com/nodejs/Release/issues/658) 38 | * [Richard] Only thing I’m aware of is we have not updated the timezone information. If we decide to do so we either need a PR that updates just the tzdata in ICU 71.1 in v16.x-staging or do a (potentially risky) backport of ICU 73.2. 39 | 40 | ## Upcoming Meetings 41 | 42 | * **Node.js Project Calendar**: 43 | 44 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 45 | -------------------------------------------------------------------------------- /doc/meetings/2023-07-27.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2023-07-27 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=3UBWEvx0K6A 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/886 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1e5RrT8gXa13JgIds0Nu80Y6vekGePKjtM2K0iSeK_1k 8 | 9 | ## Present 10 | 11 | * Release team: @nodejs/release 12 | * LTS team: @nodejs/lts 13 | * Rafael Gonzaga: @RafaelGSS 14 | * Ulises Gascon: @ulisesGascon 15 | * Ruy Adorno: @ruyadorno 16 | * Richard Lau: @richardlau 17 | * Danielle Adams: @danielleadams 18 | 19 | ## Agenda 20 | 21 | ## Announcements 22 | 23 | *Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 24 | 25 | ### nodejs/Release 26 | 27 | * Session at the Collaborator Summit [#880](https://github.com/nodejs/Release/issues/880) 28 | * Rafael is going to be at the summit but might have a conflicting session at the same time 29 | * Maybe we’ll not hold a Release WG Session this time 30 | * Periodic Table does not have an element starting with "J" or "Q" or "W" [#304](https://github.com/nodejs/Release/issues/304) 31 | * Still looking for a release manager for the upcoming major release (LTS transition for v20) 32 | * Ahead of starting a new major release it might be a good idea to add the tsc-agenda to the proposal PR so that the collaborators can be aware of the upcoming release 33 | * Onboard Ulises 34 | * Once the release team approves an email is sent to the TSC to confirm the nomination 35 | * When that’s approved we look into adding keys, permissions, etc 36 | * Update the release schedule image 37 | * Link to how to perform the update in the repo: https://github.com/nodejs/Release/blob/main/doc/release-guide.md#updating-the-schedulesvg 38 | * Release plan - v20.x Current [#855](https://github.com/nodejs/Release/issues/855) 39 | * Rafael plans to take 2 releases in the month of August, will try to pair with Ulises if possible 40 | * Release plan - v18.x Active LTS [#737](https://github.com/nodejs/Release/issues/737) 41 | * Ruy is going to work on the next v18 mid to end of August 42 | * There is an ICU update that already landed in v20 and would be great to have it land in v18 43 | * Lot’s of backport PRs open 44 | * Release plan - v16.x Maintenance [#658](https://github.com/nodejs/Release/issues/658) 45 | * Richard is planning to work on a v16 release in August 46 | 47 | ## Q&A, Other 48 | 49 | * npm 10 update plan, any concerns about that? 50 | 51 | ## Upcoming Meetings 52 | 53 | * **Node.js Project Calendar**: 54 | 55 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 56 | -------------------------------------------------------------------------------- /doc/meetings/2023-08-24.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2023-08-24 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=TwuwTHR5nvk 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/901 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1TMK5oYIFhhACqXyn15Cma6B_1nsZknkgm34ijctHEgw/edit 8 | 9 | ## Present 10 | 11 | * Release team: @nodejs/release 12 | * LTS team: @nodejs/lts 13 | * UlisesGascon: @ulisesGascon 14 | * Richard Lau: @richardlau 15 | * Rafael Gonzaga: @RafaelGSS 16 | 17 | ## Agenda 18 | 19 | ## Announcements 20 | 21 | *Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 22 | 23 | ### nodejs/Release 24 | 25 | * Plans for npm 10 [#884](https://github.com/nodejs/Release/issues/884) 26 | * Session at the Collaborator Summit [#880](https://github.com/nodejs/Release/issues/880) 27 | * Seems unlikely that any team member will be there 28 | * Issue removed from the agenda 29 | * Release plan - v20.x Current [#855](https://github.com/nodejs/Release/issues/855) 30 | * 20.6.0 proposal is stuck due machine failures, Juan can provide help. 31 | * Schedule updated 32 | * 20.7 will be postponed until 06 Sep. 33 | * Release plan - v18.x Active LTS [#737](https://github.com/nodejs/Release/issues/737) 34 | * Ruy is handling the next v18.x 35 | * It seems to be postponed to next week. 36 | * Release plan - v16.x Maintenance [#658](https://github.com/nodejs/Release/issues/658) 37 | * Richard created a summary of pending PRs to v16.x 38 | * We are not targeting a final release of v16.x. 39 | 40 | ### nodejs/citgm 41 | 42 | * Proposal - Cleanup the modules failing often [#955](https://github.com/nodejs/citgm/issues/955) 43 | * no updates 44 | 45 | 46 | ## Q&A, Other 47 | 48 | ## Upcoming Meetings 49 | 50 | * **Node.js Project Calendar**: 51 | 52 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 53 | 54 | -------------------------------------------------------------------------------- /doc/meetings/2023-10-19.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2023-10-19 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/JKkskOTRVMs 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/937 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1u0snUw7LvDgyFTJYMQLYIH88q1p9peZQT7UAXeP_tQk 8 | 9 | ## Present 10 | 11 | * Beth Griggs (@BethGriggs) 12 | * Kerem Kat @krk 13 | * Marco Ippolito @marco-ippolito 14 | * Michael Zasso @targos 15 | * Rafael Gonzaga: @RafaelGSS 16 | * Richard Lau @richardlau 17 | * Ruy Adorno @ruyadorno 18 | 19 | ## Agenda 20 | 21 | ## Announcements 22 | 23 | * Node.js 21.0.0 was released on Tuesday as planned 🎉 24 | * Node.js 20 will transition to LTS (without functional changes) next week. Richard will open the proposal soon. 25 | 26 | ### nodejs/Release 27 | 28 | * Release volunteer [#936](https://github.com/nodejs/Release/issues/936) 29 | * Release team nomination [#935](https://github.com/nodejs/Release/issues/935) 30 | * Volunteer as a releaser [#926](https://github.com/nodejs/Release/issues/926) 31 | 32 | * Releaser for v21.X [#903](https://github.com/nodejs/Release/issues/903) 33 | * Doing in pairs was good. 34 | * For the next major, prepare a checklist to better split the work. 35 | * Plans for npm 10 [#884](https://github.com/nodejs/Release/issues/884) 36 | * Concern: v18.x will likely be in Maintenance before npm 10 lands on it. 37 | * No objections to landing the npm 10 update. 38 | * Michael volunteered to prepare a release asap. 39 | * Release plan - v20.x Current [#855](https://github.com/nodejs/Release/issues/855) 40 | * Release plan - v18.x Active LTS [#737](https://github.com/nodejs/Release/issues/737) 41 | 42 | ### nodejs/citgm 43 | 44 | * Proposal - Cleanup the modules failing often [#955](https://github.com/nodejs/citgm/issues/955) 45 | * Ongoing effort 46 | 47 | ## Upcoming Meetings 48 | 49 | * **Node.js Project Calendar**: 50 | 51 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 52 | 53 | -------------------------------------------------------------------------------- /doc/meetings/2023-11-16.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2023-11-16 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=L2JrmDV_jkE 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/956 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/19PdX_eRce9RBHsniX6-BVM_dVZEdU12zpN-9WtgCsb4 8 | 9 | ## Present 10 | 11 | * Release team: @nodejs/release 12 | * LTS team: @nodejs/lts 13 | * Ruy Adorno @ruyadorno 14 | * Beth Griggs 15 | * Ulises Gascon @ulisesgascon 16 | * Richard Lau @richardlau 17 | * Yagiz Nizipli @anonrig 18 | * Michael Zasso @targos 19 | 20 | ## Agenda 21 | 22 | ## Announcements 23 | 24 | ### nodejs/Release 25 | 26 | * Release plan - v21.x Active LTS [#855](https://github.com/nodejs/Release/issues/932) 27 | * Well staffed with @RafaelGSS working on the next three releases 28 | * @ulisesgascon volunteered to work on the first release of next year on January 16th 29 | * Release plan - v20.x Active LTS [#855](https://github.com/nodejs/Release/issues/855) 30 | * @targos aiming to release the current proposal next week (November 22nd) 31 | * @ulisesgascon volunteered to work on a release early in December 32 | * Release plan - v18.x Maintenance LTS [#737](https://github.com/nodejs/Release/issues/737) 33 | * @targos is preparing a release to the end of the month (November 28th) 34 | * Proposal for new release schedule / users are not interested in releases that will not become LTS [#953](https://github.com/nodejs/Release/issues/953) 35 | 36 | ## Q&A, Other 37 | 38 | ## Upcoming Meetings 39 | 40 | * **Node.js Project Calendar**: 41 | 42 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 43 | 44 | -------------------------------------------------------------------------------- /doc/meetings/2024-01-11.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2024-01-11 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/OLM6Vily8ME 6 | * **Minutes Google Doc**: https://docs.google.com/document/d/1FyOTwlVYJ0NwJWAJK0hFF4sAYkaMbqgt5PqrYKT1ksw 7 | 8 | ## Present 9 | 10 | * Release team: @nodejs/release 11 | * LTS team: @nodejs/lts 12 | * marco-ippolito: @marco-ippolito 13 | * Rafael Gonzaga: @RafaelGSS 14 | * Richard Lau: @richardlau 15 | * Ruy Adorno: @ruyadorno 16 | 17 | ## Agenda 18 | 19 | ### nodejs/Release 20 | 21 | * Release plan - v21.x Current #932 22 | * Rafael is planning to take the next few releases up to early February, will help Marco Getting onboard and working on automation 23 | * Release plan - v20.x Active LTS #855 24 | * Call for releasers, no one scheduled yet for February and later 25 | * Release plan - v18.x Maintenance LTS #737 26 | * It looks like there are a few patches that might be released at some point, maybe in a security release? 27 | * Plans for npm 10 #884 28 | * Should probably close this release since npm10 update is done with 29 | * Rafael considered open a new issue to talk about future updates of npm 30 | * Richard raised a concern about npm not having an equivalent of LTS releases and keeping old versions of it in node LTS release lines 31 | * Rafael to potentially open a new issue to talk about future of npm updates in the node runtime 32 | * Removed this item from the agenda 33 | * proposal for new release schedule / users are not interested in releases that will not become LTS #953 34 | * Might also have an impact on the npm updates conversation 35 | 36 | ## Q&A, Other 37 | 38 | ## Upcoming Meetings 39 | 40 | * **Node.js Project Calendar**: 41 | 42 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 43 | 44 | -------------------------------------------------------------------------------- /doc/meetings/2024-02-08.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2024-02-08 2 | 3 | ## Links 4 | 5 | * **Recording**: https://youtu.be/w2wqWAbV-L8 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/980 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/12mIcpnvo_hWi61AnHRDjfmcT7BfWmQigC40cQrCllB0 8 | 9 | ## Present 10 | 11 | * Release team: @nodejs/release 12 | * LTS team: @nodejs/lts 13 | * Ruy Adorno @ruyadorno 14 | * Marco Ippolito @marco-ippolito 15 | * Richard Lau @richardlau 16 | * Ulises Gascon: @UlisesGascon 17 | * Juan Arboleda: @juanarbol 18 | 19 | ## Announcements 20 | 21 | * Marco: Security release may be delayed due to issues on Node.js 20. Decision to be made later today. 22 | * Ruy: Collaborator Summit is happening next month in London (3 - 4 April), we should propose a working group session there. Looks like we’ll have a quorum from the release team. 23 | 24 | ## Agenda 25 | 26 | ### nodejs/Release 27 | 28 | * Release plan - v21.x Current #932 29 | * Marco willing to help with Node.js 21 release but not yet a releaser so will need a releaser to pair. 30 | * Action item: Find an available releaser to pair with Marco on a v21 release. 31 | * Release plan - v20.x Active LTS #855 32 | * Node.js 20 and 18 has a npm10 regression on signals that will be fixed landing the update to npm10.3.0 but that needs to be released in a current release first. 33 | * Richard volunteered to work on the next v20 and v18 releases. 34 | * Release plan - v18.x Maintenance LTS #737 35 | * Richard volunteered to work on a release to fix the npm regression mentioned above and will be looking at what else in terms of backport PRs to land. Since this is a maintenance release line it’s up to the releaser to decide on what commits goes in that release. 36 | * proposal for new release schedule / users are not interested in releases that will not become LTS #953 37 | * We need to discuss the proposal as a group and ultimately that decision needs to be made in this Working Group since it has been chartered to make these decisions. 38 | * Richard: We also had a prior proposal from James to implement a more dynamic release schedule in the past that we decided to not move forward with. 39 | * Richard: Disagrees that the current release schedule needs to be changed, noting that data might be highly biased due to CI. We do currently get regular bug reports from folks using the Current release line. 40 | * Ruy: Agree with the points raised by Beth in the GitHub discussion, would like to highlight that changing the release schedule is not something that should be done lightly and would need a very compelling reason to outweigh the disruption, unlearning and tooling / infrastructure changes required to implement it. 41 | * Richard: It’s too late to adopt any change for Node.js v22. 42 | * Marco and Ulisses do not disagree with Richard and Ruy line of thought. 43 | * Action item: Ask the group if anyone strongly disagrees with the points made by Richard and Ruy in the call today, if not let’s form a consensus and close the issue. 44 | * PGP keys verification #965 45 | * Ulisses: Just want to make sure every releaser has their key properly assigned to them on GitHub. Should probably close this issue after that. 46 | 47 | ## Q&A, Other 48 | 49 | * Meeting issue was not populated with agenda items. Richard to reopen #147 50 | 51 | ## Upcoming Meetings 52 | 53 | * **Node.js Project Calendar**: 54 | 55 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 56 | 57 | -------------------------------------------------------------------------------- /doc/meetings/2024-05-30.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2024-05-30 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=jpz0ZhDHS8M 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/1011 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1McsLuKvHCRW-XYB2hKTGOADO-WO84T7QFn07PdT_woI/edit 8 | 9 | ## Present 10 | 11 | * Ulises Gascón: @UlisesGascon 12 | * Marco Ippolito: @marco-ippolito 13 | * Richard Lau: @richardlau 14 | 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | *Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 21 | 22 | ### nodejs/Release 23 | 24 | * Creating a branch rule for non LTS staging branches [#1004](https://github.com/nodejs/Release/issues/1004) 25 | * We discuss and agree about adding a single rule (`staging-*`) to cover this scenario for now and the future. 26 | * This will require changes in the documentation potentially (Marco will lead this) 27 | * Release plan - v22.x Current [#1001](https://github.com/nodejs/Release/issues/1001) 28 | * There are volunteers until June 29 | * Onboarding @aduh95 as a releaser [#999](https://github.com/nodejs/Release/issues/999) 30 | * Antoine already prepared a release 31 | * Ulises to check with Ruy regarding onboarding next steps. 32 | * PGP keys verification [#965](https://github.com/nodejs/Release/issues/965) 33 | * No news from now. Reminder sent on Slack 34 | * Release plan - v21.x Current [#932](https://github.com/nodejs/Release/issues/932) 35 | * No more releases planned and it got drop from the agenda 36 | * Release plan - v20.x Active LTS [#855](https://github.com/nodejs/Release/issues/855) 37 | * Marco is preparing releases until June 38 | * Release plan - v18.x Maintenance LTS [#737](https://github.com/nodejs/Release/issues/737) 39 | * No expectation for new releases right now, but we keep track of dependencies upgrades, as well for testing stability. 40 | 41 | ### nodejs/citgm 42 | 43 | * Node.js latest CITGM results [#1060](https://github.com/nodejs/citgm/issues/1060) 44 | * Brief discussion about the situation but no action pending (yet) 45 | 46 | 47 | 48 | ## Q&A, Other 49 | 50 | * Let’s start thinking about Node.js@23 51 | * Ulises want to get involved into it, but depends on his current availability in Sep/Oct 52 | * What is the current situation of the LTS team? 53 | * We made some discussion about it in the past 54 | * It has an historical context prior to the current Release team, so the organization has evolved since them. 55 | * LTS team does not provide additional access to resources (Ex. Jenkins) 56 | * Marco explained that some documentation might be outdated regarding major releases and the LTS team. 57 | * This PR seems relevant (ignoring the backporting part) https://github.com/nodejs/Release/pull/912 58 | * Marco will open an issue about it 59 | 60 | ## Upcoming Meetings 61 | 62 | * **Node.js Project Calendar**: 63 | 64 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 65 | 66 | -------------------------------------------------------------------------------- /doc/meetings/2024-06-27.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2024-06-27 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=DVjoz044Y8I 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/1021 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1DMNQWELamC4dY3vk1Q78aLXpcoDAnOCa2CQBx5zjmHU/edit 8 | 9 | ## Present 10 | 11 | * Release team: @nodejs/release 12 | * LTS team: @nodejs/lts 13 | * Ulises Gascon: @UlisesGascon 14 | * Richard Lau: @richardlau 15 | * Rafael Gonzaga: @RafaelGSS 16 | * Ruy Adorno: @ruyadorno 17 | * Chemi Atlow: @atlowChemi 18 | * Antoine du Hamel: @aduh95 19 | 20 | ## Agenda 21 | 22 | ## Announcements 23 | 24 | * Security release coming soon 25 | * Potential changes in the process for doing releases due the security automation 26 | * There was an issue with the MacOS machines in the CI, that seems to be solved now 27 | 28 | ### nodejs/Release 29 | 30 | * Current status of LTS group/ backporters [#1012](https://github.com/nodejs/Release/issues/1012) 31 | * Let’s keep it in the agenda for the next meeting 32 | * Creating a branch rule for non LTS staging branches [#1004](https://github.com/nodejs/Release/issues/1004) 33 | * Waiting for a PR on documentation change: https://github.com/nodejs/Release/issues/1004#issuecomment-2139671245 34 | * Antoine suggested an alternative approach that is more friendly to onboarding new releasers by forcing sign commits rather than a branch rule.https://github.com/nodejs/Release/issues/1004#issuecomment-2083622569 35 | * Release plan - v22.x Current [#1001](https://github.com/nodejs/Release/issues/1001) 36 | * Rafael volunteers for the next one 37 | 38 | 39 | * Onboarding @aduh95 as a releaser [#999](https://github.com/nodejs/Release/issues/999) 40 | * Richard volunteers to help with the onboarding tasks that are pending. 41 | * Antoine will prepare another release 42 | * PGP keys verification [#965](https://github.com/nodejs/Release/issues/965) 43 | * It will be removed from the agenda 44 | * Ulises will close the issue as soon as it is ready 45 | * Release plan - v20.x Active LTS [#855](https://github.com/nodejs/Release/issues/855) 46 | * We are looking for volunteers that can help 47 | * Release plan - v18.x Maintenance LTS [#737](https://github.com/nodejs/Release/issues/737) 48 | * Seems like there are some PRs that can land in the next 18.x. https://github.com/nodejs/node/pulls?q=is%3Apr+label%3Alts-watch-v18.x+is%3Aclosed 49 | * We don’t see the need yet to do the release just for this. 50 | 51 | 52 | ### nodejs/citgm 53 | 54 | * Node.js latest CITGM results [#1060](https://github.com/nodejs/citgm/issues/1060) 55 | * Discussion around potential ways to improve the current situation 56 | 57 | 58 | ## Q&A, Other 59 | 60 | ## Upcoming Meetings 61 | 62 | * **Node.js Project Calendar**: 63 | 64 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 65 | 66 | -------------------------------------------------------------------------------- /doc/meetings/2024-07-25.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2024-07-25 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=elnbwd3VL4c 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/1026 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1BRJuBAZ7oTvgA9uFxKo1714Mnh6gHJGK-gpfq0dTo5s/edit 8 | 9 | ## Present 10 | 11 | * Release team: @nodejs/release 12 | * LTS team: @nodejs/lts 13 | * Marco Ippolito @marco-ippolito 14 | * Richard Lau @richardlau 15 | * Ruy Adorno @ruyadorno 16 | * Ulises Gascón @ulisesgascon 17 | 18 | 19 | ## Agenda 20 | 21 | ## Announcements 22 | 23 | No announcements 24 | 25 | ### nodejs/Release 26 | 27 | * Current status of LTS group/ backporters [#1012](https://github.com/nodejs/Release/issues/1012) 28 | * Keep backporters to allow non-releasers to prepare releases 29 | * The LTS team was created before the release WG (Historical context) 30 | * Later on the idea was to focus the team on LTS policy efforts 31 | * Note: this team does not provide you access to additional infra resources or permissions 32 | * Next action: Seems like we can remove the team, Marco will lead this. 33 | * Creating a branch rule for non LTS staging branches [#1004](https://github.com/nodejs/Release/issues/1004) 34 | * Consensus on adding backporters team to the rule and also agreement for sign commits. For reference: https://github.com/nodejs/Release/issues/1004#issuecomment-2196798542 35 | * Next step: Add a note in the issue and apply the change. Also inform the TC. (Potentially Richard can lead it in a few week’s time) 36 | * Onboarding @aduh95 as a releaser [#999](https://github.com/nodejs/Release/issues/999) 37 | * No objections from the team so far, we feel confident. Waiting for Antoine decision. 38 | * Release plan - v22.x Current [#1001](https://github.com/nodejs/Release/issues/1001) 39 | * Rafael volunteer 40 | * Release plan - v20.x Active LTS [#855](https://github.com/nodejs/Release/issues/855) 41 | * Marco can volunteer 42 | * Release plan - v18.x Maintenance LTS [#737](https://github.com/nodejs/Release/issues/737) 43 | * No rush to make a release with the current changes in staging. Probably we do a release before the end of the year. 44 | 45 | ### nodejs/citgm 46 | 47 | * Node.js latest CITGM results [#1060](https://github.com/nodejs/citgm/issues/1060) 48 | * Discussion around potential ways to improve the current situation 49 | 50 | 51 | 52 | 53 | ## Q&A, Other 54 | 55 | ## Upcoming Meetings 56 | 57 | * **Node.js Project Calendar**: 58 | 59 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 60 | 61 | -------------------------------------------------------------------------------- /doc/meetings/2024-09-19.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2024-09-19 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=ZaPFwrlxErE 6 | * **GitHub Issue**: 7 | * **Minutes Google Doc**: 8 | 9 | ## Present 10 | 11 | * Release team: @nodejs/release 12 | * LTS team: @nodejs/lts 13 | * Marco Ippolito (@marco-ippolito) 14 | * Antoine du Hamel (@aduh95) 15 | * Rafael Gonzaga (@RafaelGSS) 16 | * Richard Lau (@richardlau) 17 | 18 | ## Agenda 19 | 20 | ## Announcements 21 | 22 | *Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 23 | 24 | ### nodejs/Release 25 | 26 | * Current status of LTS group/ backporters [#1012](https://github.com/nodejs/Release/issues/1012) 27 | * Marco will proceed to merge LTS group to release and close the issue. 28 | * Creating a branch rule for non LTS staging branches [#1004](https://github.com/nodejs/Release/issues/1004) 29 | * Consensus is that only releasers and backporters should be able to push on staging branches, waiting for a volunteer to update the rule. 30 | * Release plan - v22.x Current [#1001](https://github.com/nodejs/Release/issues/1001) 31 | * Rafael volunteering for next 22 release in October. 32 | * v22 will be promoted to LTS the 29th of October. 33 | * v23 needs to be released, looking for volunteers. 34 | * Onboarding @aduh95 as a releaser [#999](https://github.com/nodejs/Release/issues/999) 35 | * Antoine ready to be onboarded. 36 | * Richard to reach out re. gpg and ssh keys and complete onboarding steps. 37 | * Release plan - v20.x Active LTS [#855](https://github.com/nodejs/Release/issues/855) 38 | * Rafael: that we need more volunteers. Should re-evaluate the current list of releasers, ask to inactive to offboard and try to get more volunteers. 39 | * Richard: collab summit would be a good place to discuss about this 40 | * Marco: we should have a session in the next collab summit 41 | * Last release before v20 goes to maintenance, Marco volunteers for the next v20 in October. 42 | * Release plan - v18.x Maintenance LTS [#737](https://github.com/nodejs/Release/issues/737) 43 | * Possibly one release before the end of the Year (maybe security release) 44 | * Some issues with OpenSSL updates, should be released on v22 and backported. 45 | 46 | ### nodejs/citgm 47 | 48 | * Node.js latest CITGM results [#1060](https://github.com/nodejs/citgm/issues/1060) 49 | * Rafael has fixed some issues in CITGM 50 | 51 | ## Q&A, Other 52 | 53 | ## Upcoming Meetings 54 | 55 | * **Node.js Project Calendar**: 56 | 57 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 58 | -------------------------------------------------------------------------------- /doc/meetings/2024-10-17.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2024-10-17 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=MDrN5_XVi2o&ab_channel=node.js 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/1043 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/10pB9bzTGHZoLnsX5OX554b0sxKfY5qP7btvVUFni-7U/edit?tab=t.0 8 | 9 | ## Present 10 | 11 | * Release team: @nodejs/release 12 | * LTS team: @nodejs/lts 13 | * Marco Ippolito (@marco-ippolito) 14 | * Rafael Gonzaga (@RafaelGS) 15 | * Richard Lau (@richardlau) 16 | * Ruy Adorno (@ruyadorno) 17 | * Gürgün Dayıoğlu 18 | 19 | ## Agenda 20 | 21 | ## Announcements 22 | 23 | *Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 24 | 25 | * Node.js 23.0.0 and 22.10.0 released this week. 26 | * Node.js 22.10.0 was the last release before Node.js 22 become LTS. 27 | 28 | ### nodejs/Release 29 | 30 | * @nodejs/releasers health #1036 31 | * One remaining step to off-boarding Bryan, Danielle and Beth 32 | 33 | * Node.js 23 release plan #1034 34 | * Closing as completed 35 | * We can use this issue as a reference for Node.js 24 36 | 37 | * Creating a branch rule for non-LTS staging branches #1004 38 | * Need to enact the change(s). 39 | 40 | * Release plan - v22.x Current #1001 41 | * Richard will work on the transition to LTS 42 | 43 | * Onboarding @aduh95 as a releaser #999 44 | * Antoine released Node.js 22.10.0 45 | * Richard will double-check the issue and then close it as completed 46 | 47 | * Release plan - v20.x Active LTS #855 48 | * Marco volunteered to perform a v20 release after its maintenance start 49 | 50 | * Release plan - v18.x Maintenance LTS #737 51 | * Rafael will check if we’ll issue a new security release to include the OpenSSL fix 52 | * Richard: There’s one additional bug fix that would be worth it to include in a future release of v18.x 53 | 54 | ### nodejs/citgm 55 | 56 | * Node.js latest CITGM results #1060 57 | * Marco and Richard will check the results of Node.js 22.x when making the transition to LTS 58 | 59 | ## Q&A, Other 60 | 61 | * v23.x came with a regression on npm-pack. CITGM didn’t catch it because npm always fail on CITGM (https://github.com/nodejs/node/issues/55410) 62 | 63 | ## Upcoming Meetings 64 | 65 | * **Node.js Project Calendar**: 66 | 67 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 68 | 69 | -------------------------------------------------------------------------------- /doc/meetings/2024-12-12.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2024-12-12 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=xhiA6qJdIu8 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/1064 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1DxNxqf85wvd6aVhZeOLif1X6cWYwytlAb3uVos6XpYQ 8 | 9 | ## Present 10 | 11 | * Release team: @nodejs/release 12 | * Ruy Adorno @ruyadorno 13 | * Michael Zasso @targos 14 | * Rafael Gonzaga: @RafaelGSS 15 | * Antoine du Hamel @aduh95 16 | * Richard Lau: @richardlau 17 | 18 | ## Announcements 19 | 20 | * Richard: Have added additional tooling to check release assets on R2 staging prior to promotion. 21 | 22 | ## Agenda 23 | 24 | ### nodejs/node 25 | 26 | * Warning for import assertions [#55873](https://github.com/nodejs/node/pull/55873) 27 | * It can no longer be removed when using the disable warning flag since the warning comes from v8 28 | 29 | ### nodejs/Release 30 | 31 | * create-release-proposal Roadmap [#1061](https://github.com/nodejs/Release/issues/1061) 32 | * Fixed the attribution in the changelog but the commit is still authored by the bot 33 | * Potential to use the automation to also update the staging branch after editing it to remove a commit or change something 34 | * Antoine: I don't think that’s feasible without regressing on the security – currently commits landing on staging branches are signed by a trusted backporter, the automation would be much easier to impersonate. 35 | * Richard: having a shared signing key would require a bigger discussion, it would also be more risky as if it leaks, the whole Release team is compromised – compared to the current situation where, if a releaser private key leaks, it only affects them. 36 | * Backport queue automation PR [#56143](https://github.com/nodejs/node/pull/56143) 37 | * Antoine clarified that the goal is to have it be just an early validation of commits that will land cleanly while getting a report on what commits will need backporting 38 | * `git node staging` node-core-utils command [nodejs/node-core-utils/#875](https://github.com/nodejs/node-core-utils/pull/875) 39 | * Antoine would prefer to have an option for it to be interactive waiting for the releaser to decide on whether to amend the commit and continue or to skip and properly label the original PR with the backport requested label. 40 | * Release plan - v23.x Current [#1045](https://github.com/nodejs/Release/issues/1045) 41 | * Rafael will sign up to cut the next release 42 | * Release plan - v22.x Active LTS [#1001](https://github.com/nodejs/Release/issues/1001) 43 | * Ruy signed up to work on a release early in January 44 | * Release plan - v20.x Maintenance LTS [#855](https://github.com/nodejs/Release/issues/855) 45 | * Michael volunteered to work on the next release 46 | 47 | ## Upcoming Meetings 48 | 49 | * **Node.js Project Calendar**: 50 | 51 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 52 | 53 | -------------------------------------------------------------------------------- /doc/meetings/2025-05-29.md: -------------------------------------------------------------------------------- 1 | # Node.js Release WorkGroup Meeting 2025-05-29 2 | 3 | ## Links 4 | 5 | * **Recording**: https://www.youtube.com/watch?v=mHK3k9vfx0M&ab_channel=node.js 6 | * **GitHub Issue**: https://github.com/nodejs/Release/issues/1092 7 | * **Minutes Google Doc**: https://docs.google.com/document/d/1gg5-U-pGNN8aM4ktjlPzQmIW5ohSL3bAiwohAVxm9qc/edit?pli=1&tab=t.0 8 | 9 | ## Present 10 | 11 | * Rafael Gonzaga: @RafaelGSS 12 | * Marco Ippolito: @marco-ippolito 13 | * Richard Lau: @richardlau 14 | * Ruy Adorno: @ruyadorno 15 | 16 | ## Agenda 17 | 18 | ## Announcements 19 | 20 | *Extracted from **Release-agenda** labelled issues and pull requests from the **nodejs org** prior to the meeting. 21 | 22 | All the present releasers agreed to land https://github.com/nodejs/node/pull/58293 as a semver-minor release for Node.js v24 and then add baking for LTS to Node.js 22 and 20. 23 | 24 | ### nodejs/Release 25 | 26 | * Release plan - v24.x Current #1089 27 | * Rafael will do the next v24 release 28 | * Release plan - v23.x Current #1045 29 | * Removed from the agenda. It goes EOL next week. 30 | * @nodejs/releasers health #1036 31 | * Closing as completed 32 | * Release plan - v22.x Active LTS #1001 33 | * We need a volunteer for Node.js 22 release (June 21) 34 | * Release plan - v20.x Maintenance LTS #855 35 | * Marco will do the next v20 release 36 | 37 | 38 | 39 | ## Q&A, Other 40 | 41 | ## Upcoming Meetings 42 | 43 | * **Node.js Project Calendar**: 44 | 45 | Click `+GoogleCalendar` at the bottom right to add to your own Google calendar. 46 | 47 | -------------------------------------------------------------------------------- /doc/release-guide.md: -------------------------------------------------------------------------------- 1 | # Release Guidance 2 | 3 | Guidance related to the management of Node.js releases and the release schedule. 4 | 5 | *Note: The process of creating a release is documented in the [releases.md](https://github.com/nodejs/node/blob/master/doc/contributing/releases.md) file in the Node.js core repository.* 6 | 7 | # Updating the Release Schedule 8 | 9 | When making amendments to the release schedule, the following files in this repository should be updated: 10 | * `schedule.json` - The JSON file should be updated to reflect the added or amended dates/entries. 11 | * `README.md` - The [Release Schedule Table](https://github.com/nodejs/Release#release-schedule) should be updated. 12 | * `schedule.svg` - The timeline graphic should be regenerated. See [Updating the schedule.svg](#updating-the-schedulesvg) 13 | 14 | # Updating the `schedule.svg` 15 | 16 | The following commands can be used to regenerate the `schedule.svg`: 17 | 18 | ```sh 19 | $ npx lts --start yyyy-mm-dd --end yyyy-mm-dd -d "$PWD/schedule.json" -g "$PWD/schedule.svg" 20 | $ npx svgo "$PWD/schedule.svg" 21 | ``` 22 | 23 | The start and end dates should be selected so that, at least, all currently supported versions and the next (upcoming) major version of Node.js are shown. The timeline graphic should be periodically moved forward. 24 | -------------------------------------------------------------------------------- /generateReleasePlan.cjs: -------------------------------------------------------------------------------- 1 | #!/usr/bin/env node 2 | 3 | 'use strict'; 4 | // Generate Release Plan table for a given release line. 5 | // Usage: 6 | // node --harmony-temporal generateReleasePlan.cjs vxx 7 | 8 | const schedule = require('./schedule.json'); 9 | 10 | const [,, version] = process.argv; 11 | 12 | if (!Object.hasOwn(schedule, version)) { 13 | throw new Error(`Unknown version ${version}, accepted values are ${Object.keys(schedule)}`); 14 | } 15 | 16 | console.log(`_Draft schedule - all dates subject to change_ 17 | 18 | Version | Release Date | Releaser 19 | --------|--------------| -------------`); 20 | 21 | const { start, maintenance, lts } = schedule[version]; 22 | 23 | const ltsDateTime = lts && Temporal.PlainDate.from(lts); 24 | const maintenanceDateTime = Temporal.PlainDate.from(maintenance); 25 | 26 | const isNowDuringLTS = lts && Temporal.PlainDate.compare(Temporal.Now.plainDateTimeISO(), ltsDateTime) > 0; 27 | 28 | const startOfCycle = isNowDuringLTS ? ltsDateTime : Temporal.PlainDate.from(start); 29 | const endOfCycle = isNowDuringLTS ? maintenanceDateTime : ltsDateTime || maintenanceDateTime; 30 | 31 | const weeks = isNowDuringLTS ? 4 : 2; 32 | 33 | for (let i = startOfCycle; Temporal.PlainDate.compare(i, endOfCycle) === -1; i = i.add({ weeks })) { 34 | console.log(`${version}.x.x | ${i} | `); 35 | } 36 | 37 | if (lts) { 38 | console.log( 39 | `${version}.x.x (${isNowDuringLTS ? 'Maintenance' : 'LTS'} transition) | ${ 40 | isNowDuringLTS ? maintenance : lts 41 | } | ${isNowDuringLTS ? '_No release_' : ''}`, 42 | ); 43 | } 44 | -------------------------------------------------------------------------------- /schedule.json: -------------------------------------------------------------------------------- 1 | { 2 | "v0.8": { 3 | "start": "2012-06-25", 4 | "end": "2014-07-31" 5 | }, 6 | "v0.10": { 7 | "start": "2013-03-11", 8 | "end": "2016-10-31" 9 | }, 10 | "v0.12": { 11 | "start": "2015-02-06", 12 | "end": "2016-12-31" 13 | }, 14 | "v4": { 15 | "start": "2015-09-08", 16 | "lts": "2015-10-12", 17 | "maintenance": "2017-04-01", 18 | "end": "2018-04-30", 19 | "codename": "Argon" 20 | }, 21 | "v5": { 22 | "start": "2015-10-29", 23 | "maintenance": "2016-04-30", 24 | "end": "2016-06-30" 25 | }, 26 | "v6": { 27 | "start": "2016-04-26", 28 | "lts": "2016-10-18", 29 | "maintenance": "2018-04-30", 30 | "end": "2019-04-30", 31 | "codename": "Boron" 32 | }, 33 | "v7": { 34 | "start": "2016-10-25", 35 | "maintenance": "2017-04-30", 36 | "end": "2017-06-30" 37 | }, 38 | "v8": { 39 | "start": "2017-05-30", 40 | "lts": "2017-10-31", 41 | "maintenance": "2019-01-01", 42 | "end": "2019-12-31", 43 | "codename": "Carbon" 44 | }, 45 | "v9": { 46 | "start": "2017-10-01", 47 | "maintenance": "2018-04-01", 48 | "end": "2018-06-30" 49 | }, 50 | "v10": { 51 | "start": "2018-04-24", 52 | "lts": "2018-10-30", 53 | "maintenance": "2020-05-19", 54 | "end": "2021-04-30", 55 | "codename": "Dubnium" 56 | }, 57 | "v11": { 58 | "start": "2018-10-23", 59 | "maintenance": "2019-04-22", 60 | "end": "2019-06-01" 61 | }, 62 | "v12": { 63 | "start": "2019-04-23", 64 | "lts": "2019-10-21", 65 | "maintenance": "2020-11-30", 66 | "end": "2022-04-30", 67 | "codename": "Erbium" 68 | }, 69 | "v13": { 70 | "start": "2019-10-22", 71 | "maintenance": "2020-04-01", 72 | "end": "2020-06-01" 73 | }, 74 | "v14": { 75 | "start": "2020-04-21", 76 | "lts": "2020-10-27", 77 | "maintenance": "2021-10-19", 78 | "end": "2023-04-30", 79 | "codename": "Fermium" 80 | }, 81 | "v15": { 82 | "start": "2020-10-20", 83 | "maintenance": "2021-04-01", 84 | "end": "2021-06-01" 85 | }, 86 | "v16": { 87 | "start": "2021-04-20", 88 | "lts": "2021-10-26", 89 | "maintenance": "2022-10-18", 90 | "end": "2023-09-11", 91 | "codename": "Gallium" 92 | }, 93 | "v17": { 94 | "start": "2021-10-19", 95 | "maintenance": "2022-04-01", 96 | "end": "2022-06-01" 97 | }, 98 | "v18": { 99 | "start": "2022-04-19", 100 | "lts": "2022-10-25", 101 | "maintenance": "2023-10-18", 102 | "end": "2025-04-30", 103 | "codename": "Hydrogen" 104 | }, 105 | "v19": { 106 | "start": "2022-10-18", 107 | "maintenance": "2023-04-01", 108 | "end": "2023-06-01" 109 | }, 110 | "v20": { 111 | "start": "2023-04-18", 112 | "lts": "2023-10-24", 113 | "maintenance": "2024-10-22", 114 | "end": "2026-04-30", 115 | "codename": "Iron" 116 | }, 117 | "v21": { 118 | "start": "2023-10-17", 119 | "maintenance": "2024-04-01", 120 | "end": "2024-06-01" 121 | }, 122 | "v22": { 123 | "start": "2024-04-24", 124 | "lts": "2024-10-29", 125 | "maintenance": "2025-10-21", 126 | "end": "2027-04-30", 127 | "codename": "Jod" 128 | }, 129 | "v23": { 130 | "start": "2024-10-16", 131 | "maintenance": "2025-04-01", 132 | "end": "2025-06-01" 133 | }, 134 | "v24": { 135 | "start": "2025-05-06", 136 | "lts": "2025-10-28", 137 | "maintenance": "2026-10-20", 138 | "end": "2028-04-30", 139 | "codename": "" 140 | } 141 | } 142 | --------------------------------------------------------------------------------