F35 Change: Node.js 16.x by default (System-Wide Change proposal)

[Ben Cotton]

https://fedoraproject.org/wiki/Changes/Nodejs16

== Summary ==
The latest release of Node.js to carry a 30-month lifecycle is the
16.x series. As with 14.x, 12.x, 10.x and 8.x before it, Fedora 35
will carry 16.x as the default Node.js interpreter for the system. The
14.x and 12.x interpreters will remain available as non-default module
streams.

== Owner ==
* Name: [[User:zvetlik| Zuzana Svetlikova]]
* Email: [e-mail]
* Name: [[User:Sgallagh| Stephen Gallagher]]
* Email: [e-mail]
* Responsible SIG: Node.js SIG

== Detailed Description ==
Fedora 35 will ship with the latest LTS version of Node.js. '''dnf
install nodejs''' will give users nodejs-16.x and the matching npm
package.

== Benefit to Fedora ==
Node.js is a popular server-side JavaScript engine. Keeping Fedora on
the latest release allows us to continue tracking the state-of-the-art
in that space. For those whose applications do not yet work with the
16.x release, Fedora 35 will also have the 14.x and 12.x releases
available as selectable module streams.

== Scope ==
* Proposal owners: The packages are already built for Fedora 33, 34
and 35 in a non-default module stream. On June 14th, 2021, the
nodejs-16.x packages will be built in the non-modular repository and
thus become the default in Fedora 35.

* Other developers: Any developer with a package that depends on
Node.js at run-time or build-time should test with the 16.x module
stream enabled as soon as possible. Issues should be reported to
[e-mail]

* Release engineering: We will coordinate with the Node.js SIG to
create a side-tag to perform the rebuilds before making 16.x the
default.
* Policies and guidelines: N/A (not needed for this Change)
* Trademark approval: N/A (not needed for this Change)

== Upgrade/compatibility impact ==
As with previous releases, users running Fedora 33 or Fedora 34 with
the non-modular nodejs-14.x packages will be automatically upgraded to
the 16.x packages when they upgrade to Fedora 35, which may cause
issues. If users are running software known not to support Node.js
16.x yet, they can switch the system to use 14.x with '''dnf module'''
commands.

== How To Test ==
* Confirm that `dnf install nodejs` results in Node.js 16.x being installed.
* Confirm that upgrading from Fedora 33 or Fedora 34 with nodejs-14.x
installed (non-modular) results in an upgrade to nodejs-16.x
* Confirm that upgrading from Fedora 33 or Fedora 34 with the
`nodejs:14` module enabled does *not* result in an upgrade to 16.x and
still has `nodejs:14` enabled on Fedora 35.
* Confirm that upgrading from Fedora 33 or Fedora 34 with the
`nodejs:16` module enabled upgrades successfully and still has
`nodejs:16` enabled on Fedora 33.

== User Experience ==
Users will have the 16.x release of Node.js available by default. See
the "Upgrade/compatibility impact" section for specific details.

== Dependencies ==
All packages prefixed with `nodejs-` depend on this package. If they
do not work with Node.js 16.x, they will need to be updated, made
modular and dependent upon the `nodejs:14` stream or else removed from
Fedora 35.

Prior to the switchover date to Node.js 16.x as the default, packagers
are strongly encouraged to test their existing Node modules with 16.x
via the Modular version by running:

<pre>
dnf module reset nodejs
dnf module install nodejs:16/development
</pre>

Packagers can also test their builds using `mock` by creating the file
`/etc/mock/fedora-rawhide-x86_64-nodejs16.cfg` with the following
contents:

<pre>
config_opts['target_arch'] = 'x86_64'
config_opts['legal_host_arches'] = ('x86_64',)
config_opts['enable_disable_repos'] = ['--enablerepo', 'rawhide-modular']
config_opts['module_install'] = ['nodejs:16/development']

include('templates/fedora-rawhide.tpl')
</pre>

Then call
<pre>
mock -r fedora-rawhide-x86_64-nodejs16 --enablerepo=rawhide-modular nodejs-foo
</pre>

(Note that the `--enablerepo=rawhide-modular` portion looks redundant,
but this is because of
[https://github.com/rpm-software-management/mock/issues/591 a mock
bug])

== Contingency Plan ==
* Contingency mechanism:
Revert to Node.js 14.x as the default Node.js interpreter. This will
require bumping epoch.

* Contingency deadline: Beta Freeze
* Blocks release? No
* Blocks product? No

