Today, the Node.js upstream released 12.0.0, the next in its line of long-term support releases. I plan to make this the default version of Node.js in Fedora 31+, but not immediately. I'm currently working on getting a modular version of 12.x built for F29, F30 and Rawhide. I'll get that out to updates-testing this week. I'll send out an update once it's pushed to updates-testing.
Once that's available, I encourage all NPM packagers in Fedora to start testing their build and runtime with the 12.x module. I will be filing a Change Proposal and plan to switch the system interpreter for Rawhide over to 12.x around the end of May or beginning of June.
The exact timing may depend on the current status of the modules-in-the-non-modular-buildroot work in Fedora. If that's available by this time, I will retire the non-modular Node.js interpreter package and make the 12.x module the default stream for F31+. If it's not available, I'll continue to do what I've been doing in F29 and F30; building both the modular and non-modular packages.
If you discover that you own NPM packages that are critical and do not work with Node.js 12.x, please inform me immediately. We'll talk with upstream and see what we can do about it.
On Tue, Apr 23, 2019 at 5:40 PM Stephen Gallagher sgallagh@redhat.com wrote:
Today, the Node.js upstream released 12.0.0, the next in its line of long-term support releases. I plan to make this the default version of Node.js in Fedora 31+, but not immediately. I'm currently working on getting a modular version of 12.x built for F29, F30 and Rawhide. I'll get that out to updates-testing this week. I'll send out an update once it's pushed to updates-testing.
Once that's available, I encourage all NPM packagers in Fedora to start testing their build and runtime with the 12.x module. I will be filing a Change Proposal and plan to switch the system interpreter for Rawhide over to 12.x around the end of May or beginning of June.
The exact timing may depend on the current status of the modules-in-the-non-modular-buildroot work in Fedora. If that's available by this time, I will retire the non-modular Node.js interpreter package and make the 12.x module the default stream for F31+. If it's not available, I'll continue to do what I've been doing in F29 and F30; building both the modular and non-modular packages.
If you discover that you own NPM packages that are critical and do not work with Node.js 12.x, please inform me immediately. We'll talk with upstream and see what we can do about it.
I plan to make this switch on Friday, May 31st, so if you have packages that may break, now would be a good time to let me know.
Since the buildroot work isn't yet completely ready, I'm going to take the stop-gap approach and merge the '12' branch to master and do a non-modular build of Node.js 12.x in Rawhide on that day.
Dne 24. 05. 19 v 21:00 Stephen Gallagher napsal(a):
On Tue, Apr 23, 2019 at 5:40 PM Stephen Gallagher sgallagh@redhat.com wrote:
Today, the Node.js upstream released 12.0.0, the next in its line of long-term support releases. I plan to make this the default version of Node.js in Fedora 31+, but not immediately. I'm currently working on getting a modular version of 12.x built for F29, F30 and Rawhide. I'll get that out to updates-testing this week. I'll send out an update once it's pushed to updates-testing.
Once that's available, I encourage all NPM packagers in Fedora to start testing their build and runtime with the 12.x module. I will be filing a Change Proposal and plan to switch the system interpreter for Rawhide over to 12.x around the end of May or beginning of June.
The exact timing may depend on the current status of the modules-in-the-non-modular-buildroot work in Fedora. If that's available by this time, I will retire the non-modular Node.js interpreter package and make the 12.x module the default stream for F31+. If it's not available, I'll continue to do what I've been doing in F29 and F30; building both the modular and non-modular packages.
If you discover that you own NPM packages that are critical and do not work with Node.js 12.x, please inform me immediately. We'll talk with upstream and see what we can do about it.
I plan to make this switch on Friday, May 31st, so if you have packages that may break, now would be a good time to let me know.
Since the buildroot work isn't yet completely ready, I'm going to take the stop-gap approach and merge the '12' branch to master and do a non-modular build of Node.js 12.x in Rawhide on that day.
I might be missing something, but you promised "I will be filing a Change Proposal" in your original email above. Was it filled? Was it approved?
Vít
On Mon, May 27, 2019 at 6:59 AM Vít Ondruch vondruch@redhat.com wrote:
Dne 24. 05. 19 v 21:00 Stephen Gallagher napsal(a):
On Tue, Apr 23, 2019 at 5:40 PM Stephen Gallagher sgallagh@redhat.com wrote:
Today, the Node.js upstream released 12.0.0, the next in its line of long-term support releases. I plan to make this the default version of Node.js in Fedora 31+, but not immediately. I'm currently working on getting a modular version of 12.x built for F29, F30 and Rawhide. I'll get that out to updates-testing this week. I'll send out an update once it's pushed to updates-testing.
Once that's available, I encourage all NPM packagers in Fedora to start testing their build and runtime with the 12.x module. I will be filing a Change Proposal and plan to switch the system interpreter for Rawhide over to 12.x around the end of May or beginning of June.
The exact timing may depend on the current status of the modules-in-the-non-modular-buildroot work in Fedora. If that's available by this time, I will retire the non-modular Node.js interpreter package and make the 12.x module the default stream for F31+. If it's not available, I'll continue to do what I've been doing in F29 and F30; building both the modular and non-modular packages.
If you discover that you own NPM packages that are critical and do not work with Node.js 12.x, please inform me immediately. We'll talk with upstream and see what we can do about it.
I plan to make this switch on Friday, May 31st, so if you have packages that may break, now would be a good time to let me know.
Since the buildroot work isn't yet completely ready, I'm going to take the stop-gap approach and merge the '12' branch to master and do a non-modular build of Node.js 12.x in Rawhide on that day.
I might be missing something, but you promised "I will be filing a Change Proposal" in your original email above. Was it filled? Was it approved?
You are correct; I forgot to file the Change I promised. *sigh*
Filing it now and I will move out the cut-over date to June 14th to give enough time for it to be approved.
Dne 28. 05. 19 v 15:30 Stephen Gallagher napsal(a):
On Mon, May 27, 2019 at 6:59 AM Vít Ondruch vondruch@redhat.com wrote:
Dne 24. 05. 19 v 21:00 Stephen Gallagher napsal(a):
On Tue, Apr 23, 2019 at 5:40 PM Stephen Gallagher sgallagh@redhat.com wrote:
Today, the Node.js upstream released 12.0.0, the next in its line of long-term support releases. I plan to make this the default version of Node.js in Fedora 31+, but not immediately. I'm currently working on getting a modular version of 12.x built for F29, F30 and Rawhide. I'll get that out to updates-testing this week. I'll send out an update once it's pushed to updates-testing.
Once that's available, I encourage all NPM packagers in Fedora to start testing their build and runtime with the 12.x module. I will be filing a Change Proposal and plan to switch the system interpreter for Rawhide over to 12.x around the end of May or beginning of June.
The exact timing may depend on the current status of the modules-in-the-non-modular-buildroot work in Fedora. If that's available by this time, I will retire the non-modular Node.js interpreter package and make the 12.x module the default stream for F31+. If it's not available, I'll continue to do what I've been doing in F29 and F30; building both the modular and non-modular packages.
If you discover that you own NPM packages that are critical and do not work with Node.js 12.x, please inform me immediately. We'll talk with upstream and see what we can do about it.
I plan to make this switch on Friday, May 31st, so if you have packages that may break, now would be a good time to let me know.
Since the buildroot work isn't yet completely ready, I'm going to take the stop-gap approach and merge the '12' branch to master and do a non-modular build of Node.js 12.x in Rawhide on that day.
I might be missing something, but you promised "I will be filing a Change Proposal" in your original email above. Was it filled? Was it approved?
You are correct; I forgot to file the Change I promised. *sigh*
Filing it now and I will move out the cut-over date to June 14th to give enough time for it to be approved.
Thx 👍️
Vít
On Tue, May 28, 2019 at 9:30 AM Stephen Gallagher sgallagh@redhat.com wrote:
On Mon, May 27, 2019 at 6:59 AM Vít Ondruch vondruch@redhat.com wrote:
Dne 24. 05. 19 v 21:00 Stephen Gallagher napsal(a):
On Tue, Apr 23, 2019 at 5:40 PM Stephen Gallagher sgallagh@redhat.com wrote:
Today, the Node.js upstream released 12.0.0, the next in its line of long-term support releases. I plan to make this the default version of Node.js in Fedora 31+, but not immediately. I'm currently working on getting a modular version of 12.x built for F29, F30 and Rawhide. I'll get that out to updates-testing this week. I'll send out an update once it's pushed to updates-testing.
Once that's available, I encourage all NPM packagers in Fedora to start testing their build and runtime with the 12.x module. I will be filing a Change Proposal and plan to switch the system interpreter for Rawhide over to 12.x around the end of May or beginning of June.
The exact timing may depend on the current status of the modules-in-the-non-modular-buildroot work in Fedora. If that's available by this time, I will retire the non-modular Node.js interpreter package and make the 12.x module the default stream for F31+. If it's not available, I'll continue to do what I've been doing in F29 and F30; building both the modular and non-modular packages.
If you discover that you own NPM packages that are critical and do not work with Node.js 12.x, please inform me immediately. We'll talk with upstream and see what we can do about it.
I plan to make this switch on Friday, May 31st, so if you have packages that may break, now would be a good time to let me know.
Since the buildroot work isn't yet completely ready, I'm going to take the stop-gap approach and merge the '12' branch to master and do a non-modular build of Node.js 12.x in Rawhide on that day.
I might be missing something, but you promised "I will be filing a Change Proposal" in your original email above. Was it filled? Was it approved?
You are correct; I forgot to file the Change I promised. *sigh*
Filing it now and I will move out the cut-over date to June 14th to give enough time for it to be approved.
Just a reminder, I will cut Rawhide over to Node.js 12.x on Friday, June 14th. That's two days from now.
Node.js 12.4.0 is now in the Rawhide buildroot and will be in the repos tomorrow.
On Wed, Jun 12, 2019 at 4:35 PM Stephen Gallagher sgallagh@redhat.com wrote:
On Tue, May 28, 2019 at 9:30 AM Stephen Gallagher sgallagh@redhat.com wrote:
On Mon, May 27, 2019 at 6:59 AM Vít Ondruch vondruch@redhat.com wrote:
Dne 24. 05. 19 v 21:00 Stephen Gallagher napsal(a):
On Tue, Apr 23, 2019 at 5:40 PM Stephen Gallagher sgallagh@redhat.com wrote:
Today, the Node.js upstream released 12.0.0, the next in its line of long-term support releases. I plan to make this the default version of Node.js in Fedora 31+, but not immediately. I'm currently working on getting a modular version of 12.x built for F29, F30 and Rawhide. I'll get that out to updates-testing this week. I'll send out an update once it's pushed to updates-testing.
Once that's available, I encourage all NPM packagers in Fedora to start testing their build and runtime with the 12.x module. I will be filing a Change Proposal and plan to switch the system interpreter for Rawhide over to 12.x around the end of May or beginning of June.
The exact timing may depend on the current status of the modules-in-the-non-modular-buildroot work in Fedora. If that's available by this time, I will retire the non-modular Node.js interpreter package and make the 12.x module the default stream for F31+. If it's not available, I'll continue to do what I've been doing in F29 and F30; building both the modular and non-modular packages.
If you discover that you own NPM packages that are critical and do not work with Node.js 12.x, please inform me immediately. We'll talk with upstream and see what we can do about it.
I plan to make this switch on Friday, May 31st, so if you have packages that may break, now would be a good time to let me know.
Since the buildroot work isn't yet completely ready, I'm going to take the stop-gap approach and merge the '12' branch to master and do a non-modular build of Node.js 12.x in Rawhide on that day.
I might be missing something, but you promised "I will be filing a Change Proposal" in your original email above. Was it filled? Was it approved?
You are correct; I forgot to file the Change I promised. *sigh*
Filing it now and I will move out the cut-over date to June 14th to give enough time for it to be approved.
Just a reminder, I will cut Rawhide over to Node.js 12.x on Friday, June 14th. That's two days from now.