> Is there a webpage for release note or change log except for the > RELEASENOTES.md in Cordova?
blog.cordova.io is a blog with posts about releases. > Or is it necessary to have that page? Not that I know of. > Does it comply the ASF’s policy if Weex continues to include npm/gradle > distribution channel in Github page > https://github.com/apache/incubator-weex#weex > <https://github.com/apache/incubator-weex#weex> ? I personally see no problem in linking do npm, gradle, or whatever _additional_ distribution methods a project uses for developer convenience. The idea behind the rules of Apache are that developers can understand what software they are actually downloading. If you make sure the Apache releases are equal to npm/gradle/whatever, that goal is reached and everything should be fine. -J Am Di., 23. Apr. 2019 um 13:38 Uhr schrieb York Shen <shenyua...@gmail.com>: > > Found it. Thanks. > > Is there a webpage for release note or change log except for the > RELEASENOTES.md in Cordova? Or is it necessary to have that page? > > Does it comply the ASF’s policy if Weex continues to include npm/gradle > distribution channel in Github page > https://github.com/apache/incubator-weex#weex > <https://github.com/apache/incubator-weex#weex> ? > > Best Regards, > York Shen > > 申远 > > > 在 2019年4月23日，19:21，Jan Piotrowski <piotrow...@gmail.com> 写道： > > > > I would guess the .tgz includes the RELEASENOTES.md that is also in > > the source code repository. > > > > As I wrote before, I am at least not aware of any complaints about how > > Cordova does things from Apache. > > > > -J > > > > Am Di., 23. Apr. 2019 um 13:12 Uhr schrieb York Shen <shenyua...@gmail.com>: > >> > >> Actually, I’d like to adopt Cordova’s distribution mechanism and > >> corresponding webpages if it complies ASF policy. > >> > >> As far as I understand, Weex is very similar to Cordova. Main users of > >> both are front-end engineers, who would prefer npm or gradle as > >> distribution mechanism. > >> > >> But is there ChangeLog/ReleaseNote pages for Cordova’s Source Distribution? > >> > >> Best Regards, > >> York Shen > >> > >> 申远 > >> > >>> 在 2019年4月23日，18:00，Jan Piotrowski <piotrow...@gmail.com> 写道： > >>> > >>> What part of the release policy are you specifically referring to? > >>> > >>> The main distribution mechanism for Apache Cordova is npm, which > >>> command is mentioned in the "Get started" [1] part of the homepage and > >>> installations instructions [2] of the documentation. Using the source > >>> code is just a fallback, which the "Source Distribution" link probably > >>> takes care of. I am not aware of any complaints from Apache regarding > >>> this to Apache Cordova. The main usage type for users is front and > >>> center, the source code still is available if needed - so I wouldn't > >>> know why this should not be fine. > >>> > >>> -J > >>> > >>> [1] https://cordova.apache.org/#getstarted > >>> [2] https://cordova.apache.org/docs/en/latest/guide/cli/index.html > >>> > >>> Am Di., 23. Apr. 2019 um 11:50 Uhr schrieb 申远 <shenyua...@gmail.com>: > >>>> > >>>> Hi, developers > >>>> > >>>> After digging into ASF policy [1], it is clear that Weex missing a > >>>> download > >>>> page which should links to Weex Apache Release. But is there any > >>>> requirement of the format for the download page? > >>>> > >>>> For example, I found RocketMQ has a specified designed download page [2], > >>>> while Cordova [3] only has a text area called "source distribution" which > >>>> will be redirected to ASF page [4] . > >>>> > >>>> Are both the download pages valid according to ASFs' policy? No offense, > >>>> but it occured to me that Cordova may probably choose a lazy way. > >>>> > >>>> [1] https://www.apache.org/legal/release-policy.html > >>>> [2] https://rocketmq.apache.org/dowloading/releases/ > >>>> [3] https://cordova.apache.org/ > >>>> [4] https://www.apache.org/dyn/closer.cgi/cordova > >>>> > >>>> Best Regards, > >>>> YorkShen > >>>> > >>>> 申远 > >> >
