Does anyone have any reason to delay a Weex release ? Any vital patches needs to be merged?
If not, I will start the release process tomorrow. Actually, after reading ASF’s release policy [1] and Apache Cordova release process [2], I found the following aspect of Weex release process needs improvement: Weex release process is not documented and it’s necessary to document it. Weex misses release script which would handle packing and publishing in several command line. Weex needs a webpage to list all the release version, release date, release source, binary artifact, changeLog, and available secondary distribution channel like Bintray or NPM. Weex needs a place that is only visible to PPMCs to store private key for NPM and Bintray distribution channel. I am volunteer to help with the missing part above and this release may take longer than before as we need to finish the missing part during the release process BTW: Though Apache Cordova release process is pretty complicated, I think Weex can learn a lot from it as these projects are very similar in release artifact and distribution channel. [1] http://www.apache.org/legal/release-policy.html <http://www.apache.org/legal/release-policy.html> [2] https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md <https://github.com/apache/cordova-coho/blob/master/docs/platforms-release-process.md> Best Regards, York Shen 申远