== Documentation ==
* https://nodejs.org/dist/latest-v16.x/docs/api/
* https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V16.md

== Release Notes ==
Fedora 35 now ships with Node.js 16.x as the default Node.js
JavaScript server-side engine. If your applications are not yet ready
for this newer version, you can revert to the 14.x series by running
the following commands

<pre>
dnf remove nodejs
dnf module reset nodejs
dnf module install nodejs:14
</pre>

[Miro Hrončok]

On 29. 04. 21 21:14, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/Nodejs16
>
> == Summary ==
> The latest release of Node.js to carry a 30-month lifecycle is the
> 16.x series. As with 14.x, 12.x, 10.x and 8.x before it, Fedora 35
> will carry 16.x as the default Node.js interpreter for the system. The
> 14.x and 12.x interpreters will remain available as non-default module
> streams.
> ...snip...

I just wanted to say that this is very nicely crafted change proposal, thanks!

[Stephen Gallagher]

Just a quick reminder, this switch will be occurring in a little over
three weeks, so make sure to test your NPM packages with Node.js 16.x!

On Thu, Apr 29, 2021 at 3:46 PM Ben Cotton  wrote:
> https://fedoraproject.org/wiki/Changes/Nodejs16
>
> == Summary ==
> The latest release of Node.js to carry a 30-month lifecycle is the
> 16.x series. As with 14.x, 12.x, 10.x and 8.x before it, Fedora 35
> will carry 16.x as the default Node.js interpreter for the system. The
> 14.x and 12.x interpreters will remain available as non-default module
> streams.
>
> == Owner ==
> Name: [[User:zvetlik| Zuzana Svetlikova]]
> Email: [e-mail]
> Name: [[User:Sgallagh| Stephen Gallagher]]
> Email: [e-mail]
> Responsible SIG: Node.js SIG
>
> == Detailed Description ==
> Fedora 35 will ship with the latest LTS version of Node.js. '''dnf
> install nodejs''' will give users nodejs-16.x and the matching npm
> package.
>
> == Benefit to Fedora ==
> Node.js is a popular server-side JavaScript engine. Keeping Fedora on
> the latest release allows us to continue tracking the state-of-the-art
> in that space. For those whose applications do not yet work with the
> 16.x release, Fedora 35 will also have the 14.x and 12.x releases
> available as selectable module streams.
>
> == Scope ==
> Proposal owners: The packages are already built for Fedora 33, 34
>
> and 35 in a non-default module stream. On June 14th, 2021, the
> nodejs-16.x packages will be built in the non-modular repository and
> thus become the default in Fedora 35.
> Other developers: Any developer with a package that depends on
>
> Node.js at run-time or build-time should test with the 16.x module
> stream enabled as soon as possible. Issues should be reported to
> [e-mail]
> Release engineering: We will coordinate with the Node.js SIG to
>
> create a side-tag to perform the rebuilds before making 16.x the
> default.
> Policies and guidelines: N/A (not needed for this Change)
> Trademark approval: N/A (not needed for this Change)
>
> == Upgrade/compatibility impact ==
> As with previous releases, users running Fedora 33 or Fedora 34 with
> the non-modular nodejs-14.x packages will be automatically upgraded to
> the 16.x packages when they upgrade to Fedora 35, which may cause
> issues. If users are running software known not to support Node.js
> 16.x yet, they can switch the system to use 14.x with '''dnf module'''
> commands.
>
> == How To Test ==
> Confirm that `dnf install nodejs` results in Node.js 16.x being installed.
> Confirm that upgrading from Fedora 33 or Fedora 34 with nodejs-14.x
>
> installed (non-modular) results in an upgrade to nodejs-16.x
> Confirm that upgrading from Fedora 33 or Fedora 34 with the
>
> `nodejs:14` module enabled does *not* result in an upgrade to 16.x and
> still has `nodejs:14` enabled on Fedora 35.
> Confirm that upgrading from Fedora 33 or Fedora 34 with the
>
> `nodejs:16` module enabled upgrades successfully and still has
> `nodejs:16` enabled on Fedora 33.
>
> == User Experience ==
> Users will have the 16.x release of Node.js available by default. See
> the "Upgrade/compatibility impact" section for specific details.
>
> == Dependencies ==
> All packages prefixed with `nodejs-` depend on this package. If they
> do not work with Node.js 16.x, they will need to be updated, made
> modular and dependent upon the `nodejs:14` stream or else removed from
> Fedora 35.
>
> Prior to the switchover date to Node.js 16.x as the default, packagers
> are strongly encouraged to test their existing Node modules with 16.x
> via the Modular version by running:
>
> <pre>
> dnf module reset nodejs
> dnf module install nodejs:16/development
> </pre>
>
> Packagers can also test their builds using `mock` by creating the file
> `/etc/mock/fedora-rawhide-x86_64-nodejs16.cfg` with the following
> contents:
>
> <pre>
> config_opts['target_arch'] = 'x86_64'
> config_opts['legal_host_arches'] = ('x86_64',)
> config_opts['enable_disable_repos'] = ['--enablerepo', 'rawhide-modular']
> config_opts['module_install'] = ['nodejs:16/development']
>
> include('templates/fedora-rawhide.tpl')
> </pre>
>
> Then call
>
> <pre>
> mock -r fedora-rawhide-x86_64-nodejs16 --enablerepo=rawhide-modular nodejs-foo
> </pre>
>
> (Note that the `--enablerepo=rawhide-modular` portion looks redundant,
> but this is because of
> [https://github.com/rpm-software-management/mock/issues/591 a mock
> bug])
>
> == Contingency Plan ==
> Contingency mechanism:
>
> Revert to Node.js 14.x as the default Node.js interpreter. This will
> require bumping epoch.
> Contingency deadline: Beta Freeze
> Blocks release? No
> Blocks product? No
>
> == Documentation ==
> https://nodejs.org/dist/latest-v16.x/docs/api/
> https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V16.md
>
> == Release Notes ==
> Fedora 35 now ships with Node.js 16.x as the default Node.js
> JavaScript server-side engine. If your applications are not yet ready
> for this newer version, you can revert to the 14.x series by running
> the following commands
>
> <pre>
> dnf remove nodejs
> dnf module reset nodejs
> dnf module install nodejs:14
> </pre>
>
> --
> Ben Cotton
> He / Him / His
> Senior Program Manager, Fedora & CentOS Stream
> Red Hat
> TZ=America/Indiana/Indianapolis
> _______________________________________________
> devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]
> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Stephen Gallagher]

