As the release procedure is not documented and corresponding script is out of date, the release would be delayed about one weeks or more.
Thanks for your interest. Best Regards, York Shen 申远 > 在 2019年4月25日，11:53，申远 <[email protected]> 写道： > > Just created a Github Project[1] for this release. All the document and > scripts we need to write is in the page. > > [1] https://github.com/apache/incubator-weex/projects/5 > <https://github.com/apache/incubator-weex/projects/5> > > Best Regards, > YorkShen > > 申远 > > > 申远 <[email protected] <mailto:[email protected]>> 于2019年4月25日周四 > 上午11:06写道： > Apache Cordova is using a private SVN hosted by Apache for that and > similar use cases. > Any document about how private Apache SNV works? > > The Apache Cordova release process is also >5 years old > Actually, I personally think Apache Cordova release process shows us what a > Apache release procedure look likes (thanks for your contribution). But as > you said, it's over complicated, I'd like to the unnecessary procedure(maybe > 50%), and remains the things that still make sense. > > Best Regards, > YorkShen > > 申远 > > > Jan Piotrowski <[email protected] <mailto:[email protected]>> > 于2019年4月24日周三 下午6:11写道： > > Weex needs a place that is only visible to PPMCs to store private key for > > NPM and Bintray distribution channel. > > Apache Cordova is using a private SVN hosted by Apache for that and > similar use cases. > > > 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. > > The Apache Cordova release process is also >5 years old, pretty over > complex and currently not very well documented. You should _not_ take > this as a positive example at all. You should probably just forget > that it exists (besides the individual things being done, those > probably still make sense for Weex). > > -J > > Am Mi., 24. Apr. 2019 um 09:44 Uhr schrieb York Shen <[email protected] > <mailto:[email protected]>>: > > > > 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> > > <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> > > > > <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 > > > > 申远 > >
