After #527, Node-ChakraCore is releasing nightlies when the v8.x or master branch changes. Adding to this, it would be useful to mark versions that are more adequate for public consumption, with less known issues.
We would like to move forward by making available release builds of Node-ChakraCore. This will use the same infrastructure and Jenkins job as the nightlies, but published in a different folder in the server, https://nodejs.org/download/chakracore-release/.
Here is the current plan to make this happen:
It is not yet time to mirror the full release process of Node-V8. For now, this will use automatic promotion for simplicity. This will be reevaluated in the future, it might be better to move to a closer integration with Node-V8 instead of a parallel release process. Also note that for now there are no MSI packages of Node-ChakraCore to avoid conflicts (users can use the zip/7z package or NVS).
I'm moving forward with this plan to unblock nodejs/node-chakracore#324 and related issues. This issue can be used to gather feedback and suggestions, I can revert my changes if there are objections.
cc @nodejs/build @nodejs/node-chakracore
After #527, Node-ChakraCore is releasing nightlies when the
v8.xormasterbranch changes. Adding to this, it would be useful to mark versions that are more adequate for public consumption, with less known issues.We would like to move forward by making available release builds of Node-ChakraCore. This will use the same infrastructure and Jenkins job as the nightlies, but published in a different folder in the server, https://nodejs.org/download/chakracore-release/.
Here is the current plan to make this happen:
node-chakracore(removing-nightlies)releasedisttype to the Jenkins jobwwwserver (similar to WWW changes for ChakraCore nightlies and releases #547, including automatic promotion)It is not yet time to mirror the full release process of Node-V8. For now, this will use automatic promotion for simplicity. This will be reevaluated in the future, it might be better to move to a closer integration with Node-V8 instead of a parallel release process. Also note that for now there are no MSI packages of Node-ChakraCore to avoid conflicts (users can use the zip/7z package or NVS).
I'm moving forward with this plan to unblock nodejs/node-chakracore#324 and related issues. This issue can be used to gather feedback and suggestions, I can revert my changes if there are objections.
cc @nodejs/build @nodejs/node-chakracore