I'm a little behind on this, but I've created side-tag
f35-build-side-42997 to perform any necessary nodejs-* rebuilds.
Currently I'm only aware of the `nodejs` and `R-V8` packages needing
to be rebuilt there. Most Node.js packages don't have a tight
dependency on the interpreter. If you have a package that needs to be
rebuilt against Node.js 16 (currently 16.4.0), please let me know
immediately, as well as whether you want me to rebuild it for you or
you will be doing it yourself in the side-tag.

On Thu, May 27, 2021 at 10:11 AM Stephen Gallagher  wrote:
> Just a quick reminder, this switch will be occurring in a little over
> three weeks, so make sure to test your NPM packages with Node.js 16.x!
>
> On Thu, Apr 29, 2021 at 3:46 PM Ben Cotton  wrote:
> > https://fedoraproject.org/wiki/Changes/Nodejs16
> >
> > == Summary ==
> > The latest release of Node.js to carry a 30-month lifecycle is the
> > 16.x series. As with 14.x, 12.x, 10.x and 8.x before it, Fedora 35
> > will carry 16.x as the default Node.js interpreter for the system. The
> > 14.x and 12.x interpreters will remain available as non-default module
> > streams.
> >
> > == Owner ==
> > Name: [[User:zvetlik| Zuzana Svetlikova]]
> > Email: [e-mail]
> > Name: [[User:Sgallagh| Stephen Gallagher]]
> > Email: [e-mail]
> > Responsible SIG: Node.js SIG
> >
> > == Detailed Description ==
> > Fedora 35 will ship with the latest LTS version of Node.js. '''dnf
> > install nodejs''' will give users nodejs-16.x and the matching npm
> > package.
> >
> > == Benefit to Fedora ==
> > Node.js is a popular server-side JavaScript engine. Keeping Fedora on
> > the latest release allows us to continue tracking the state-of-the-art
> > in that space. For those whose applications do not yet work with the
> > 16.x release, Fedora 35 will also have the 14.x and 12.x releases
> > available as selectable module streams.
> >
> > == Scope ==
> > Proposal owners: The packages are already built for Fedora 33, 34
> >
> > and 35 in a non-default module stream. On June 14th, 2021, the
> > nodejs-16.x packages will be built in the non-modular repository and
> > thus become the default in Fedora 35.
> > Other developers: Any developer with a package that depends on
> >
> > Node.js at run-time or build-time should test with the 16.x module
> > stream enabled as soon as possible. Issues should be reported to
> > [e-mail]
> > Release engineering: We will coordinate with the Node.js SIG to
> >
> > create a side-tag to perform the rebuilds before making 16.x the
> > default.
> > Policies and guidelines: N/A (not needed for this Change)
> > Trademark approval: N/A (not needed for this Change)
> >
> > == Upgrade/compatibility impact ==
> > As with previous releases, users running Fedora 33 or Fedora 34 with
> > the non-modular nodejs-14.x packages will be automatically upgraded to
> > the 16.x packages when they upgrade to Fedora 35, which may cause
> > issues. If users are running software known not to support Node.js
> > 16.x yet, they can switch the system to use 14.x with '''dnf module'''
> > commands.
> >
> > == How To Test ==
> > Confirm that `dnf install nodejs` results in Node.js 16.x being installed.
> > Confirm that upgrading from Fedora 33 or Fedora 34 with nodejs-14.x
> >
> > installed (non-modular) results in an upgrade to nodejs-16.x
> > Confirm that upgrading from Fedora 33 or Fedora 34 with the
> >
> > `nodejs:14` module enabled does *not* result in an upgrade to 16.x and
> > still has `nodejs:14` enabled on Fedora 35.
> > Confirm that upgrading from Fedora 33 or Fedora 34 with the
> >
> > `nodejs:16` module enabled upgrades successfully and still has
> > `nodejs:16` enabled on Fedora 33.
> >
> > == User Experience ==
> > Users will have the 16.x release of Node.js available by default. See
> > the "Upgrade/compatibility impact" section for specific details.
> >
> > == Dependencies ==
> > All packages prefixed with `nodejs-` depend on this package. If they
> > do not work with Node.js 16.x, they will need to be updated, made
> > modular and dependent upon the `nodejs:14` stream or else removed from
> > Fedora 35.
> >
> > Prior to the switchover date to Node.js 16.x as the default, packagers
> > are strongly encouraged to test their existing Node modules with 16.x
> > via the Modular version by running:
> >
> > <pre>
> > dnf module reset nodejs
> > dnf module install nodejs:16/development
> > </pre>
> >
> > Packagers can also test their builds using `mock` by creating the file
> > `/etc/mock/fedora-rawhide-x86_64-nodejs16.cfg` with the following
> > contents:
> >
> > <pre>
> > config_opts['target_arch'] = 'x86_64'
> > config_opts['legal_host_arches'] = ('x86_64',)
> > config_opts['enable_disable_repos'] = ['--enablerepo', 'rawhide-modular']
> > config_opts['module_install'] = ['nodejs:16/development']
> >
> > include('templates/fedora-rawhide.tpl')
> > </pre>
> >
> > Then call
> >
> > <pre>
> > mock -r fedora-rawhide-x86_64-nodejs16 --enablerepo=rawhide-modular nodejs-foo
> > </pre>
> >
> > (Note that the `--enablerepo=rawhide-modular` portion looks redundant,
> > but this is because of
> > [https://github.com/rpm-software-management/mock/issues/591 a mock
> > bug])
> >
> > == Contingency Plan ==
> > Contingency mechanism:
> >
> > Revert to Node.js 14.x as the default Node.js interpreter. This will
> > require bumping epoch.
> > Contingency deadline: Beta Freeze
> > Blocks release? No
> > Blocks product? No
> >
> > == Documentation ==
> > https://nodejs.org/dist/latest-v16.x/docs/api/
> > https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V16.md
> >
> > == Release Notes ==
> > Fedora 35 now ships with Node.js 16.x as the default Node.js
> > JavaScript server-side engine. If your applications are not yet ready
> > for this newer version, you can revert to the 14.x series by running
> > the following commands
> >
> > <pre>
> > dnf remove nodejs
> > dnf module reset nodejs
> > dnf module install nodejs:14
> > </pre>
> >
> > --
> > Ben Cotton
> > He / Him / His
> > Senior Program Manager, Fedora & CentOS Stream
> > Red Hat
> > TZ=America/Indiana/Indianapolis
> > _______________________________________________
> > devel mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
> > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: https://lists.fedoraproject.org/archives/list/[e-mail]
> > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure

