I stand to what I have said on the mailing list: > I think we just have to start the process. We have to do the releases in > order anyway and there is the [buy-in phase][1] for each release, so any > blockers will surface when it's the turn of the respective repo. The first > release that would have to be done is `cordova-common`.
That being said, I have no capacities to do any release management myself right now. Things that should be resolved before the respective major release: - For platforms: https://github.com/apache/cordova/issues/32 - https://github.com/apache/cordova-fetch/pull/44 (basically finished; would appreciate another review) - https://github.com/apache/cordova-fetch/issues/47 (would like some opinions before we release the new major) Regarding committing `package-lock.json`: Since there was little feedback after the latest concerns I would still assume consensus for the original plan. However, we might as well postpone this task to any following release, since the presence of `package-lock.json` [affects development only](https://lists.apache.org/thread.html/c06d35b6944fb44a04449a7baf10797f8ae11cbcfddb3e90851dc0b9@%3Cdev.cordova.apache.org%3E) anyway. [1]: https://github.com/apache/cordova-coho/blob/master/docs/tools-release-process.md#get-buy-in [ Full content available at: https://github.com/apache/cordova/issues/10 ] This message was relayed via gitbox.apache.org for [email protected]
