354
Comment:
|
1088
|
Deletions are marked like this. | Additions are marked like this. |
Line 9: | Line 9: |
Whenever updating a new major version of any node module or JavaScript library, please follow these steps. Like a regular [[Transition]] but without binNMU or back from release team. 1. Upload the new major release to experimental 2. Run autopkgtest of reverse dependencies and rebuild all reverse build dependencies. Use tools like https://salsa.debian.org/ruby-team/meta build script. 3. If a reverse dependency does not have tests enabled, then use the upstream testsuite with package.json updated 4. Report bugs against all failing packages. Give reasonable time to fix things (2 week to a month at least). 5. Fix packages in unstable or in experimental. 6. Upload to unstable when important breakages are fixed. |
Javascript/Nodejs/Node12 - READY.
- Acorn 6 - DONE.
/Rollup1 - READY.
?/Webpack4 - READY to go with webassemblyjs.
/Babel7 - STALLED need to build with babel 6 or embed babel 7
- webassemblyjs - READY to go with nodejs 12 for Array.prototype.flatMap
webpack 4.30 and nodejs 12 will need to go to unstable together.
Whenever updating a new major version of any node module or ?JavaScript library, please follow these steps. Like a regular ?Transition but without binNMU or back from release team.
- Upload the new major release to experimental
Run autopkgtest of reverse dependencies and rebuild all reverse build dependencies. Use tools like https://salsa.debian.org/ruby-team/meta build script.
- If a reverse dependency does not have tests enabled, then use the upstream testsuite with package.json updated
- Report bugs against all failing packages. Give reasonable time to fix things (2 week to a month at least).
- Fix packages in unstable or in experimental.
- Upload to unstable when important breakages are fixed.