[Stephen Gallagher]

On Thu, Jun 24, 2021 at 2:13 PM Stephen Gallagher  wrote:
> I'm a little behind on this, but I've created side-tag
> f35-build-side-42997 to perform any necessary nodejs-* rebuilds.
> Currently I'm only aware of the `nodejs` and `R-V8` packages needing
> to be rebuilt there. Most Node.js packages don't have a tight
> dependency on the interpreter. If you have a package that needs to be
> rebuilt against Node.js 16 (currently 16.4.0), please let me know
> immediately, as well as whether you want me to rebuild it for you or
> you will be doing it yourself in the side-tag.

This side-tag has now been merged and Node.js 16.x is in Rawhide.

[Miro Hrončok]

On 02. 07. 21 14:13, Stephen Gallagher wrote:
> On Thu, Jun 24, 2021 at 2:13 PM Stephen Gallagher  wrote:
> > I'm a little behind on this, but I've created side-tag
> > f35-build-side-42997 to perform any necessary nodejs-* rebuilds.
> > Currently I'm only aware of the `nodejs` and `R-V8` packages needing
> > to be rebuilt there. Most Node.js packages don't have a tight
> > dependency on the interpreter. If you have a package that needs to be
> > rebuilt against Node.js 16 (currently 16.4.0), please let me know
> > immediately, as well as whether you want me to rebuild it for you or
> > you will be doing it yourself in the side-tag.
>
> This side-tag has now been merged and Node.js 16.x is in Rawhide.

Is this relevant?

can't install R-V8:
   - nothing provides libnode.so.83()(64bit) needed by R-V8-3.4.2-1.fc35.x86_64

https://bugzilla.redhat.com/show_bug.cgi?id=1978630

[Stephen Gallagher]

Yes, it is. I'm working with Jeroen to resolve this.

On Fri, Jul 2, 2021 at 9:20 AM Miro Hrončok  wrote:
> On 02. 07. 21 14:13, Stephen Gallagher wrote:
> > On Thu, Jun 24, 2021 at 2:13 PM Stephen Gallagher  wrote:
> > > I'm a little behind on this, but I've created side-tag
> > > f35-build-side-42997 to perform any necessary nodejs-* rebuilds.
> > > Currently I'm only aware of the `nodejs` and `R-V8` packages needing
> > > to be rebuilt there. Most Node.js packages don't have a tight
> > > dependency on the interpreter. If you have a package that needs to be
> > > rebuilt against Node.js 16 (currently 16.4.0), please let me know
> > > immediately, as well as whether you want me to rebuild it for you or
> > > you will be doing it yourself in the side-tag.
> >
> > This side-tag has now been merged and Node.js 16.x is in Rawhide.
>
> Is this relevant?
>
> can't install R-V8:
> nothing provides libnode.so.83()(64bit) needed by R-V8-3.4.2-1.fc35.x86_64
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1978630
>
> --
> Miro Hrončok
> --
> Phone: [phone]
> IRC: mhroncok

[Stephen Gallagher]

This should now be fixed and in the next Rawhide compose.

On Fri, Jul 2, 2021 at 9:26 AM Stephen Gallagher  wrote:
> Yes, it is. I'm working with Jeroen to resolve this.
>
> On Fri, Jul 2, 2021 at 9:20 AM Miro Hrončok  wrote:
> > On 02. 07. 21 14:13, Stephen Gallagher wrote:
> > > On Thu, Jun 24, 2021 at 2:13 PM Stephen Gallagher  wrote:
> > > > I'm a little behind on this, but I've created side-tag
> > > > f35-build-side-42997 to perform any necessary nodejs-* rebuilds.
> > > > Currently I'm only aware of the `nodejs` and `R-V8` packages needing
> > > > to be rebuilt there. Most Node.js packages don't have a tight
> > > > dependency on the interpreter. If you have a package that needs to be
> > > > rebuilt against Node.js 16 (currently 16.4.0), please let me know
> > > > immediately, as well as whether you want me to rebuild it for you or
> > > > you will be doing it yourself in the side-tag.
> > >
> > > This side-tag has now been merged and Node.js 16.x is in Rawhide.
> >
> > Is this relevant?
> >
> > can't install R-V8:
> > nothing provides libnode.so.83()(64bit) needed by R-V8-3.4.2-1.fc35.x86_64
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=1978630
> >
> > --
> > Miro Hrončok
> > --
> > Phone: [phone]
> > IRC: mhroncok