[RESULT][VOTE]: Apache Weex-incubating Release 0.12.0-RC5
Hi IMPC, With 3 +1 and no -1, the vote has passed. Thanks to Raphael Bircher, John D. Ament and Josh Elser. It's our very first release which is meaning a lot to us. Thanks to people in previous vote thread too. -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io>
Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC5
Thanks for reviewing. I'll look into the things you mentioned. Josh Elser <els...@apache.org>于2017年6月7日 周三下午11:24写道： > +1 (binding) > > * Make sure https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS > exists at https://dist.apache.org/repos/dist/release/incubator/weex/KEYS. > * Would recommend sha512 instead of sha1 for the future. > * Ran into an issue with node-7.7.4, upgrade to 8 seems to have gotten > past that. > * After that, I'm running into an issue with the build failing due to a > missing ".wwprc" file. Not sure what to do with that.. Looks like your > build instructions/script could use a refresh :) > * L look ok at a glance. xsums/sigs are good. > > On 6/5/17 5:27 AM, sospartan wrote: > > Hi all, > > > > I'm calling a vote for Weex-incubating 0.12.0-RC5 release. > > The changes fix problems pointed out by John D. Ament and Justin Mclean > in > > RC4 voting thread[1]. > > Thanks to these guys. And thanks to people who vote +1 too. Hope this RC > > would finally passed. > > > > The PPMC vote for this release has passed: > > * > https://lists.apache.org/thread.html/866a707deea418ff5374d38783f5591d0cda6fa09515766fec101d3e@%3Cdev.weex.apache.org%3E > > < > https://lists.apache.org/thread.html/866a707deea418ff5374d38783f5591d0cda6fa09515766fec101d3e@%3Cdev.weex.apache.org%3E > >* > > > > The tag to be voted upon: > > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git > > ;a=shortlog;h=refs/tags/0.12.0-rc5 > > > > The commit hash: > > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h= > > dcf9a83360b4403ffbdbfb3e168a68d1ff7a2b38 > > > > The source tarball can be found at: > > > https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0-incubating/RC5/ > > > > The fingerprint of key to sign release artifacts: > > 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784 > > > > Release artifacts are signed with the following key: > > https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS > > > > Release note about this version: > > https://issues.apache.org/jira/browse/WEEX-26 > > > > This vote will remain open for at least 72 hours. > > Please vote on releasing this RC. > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > > > 1. > > > https://lists.apache.org/thread.html/9e9308203feb3e9651644e7bef6578a50cf21a4a0513bd6175e1fb53@%3Cgeneral.incubator.apache.org%3E > > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
[VOTE]: Apache Weex-incubating Release 0.12.0-RC5
Hi all, I'm calling a vote for Weex-incubating 0.12.0-RC5 release. The changes fix problems pointed out by John D. Ament and Justin Mclean in RC4 voting thread[1]. Thanks to these guys. And thanks to people who vote +1 too. Hope this RC would finally passed. The PPMC vote for this release has passed: *https://lists.apache.org/thread.html/866a707deea418ff5374d38783f5591d0cda6fa09515766fec101d3e@%3Cdev.weex.apache.org%3E <https://lists.apache.org/thread.html/866a707deea418ff5374d38783f5591d0cda6fa09515766fec101d3e@%3Cdev.weex.apache.org%3E>* The tag to be voted upon: https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git ;a=shortlog;h=refs/tags/0.12.0-rc5 The commit hash: https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h= dcf9a83360b4403ffbdbfb3e168a68d1ff7a2b38 The source tarball can be found at: https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0-incubating/RC5/ The fingerprint of key to sign release artifacts: 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784 Release artifacts are signed with the following key: https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS Release note about this version: https://issues.apache.org/jira/browse/WEEX-26 This vote will remain open for at least 72 hours. Please vote on releasing this RC. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) 1. https://lists.apache.org/thread.html/9e9308203feb3e9651644e7bef6578a50cf21a4a0513bd6175e1fb53@%3Cgeneral.incubator.apache.org%3E -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io>
[VOTE][CANCEL]: Apache Weex-incubating Release 0.12.0-RC4
HI, We'll cancel this vote and start a new RC later. -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io>
Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC4
Okay, I see. Thank you for point it out. Lesson learned. On Fri, Jun 2, 2017 at 11:58 AM, Justin Mclean <jus...@classsoftware.com> wrote: > Hi, > > > All issues is fixed except this one: > >> LICENSE contains incorrect boilerplate text (copyright line) > > This line: > Copyright 2017 The Apache Software Foundation > > Should be: > Copyright [] [name of copyright owner] > > As it’s instructions for 3rd parties in how they can apply the Apache > license to their code. See [1]. > > Thanks, > Justin > > 1. https://www.apache.org/licenses/LICENSE-2.0.txt > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC4
Hi all, All issues is fixed except this one: > LICENSE contains incorrect boilerplate text (copyright line) See file here https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=blob;f=LICENSE;h=ca146a698f3b3950ed7b36aae8c90bf1bd76b91d;hb=refs/heads/dev I don't understand this issue. What is 'incorrect boilerplate text'? Raphael, please help me on this one. On Thu, Jun 1, 2017 at 12:53 PM, Raphael Bircher <rbircherapa...@gmail.com> wrote: > Hi all, > > Am .06.2017, 02:59 Uhr, schrieb Justin Mclean <jus...@classsoftware.com>: > > Hi, >> >> Thanks for the feedback. I hope sospartan or someone else will soon show >>> up. I think we should go for an RC5. There are simply too many issues. >>> >> >> >> All issues I mentioned are minor and can be fixed in a next release, but >> the binary in source code is IMO a blocker. >> >> Other people may have differing options and I think you may actually have >> enough votes to make a release if you wanted to. You only need 3 +1 votes >> and more +1 than -1 ones. That being said the RM may decide that the issue >> is serious enough to make another release candidate. >> > Just talked about it on the Mailing List. Weex will go for a RC5. > > Regards, Raphael > > > -- > My introduction https://youtu.be/Ln4vly5sxYU > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC4
Thanks for the review. We are working on these issue now. And another RC will make. On Thu, Jun 1, 2017 at 8:59 AM, Justin Mclean <jus...@classsoftware.com> wrote: > Hi, > > > Thanks for the feedback. I hope sospartan or someone else will soon show > up. I think we should go for an RC5. There are simply too many issues. > > > All issues I mentioned are minor and can be fixed in a next release, but > the binary in source code is IMO a blocker. > > Other people may have differing options and I think you may actually have > enough votes to make a release if you wanted to. You only need 3 +1 votes > and more +1 than -1 ones. That being said the RM may decide that the issue > is serious enough to make another release candidate. > > Thanks, > Justin > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC4
Is this release have enough +1 bindings now? I count rapheal, craig and john ~~ that's 3 of them. I shall prepare some fireworks for this. On Thu, May 25, 2017 at 8:27 AM, Raphael Bircher <rbircherapa...@gmail.com> wrote: > I give my +1 (binding) too > > > Am .05.2017, 12:02 Uhr, schrieb sospartan <sospar...@gmail.com>: > > Hi guys, >> >> I'm calling a vote for Weex-incubating 0.12.0-RC4 release. >> The issues pointed out by Craig in previous vote were ALL FIXED. >> A build README(README_RELEASE.md) is in the tarball now. >> >> Thanks for peoples who were taking time to review our last RC (RC3). I'm >> Hoping >> this RC is doing better. >> >> The PPMC vote for this release has passed: >> https://lists.apache.org/thread.html/0e05de680b315e453f >> e8643ff297d5ebfb9cdd30ea2c982e33854ff5@%3Cdev.weex.apache.org%3E >> >> The tag to be voted upon: >> https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git >> ;a=shortlog;h=refs/tags/0.12.0-rc4 >> >> The commit hash: >> https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git >> ;a=commit;h=e19ef8a4acc39cd8db2cf3be4f8369f6d7a0bb43 >> >> The source tarball can be found at: >> https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0 >> -incubating/RC4/ >> >> The fingerprint of key to sign release artifacts: >> 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784 >> >> Release artifacts are signed with the following key: >> https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS >> >> Release note about this version: >> https://issues.apache.org/jira/browse/WEEX-26 >> >> This vote will remain open for at least 72 hours. >> Please vote on releasing this RC. >> >> [ ] +1 approve >> [ ] +0 no opinion >> [ ] -1 disapprove (and reason why) >> >> > > -- > My introduction https://youtu.be/Ln4vly5sxYU > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC4
I just re-post the vote thread, not a new RC. I think people come to apachecon may not see this thread. On Tue, May 23, 2017 at 6:17 PM, John D. Ament <johndam...@apache.org> wrote: > I'll be honest, I don't understand why you created a new RC for the vote. > Usually we only re-roll a release if someone notes a blocking issue. I > don't see any blocking issues listed in the prior candidate, however you > are struggling to get that third vote. > > Its also good form to send a [CANCEL] email for the prior vote so people > don't get lost. > > John > > On Tue, May 23, 2017 at 6:03 AM sospartan <sospar...@gmail.com> wrote: > > > Hi guys, > > > > I'm calling a vote for Weex-incubating 0.12.0-RC4 release. > > The issues pointed out by Craig in previous vote were ALL FIXED. > > A build README(README_RELEASE.md) is in the tarball now. > > > > Thanks for peoples who were taking time to review our last RC (RC3). I'm > > Hoping > > this RC is doing better. > > > > The PPMC vote for this release has passed: > > https://lists.apache.org/thread.html/0e05de680b315e453f > > e8643ff297d5ebfb9cdd30ea2c982e33854ff5@%3Cdev.weex.apache.org%3E > > > > The tag to be voted upon: > > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git > > ;a=shortlog;h=refs/tags/0.12.0-rc4 > > > > The commit hash: > > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git > > ;a=commit;h=e19ef8a4acc39cd8db2cf3be4f8369f6d7a0bb43 > > > > The source tarball can be found at: > > > > https://dist.apache.org/repos/dist/dev/incubator/weex/0.12. > 0-incubating/RC4/ > > > > The fingerprint of key to sign release artifacts: > > 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784 > > > > Release artifacts are signed with the following key: > > https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS > > > > Release note about this version: > > https://issues.apache.org/jira/browse/WEEX-26 > > > > This vote will remain open for at least 72 hours. > > Please vote on releasing this RC. > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > -- > > Best Regards! > > > > sospartan > > http://weex.apache.org/ <https://weex-project.io/> > > > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
[VOTE]: Apache Weex-incubating Release 0.12.0-RC4
Hi guys, I'm calling a vote for Weex-incubating 0.12.0-RC4 release. The issues pointed out by Craig in previous vote were ALL FIXED. A build README(README_RELEASE.md) is in the tarball now. Thanks for peoples who were taking time to review our last RC (RC3). I'm Hoping this RC is doing better. The PPMC vote for this release has passed: https://lists.apache.org/thread.html/0e05de680b315e453f e8643ff297d5ebfb9cdd30ea2c982e33854ff5@%3Cdev.weex.apache.org%3E The tag to be voted upon: https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git ;a=shortlog;h=refs/tags/0.12.0-rc4 The commit hash: https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git ;a=commit;h=e19ef8a4acc39cd8db2cf3be4f8369f6d7a0bb43 The source tarball can be found at: https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0-incubating/RC4/ The fingerprint of key to sign release artifacts: 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784 Release artifacts are signed with the following key: https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS Release note about this version: https://issues.apache.org/jira/browse/WEEX-26 This vote will remain open for at least 72 hours. Please vote on releasing this RC. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC4
John and Craig, Take a look at this issue https://issues.apache.org/jira/browse/WEEX-36 As I said in previous mail, all problems are fixed. Hope it's help. On Mon, May 22, 2017 at 11:34 AM, John D. Ament <johndam...@apache.org> wrote: > sospartan, > > One thing that may help other IPMC members is to go through the list of > what Craig sent out, and for the items fixed indicate they were fixed, > likewise for the items that were not fixed but deferred call out the JIRAs > that will fix them for subsequent releases. > > John > > On Sun, May 21, 2017 at 11:26 PM sospartan <sospar...@gmail.com> wrote: > > > Anybody wanna have a look at this release? > > I've fixed all problems block release in previous RCs. > > > > On Thu, May 18, 2017 at 6:10 PM, Raphael Bircher < > rbircherapa...@gmail.com > > > > > wrote: > > > > > +1 (binding) > > > > > > > > > Am .05.2017, 11:23 Uhr, schrieb sospartan <sospar...@apache.org>: > > > > > > Hi IPMC, > > >> > > >> I'm calling a vote for Weex-incubating 0.12.0-RC4 release. > > >> In this release, source tarball only include files necessary to build > > Weex > > >> SDK. > > >> All binaries were excluded. > > >> A build README(README_RELEASE.md) is in the tarball now. > > >> > > >> Thanks for peoples who were taking time to review our last RC (RC3). > I'm > > >> Hoping > > >> this RC is doing better. > > >> > > >> The PPMC vote for this release has passed: > > >> https://lists.apache.org/thread.html/0e05de680b315e453fe8643ff297d5 > > >> ebfb9cdd30ea2c982e33854ff5@%3Cdev.weex.apache.org%3E > > >> > > >> The tag to be voted upon: > > >> https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git > > >> ;a=shortlog;h=refs/tags/0.12.0-rc4 > > >> > > >> The commit hash: > > >> > > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h= > > >> e19ef8a4acc39cd8db2cf3be4f8369f6d7a0bb43 > > >> > > >> The source tarball can be found at: > > >> https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0 > > >> -incubating/RC4/ > > >> > > >> The fingerprint of key to sign release artifacts: > > >> 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784 > > >> > > >> Release artifacts are signed with the following key: > > >> https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS > > >> > > >> Release note about this version: > > >> https://issues.apache.org/jira/browse/WEEX-26 > > >> > > >> This vote will remain open for at least 72 hours. > > >> Please vote on releasing this RC. > > >> > > >> [ ] +1 approve > > >> [ ] +0 no opinion > > >> [ ] -1 disapprove (and reason why) > > >> > > >> > > > > > > -- > > > My introduction https://youtu.be/Ln4vly5sxYU > > > > > > - > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > > > -- > > Best Regards! > > > > sospartan > > http://weex.apache.org/ <https://weex-project.io/> > > > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC4
Anybody wanna have a look at this release? I've fixed all problems block release in previous RCs. On Thu, May 18, 2017 at 6:10 PM, Raphael Bircher <rbircherapa...@gmail.com> wrote: > +1 (binding) > > > Am .05.2017, 11:23 Uhr, schrieb sospartan <sospar...@apache.org>: > > Hi IPMC, >> >> I'm calling a vote for Weex-incubating 0.12.0-RC4 release. >> In this release, source tarball only include files necessary to build Weex >> SDK. >> All binaries were excluded. >> A build README(README_RELEASE.md) is in the tarball now. >> >> Thanks for peoples who were taking time to review our last RC (RC3). I'm >> Hoping >> this RC is doing better. >> >> The PPMC vote for this release has passed: >> https://lists.apache.org/thread.html/0e05de680b315e453fe8643ff297d5 >> ebfb9cdd30ea2c982e33854ff5@%3Cdev.weex.apache.org%3E >> >> The tag to be voted upon: >> https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git >> ;a=shortlog;h=refs/tags/0.12.0-rc4 >> >> The commit hash: >> https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h= >> e19ef8a4acc39cd8db2cf3be4f8369f6d7a0bb43 >> >> The source tarball can be found at: >> https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0 >> -incubating/RC4/ >> >> The fingerprint of key to sign release artifacts: >> 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784 >> >> Release artifacts are signed with the following key: >> https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS >> >> Release note about this version: >> https://issues.apache.org/jira/browse/WEEX-26 >> >> This vote will remain open for at least 72 hours. >> Please vote on releasing this RC. >> >> [ ] +1 approve >> [ ] +0 no opinion >> [ ] -1 disapprove (and reason why) >> >> > > -- > My introduction https://youtu.be/Ln4vly5sxYU > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
Re: [DISCUSS][VOTE]: Apache Weex-incubating Release 0.12.0-RC4
Raphael, This tarball(https://dist.apache.org/repos/dist/dev/incubator/weex/weex-j ars.tar.gz) is not used. I have exclude playground app and use installed gradle to setup android project. So these file is not needed. On Thu, May 18, 2017 at 5:23 PM, Raphael Bircher <rbircherapa...@gmail.com> wrote: > Hi John > > Am .05.2017, 17:40 Uhr, schrieb John D. Ament <johndam...@apache.org>: > > sospartan, >> >> Couple of things noticed: >> >> - Your email still points to your non-ASF hosted website. Don't forget to >> point to your ASF website. >> - The source release still contains a sub-directory. >> - Its still not clear to me how to create the binary. >> - Your package.json points still to old alibaba repos and not ASF repos >> >> I would like to see these 4 issues fixed for next release. >> >> LICENSE file looks good, minor typos (still need to fix the extra >> comments) >> NOTICE file looks fine >> DISCLAIMER is present. >> No binaries that I can find. >> > > Well, they are not directly in the release, but they are on the ASF > Infrastructure. https://dist.apache.org/repos/ > dist/dev/incubator/weex/weex-jars.tar.gz > I don't know, if this is fine. > > Regards, Raphael > > >> +1 >> >> John >> >> On Mon, May 15, 2017 at 5:24 AM sospartan <sospar...@apache.org> wrote: >> >> Hi IPMC, >>> >>> I'm calling a vote for Weex-incubating 0.12.0-RC4 release. >>> In this release, source tarball only include files necessary to build >>> Weex >>> SDK. >>> All binaries were excluded. >>> A build README(README_RELEASE.md) is in the tarball now. >>> >>> Thanks for peoples who were taking time to review our last RC (RC3). I'm >>> Hoping >>> this RC is doing better. >>> >>> The PPMC vote for this release has passed: >>> https://lists.apache.org/thread.html/0e05de680b315e453fe8643ff297d5 >>> ebfb9cdd30ea2c982e33854ff5@%3Cdev.weex.apache.org%3E >>> >>> The tag to be voted upon: >>> https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git >>> ;a=shortlog;h=refs/tags/0.12.0-rc4 >>> >>> The commit hash: >>> https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h= >>> e19ef8a4acc39cd8db2cf3be4f8369f6d7a0bb43 >>> <https://git-wip-us.apache.org/repos/asf?p=incubator-weex. >>> git;a=commit;h=e19ef8a4acc39cd8db2cf3be4f8369f6d7a0bb43> >>> >>> The source tarball can be found at: >>> >>> https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0 >>> -incubating/RC4/ >>> >>> The fingerprint of key to sign release artifacts: >>> 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784 >>> >>> Release artifacts are signed with the following key: >>> https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS >>> >>> Release note about this version: >>> https://issues.apache.org/jira/browse/WEEX-26 >>> >>> This vote will remain open for at least 72 hours. >>> Please vote on releasing this RC. >>> >>> [ ] +1 approve >>> [ ] +0 no opinion >>> [ ] -1 disapprove (and reason why) >>> >>> -- >>> Best Regards! >>> -- >>> >>> sospartan >>> https://weex-project.io >>> >>> > > -- > My introduction https://youtu.be/Ln4vly5sxYU > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- Best Regards! sospartan http://weex.apache.org/ <https://weex-project.io/>
Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC4
ok, I'll update my release script to bring every source code under root directory. Thanks for this tip. On Thu, May 18, 2017 at 11:03 AM, John D. Ament <johndam...@apache.org> wrote: > On Wed, May 17, 2017 at 7:57 PM sospartan <sospar...@gmail.com> wrote: > > > John, > > Thanks for the review. > > I don't understand the issue with "sub-directory". Is there any standard > > directory structure for source release? > > > > > Typically the release contents are simply in the root directory. There > should not be a subdirectory where all the contents exist. > > > > > > John D. Ament <johndam...@apache.org>于2017年5月17日 周三下午11:41写道： > > > > > sospartan, > > > > > > Couple of things noticed: > > > > > > - Your email still points to your non-ASF hosted website. Don't forget > > to > > > point to your ASF website. > > > - The source release still contains a sub-directory. > > > - Its still not clear to me how to create the binary. > > > - Your package.json points still to old alibaba repos and not ASF repos > > > > > > I would like to see these 4 issues fixed for next release. > > > > > > LICENSE file looks good, minor typos (still need to fix the extra > > comments) > > > NOTICE file looks fine > > > DISCLAIMER is present. > > > No binaries that I can find. > > > > > > +1 > > > > > > John > > > > > > On Mon, May 15, 2017 at 5:24 AM sospartan <sospar...@apache.org> > wrote: > > > > > > > Hi IPMC, > > > > > > > > I'm calling a vote for Weex-incubating 0.12.0-RC4 release. > > > > In this release, source tarball only include files necessary to build > > > Weex > > > > SDK. > > > > All binaries were excluded. > > > > A build README(README_RELEASE.md) is in the tarball now. > > > > > > > > Thanks for peoples who were taking time to review our last RC (RC3). > > I'm > > > > Hoping > > > > this RC is doing better. > > > > > > > > The PPMC vote for this release has passed: > > > > https://lists.apache.org/thread.html/0e05de680b315e453fe8643ff297d5 > > > > ebfb9cdd30ea2c982e33854ff5@%3Cdev.weex.apache.org%3E > > > > > > > > The tag to be voted upon: > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git > > > > ;a=shortlog;h=refs/tags/0.12.0-rc4 > > > > > > > > The commit hash: > > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h= > > > > e19ef8a4acc39cd8db2cf3be4f8369f6d7a0bb43 > > > > < > > > > > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h= > e19ef8a4acc39cd8db2cf3be4f8369f6d7a0bb43 > > > > > > > > > > > > The source tarball can be found at: > > > > > > > > > > > > > https://dist.apache.org/repos/dist/dev/incubator/weex/0.12. > 0-incubating/RC4/ > > > > > > > > The fingerprint of key to sign release artifacts: > > > > 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784 > > > > > > > > Release artifacts are signed with the following key: > > > > https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS > > > > > > > > Release note about this version: > > > > https://issues.apache.org/jira/browse/WEEX-26 > > > > > > > > This vote will remain open for at least 72 hours. > > > > Please vote on releasing this RC. > > > > > > > > [ ] +1 approve > > > > [ ] +0 no opinion > > > > [ ] -1 disapprove (and reason why) > > > > > > > > -- > > > > Best Regards! > > > > -- > > > > > > > > sospartan > > > > https://weex-project.io > > > > > > > > > -- > > sospartan > > Phone:13588488290 > > HangZhou > > > -- sospartan Phone:13588488290 HangZhou
Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC4
John, Thanks for the review. I don't understand the issue with "sub-directory". Is there any standard directory structure for source release? John D. Ament <johndam...@apache.org>于2017年5月17日 周三下午11:41写道： > sospartan, > > Couple of things noticed: > > - Your email still points to your non-ASF hosted website. Don't forget to > point to your ASF website. > - The source release still contains a sub-directory. > - Its still not clear to me how to create the binary. > - Your package.json points still to old alibaba repos and not ASF repos > > I would like to see these 4 issues fixed for next release. > > LICENSE file looks good, minor typos (still need to fix the extra comments) > NOTICE file looks fine > DISCLAIMER is present. > No binaries that I can find. > > +1 > > John > > On Mon, May 15, 2017 at 5:24 AM sospartan <sospar...@apache.org> wrote: > > > Hi IPMC, > > > > I'm calling a vote for Weex-incubating 0.12.0-RC4 release. > > In this release, source tarball only include files necessary to build > Weex > > SDK. > > All binaries were excluded. > > A build README(README_RELEASE.md) is in the tarball now. > > > > Thanks for peoples who were taking time to review our last RC (RC3). I'm > > Hoping > > this RC is doing better. > > > > The PPMC vote for this release has passed: > > https://lists.apache.org/thread.html/0e05de680b315e453fe8643ff297d5 > > ebfb9cdd30ea2c982e33854ff5@%3Cdev.weex.apache.org%3E > > > > The tag to be voted upon: > > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git > > ;a=shortlog;h=refs/tags/0.12.0-rc4 > > > > The commit hash: > > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h= > > e19ef8a4acc39cd8db2cf3be4f8369f6d7a0bb43 > > < > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h=e19ef8a4acc39cd8db2cf3be4f8369f6d7a0bb43 > > > > > > The source tarball can be found at: > > > > > https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0-incubating/RC4/ > > > > The fingerprint of key to sign release artifacts: > > 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784 > > > > Release artifacts are signed with the following key: > > https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS > > > > Release note about this version: > > https://issues.apache.org/jira/browse/WEEX-26 > > > > This vote will remain open for at least 72 hours. > > Please vote on releasing this RC. > > > > [ ] +1 approve > > [ ] +0 no opinion > > [ ] -1 disapprove (and reason why) > > > > -- > > Best Regards! > > -- > > > > sospartan > > https://weex-project.io > > > -- sospartan Phone:13588488290 HangZhou
Re: Looking for additional mentors for weex-incubating
I'm very grateful to you for this. I've make some changes to the source release and start new RC vote in another thread: https://lists.apache.org/thread.html/9e9308203feb3e9651644e7bef6578a50cf21a4a0513bd6175e1fb53@%3Cgeneral.incubator.apache.org%3E I believe we can finally get there. Thank you. On Wed, May 17, 2017 at 5:44 PM, Raphael Bircher <rbircherapa...@gmail.com> wrote: > Hi sospartan > > Yea, I see, there are several issues. I will not act as an official > mentor, but I subscribed the dev list, and we'll see what we can do. > > Regards Raphael > > Am .05.2017, 11:24 Uhr, schrieb sospartan <sospar...@apache.org>: > > Weex has been incubating since 2016-11-30. Now we are working forward to >> our first >> apache release. Because our 4 mentors are mostly absent. Now we are >> looking >> for >> additional mentors to join us. >> >> Anybody from IPMC interesting in weex is welcomed. Most (probably all) of >> our >> committers and contributors are new to ASF, we are still try to learn the >> apache-way. >> Especially, there are lots issues about our release according last RC >> vote. >> We need >> mentors to guide the community. >> >> > > -- > My introduction https://youtu.be/Ln4vly5sxYU > > ----- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- sospartan Phone:13588488290 HangZhou
Looking for additional mentors for weex-incubating
Weex has been incubating since 2016-11-30. Now we are working forward to our first apache release. Because our 4 mentors are mostly absent. Now we are looking for additional mentors to join us. Anybody from IPMC interesting in weex is welcomed. Most (probably all) of our committers and contributors are new to ASF, we are still try to learn the apache-way. Especially, there are lots issues about our release according last RC vote. We need mentors to guide the community. -- Best Regards! -- sospartan Weex is a framework for building Mobile cross-platform high performance UI.
Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC4
Could anyone from IPMC review this release? On Mon, May 15, 2017 at 5:23 PM, sospartan <sospar...@apache.org> wrote: > Hi IPMC, > > I'm calling a vote for Weex-incubating 0.12.0-RC4 release. > In this release, source tarball only include files necessary to build Weex > SDK. > All binaries were excluded. > A build README(README_RELEASE.md) is in the tarball now. > > Thanks for peoples who were taking time to review our last RC (RC3). I'm > Hoping > this RC is doing better. > > The PPMC vote for this release has passed: > https://lists.apache.org/thread.html/0e05de680b315e453f > e8643ff297d5ebfb9cdd30ea2c982e33854ff5@%3Cdev.weex.apache.org%3E > > The tag to be voted upon: > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git > ;a=shortlog;h=refs/tags/0.12.0-rc4 > > The commit hash: > https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git > ;a=commit;h=e19ef8a4acc39cd8db2cf3be4f8369f6d7a0bb43 > > The source tarball can be found at: > https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0 > -incubating/RC4/ > > The fingerprint of key to sign release artifacts: > 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784 > > Release artifacts are signed with the following key: > https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS > > Release note about this version: > https://issues.apache.org/jira/browse/WEEX-26 > > This vote will remain open for at least 72 hours. > Please vote on releasing this RC. > > [ ] +1 approve > [ ] +0 no opinion > [ ] -1 disapprove (and reason why) > > -- > Best Regards! > -- > > sospartan > https://weex-project.io > -- Best Regards! -- sospartan https://weex-project.io
[VOTE]: Apache Weex-incubating Release 0.12.0-RC4
Hi IPMC, I'm calling a vote for Weex-incubating 0.12.0-RC4 release. In this release, source tarball only include files necessary to build Weex SDK. All binaries were excluded. A build README(README_RELEASE.md) is in the tarball now. Thanks for peoples who were taking time to review our last RC (RC3). I'm Hoping this RC is doing better. The PPMC vote for this release has passed: https://lists.apache.org/thread.html/0e05de680b315e453fe8643ff297d5 ebfb9cdd30ea2c982e33854ff5@%3Cdev.weex.apache.org%3E The tag to be voted upon: https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git ;a=shortlog;h=refs/tags/0.12.0-rc4 The commit hash: https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h= e19ef8a4acc39cd8db2cf3be4f8369f6d7a0bb43 The source tarball can be found at: https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0-incubating/RC4/ The fingerprint of key to sign release artifacts: 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784 Release artifacts are signed with the following key: https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS Release note about this version: https://issues.apache.org/jira/browse/WEEX-26 This vote will remain open for at least 72 hours. Please vote on releasing this RC. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Best Regards! -- sospartan https://weex-project.io
Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC3
loaded from ASF sources. However, if these are not available > >through ASF or 3rd party artefact repos ( e.g. mvnrepository.com) it > >is advised that the project contacts the (appropriate) ASF project > that > >delivers such solutions and have them included in these artefact > repos. The > >project can then have such retrieved through the depency mgt solution > used > >by the project; > >3. gradle-wrapper.jar is generated by executing a gradle task > >(./gradle wrapper), and is based on > > 1. the gradle version used (by the person having downloaded the > > source) > > 2. potential gradle configuration elements included in the > > project's source code (build.gradle, etc). > > > > No gradle-wrapper.jar artefact was found via mvnrepository.com. The > ideal > > situation (to resolve the major issue discussed in this thread) would be > if > > such convenience download would be made available through the various jar > > repos (e.g. mvnrepository). This should (preferably) be done by the > Gradle > > community/organisation. However, in the short term, the project could > > adjust the gradlew scripts in the codebase to have that invoke the > > download from the project's repo ((in ./gradlew for linux initiate e.g. > > wget), and in ./gradlew.bat initiate an equivalent)) > > > > > > I trust the above helps to clear the air. > > > > Best regards, > > > > Pierre Smits > > > > ORRTIZ.COM <http://www.orrtiz.com> > > OFBiz based solutions & services > > > > OFBiz Extensions Marketplace > > http://oem.ofbizci.net/oci-2/ > > > > On Fri, May 5, 2017 at 3:57 AM, sospartan <sospar...@gmail.com> wrote: > > > >> Taylor, > >> Can you point out which objections you are agreed exactly? > >> > >> > >> > >> On Fri, May 5, 2017 at 9:31 AM, P. Taylor Goetz <ptgo...@gmail.com> > >> wrote: > >> > >> > Apologies for the auto correct. > >> > > >> > Please sub "Niclas" for "Nicolas". > >> > > >> > -Taylor > >> > > >> > > On May 4, 2017, at 8:43 PM, P. Taylor Goetz <ptgo...@gmail.com> > >> wrote: > >> > > > >> > > Nicolas, > >> > > > >> > > I understand and appreciate your passion, but would respectfully ask > >> > that you step down your tone a little bit. Craig and John have both > >> taken > >> > time to review the release candidate (which you should be appreciative > >> of > >> > -- getting IPMC members to review a release can be difficult). In my > >> > opinion their reviews bring up some valid points that need to be > >> considered. > >> > > > >> > > Weex, by its nature, has a complicated codebase with respect to > >> > licensing and building from source. It is a far cry from a java > project > >> > with a Pom and a a "src" directory. It pulls in a lot of different > code > >> > that needs to be considered and evaluated. Going forward the (P)PMC > will > >> > need to understand that and as a TLP will need to be able to address > >> issues > >> > accordingly. > >> > > > >> > > What may seem like "Incubator hazing" right now, I would argue, is > an > >> > exercise in making sure the podling has what it takes to operate as a > >> fully > >> > functional TLP. No two podlings are the same, and some face certain > >> burdens > >> > that others do not. > >> > > > >> > > For now can we try to turn the thread toward a more constructive > path > >> > that benefits both the podling and the Incubator? > >> > > > >> > > For what it's worth, I agree with some (not all) of the objections > >> that > >> > have been raised. So I would be a -1 as well. > >> > > > >> > > -Taylor > >> > > > >> > > > >> > > > >> > >> On May 4, 2017, at 3:02 AM, Niclas Hedhman <nic...@hedhman.org> > >> wrote: > >> > >> > >> > >> Sorry, but if you don't know the background on that file, then > >> perhaps > >> > you > >> > >> think I am "not civil"... The fact is that NOTICE file doesn't > >> require > >&g
Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC3
Taylor, Can you point out which objections you are agreed exactly? On Fri, May 5, 2017 at 9:31 AM, P. Taylor Goetz <ptgo...@gmail.com> wrote: > Apologies for the auto correct. > > Please sub "Niclas" for "Nicolas". > > -Taylor > > > On May 4, 2017, at 8:43 PM, P. Taylor Goetz <ptgo...@gmail.com> wrote: > > > > Nicolas, > > > > I understand and appreciate your passion, but would respectfully ask > that you step down your tone a little bit. Craig and John have both taken > time to review the release candidate (which you should be appreciative of > -- getting IPMC members to review a release can be difficult). In my > opinion their reviews bring up some valid points that need to be considered. > > > > Weex, by its nature, has a complicated codebase with respect to > licensing and building from source. It is a far cry from a java project > with a Pom and a a "src" directory. It pulls in a lot of different code > that needs to be considered and evaluated. Going forward the (P)PMC will > need to understand that and as a TLP will need to be able to address issues > accordingly. > > > > What may seem like "Incubator hazing" right now, I would argue, is an > exercise in making sure the podling has what it takes to operate as a fully > functional TLP. No two podlings are the same, and some face certain burdens > that others do not. > > > > For now can we try to turn the thread toward a more constructive path > that benefits both the podling and the Incubator? > > > > For what it's worth, I agree with some (not all) of the objections that > have been raised. So I would be a -1 as well. > > > > -Taylor > > > > > > > >> On May 4, 2017, at 3:02 AM, Niclas Hedhman <nic...@hedhman.org> wrote: > >> > >> Sorry, but if you don't know the background on that file, then perhaps > you > >> think I am "not civil"... The fact is that NOTICE file doesn't require > any > >> inclusion of what the project depends on, since they are not bundled, > but > >> will be downloaded during build. In a previous round, we were told to > take > >> it out of NOTICE for that reason (not bundled) and I argued that we > should > >> keep it in to make it more reasonable for downstreams to get an idea of > >> what a binary distro will actually contain. This file was the > compromise of > >> providing such details to downstream. > >> > >> Now you say, "Uhhh, it is unclear..." when in reality it would be even > more > >> unclear if we left it out, as some people on this very list pushed for > on a > >> previous RC. > >> > >> So, yes, I get pissed off as well. The incubator over time is getting > more > >> and more intolerant at podling's first release, and I think it is the > wrong > >> way to go. It is disheartening... truly... > >> > >> > >> Niclas > >> > >>> On Thu, May 4, 2017 at 1:57 PM, Craig Russell <apache@gmail.com> > wrote: > >>> > >>> I'm going to call foul on this one. > >>> > >>> If you cannot be civil, then leave the discussion to others. > >>> > >>> Craig > >>> > >>>> On May 3, 2017, at 7:24 PM, Niclas Hedhman <nic...@hedhman.org> > wrote: > >>>> > >>>> BUT ALSO figuring out what to start looking for. For fak sake, > >>>> man Get a grip on reality! > >>> > >>> Craig L Russell > >>> Secretary, Apache Software Foundation > >>> c...@apache.org http://db.apache.org/jdo > >>> > >>> > >>> - > >>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >>> For additional commands, e-mail: general-h...@incubator.apache.org > >>> > >>> > >> > >> > >> -- > >> Niclas Hedhman, Software Developer > >> http://polygene.apache.org - New Energy for Java > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- sospartan Phone:13588488290 HangZhou
Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC3
information (compared to Maven Central uploads) how > that is to be handled, since the content that is uploaded need to be part > of a source release. > > > 7. The scripts/rh contains LICENSE and NOTICE files. These should be in > the top level directory of the release. > > The scripts/ directory is mistakenly included in the dist. > > > 8. There is an executable file that doesn't belong: > > > > clr% ls -l start > > -rwxr-xr-x@ 1 clr staff 161 Apr 27 20:34 start > > What's the problem with "executable file"? It is a shell script, and since > when are we not allowed to ship that? > > Granted; lacking license header, but that is not your complaint. > > > 9. There is an executable gradlew in sdk/gradle that doesn't belong in a > source release. > > Port of your point 1, and gradlew is another shell script. ARE YOU SAYING > that shell scripts are not allowed in source distros? > > > 10. There are shared objects in sdk/libs that don't belong in a source > release. > > Alright, this is a issue that I am not convinced either way. I agree that > "doesn't belong", but on the other hand, the steps to set up (and get > working) the Android Native Development Kit (not talking about the Android > SDK) is substantial. By allowing these built binaries, we can avoid that > for most users, who normally never touch the NDK. By demanding that these > binaries are taken out, then you just condemned this project to produce a > Binary Release as well, which was not planned for this release. > > > 11. There are NOTICE and LICENSE files in ios/sdk that seem to be unix > executable files. > > clr% ls -l ios/sdk > > total 40 > > -rwxr-xr-x@ 1 clr staff 11343 Apr 27 20:34 LICENSE > > -rwxr-xr-x@ 1 clr staff575 Apr 27 20:34 NOTICE > > An honest mistake, and shouldn't stop a release. > > > 12. The README.md doesn't tell me how to build/use org.apache.weex. The > first several lines refer to third-party projects from Alibaba and > cocoapods. How do I use the Apache project? > > Well, you just introduced more complexity in "using the project" with your > insistence on no binaries, and more so if your "no execute flag" is also > now not allowed. AFAIK, there is no obligation that the source distribution > must contain all details needed to build the project, only that it can be > built. But for you convenience; > > 1. Install Gradle and learn how to use it. > 2. Install Maven and learn how to use it. > 3. Install Android NDK and learn how to use it. > 4. Install Android SDK and learn how to use it. > 5. Install Xcode and learn how to use it. > 6. Install IOS SDK and learn how to use it. > 7. Build each part with the tool needed. > > > Cheers > -- > Niclas Hedhman, Software Developer > http://polygene.apache.org - New Energy for Java > -- sospartan Phone:13588488290 HangZhou
[VOTE]: Apache Weex-incubating Release 0.12.0-RC3
Hi all, I'll calling a vote for Weex-incubating 0.12.0-RC3 release. The PPMC vote for this release has passed: https://lists.apache.org/thread.html/c5514c86433e3551cae00b21a77a1407ee20846f6565f9701d78c85b@%3Cdev.weex.apache.org%3E The tag to be voted upon: https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git ;a=shortlog;h=refs/tags/0.12.0-rc3 The commit hash: https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h=702d04c4922105069f537afdb4688f808530994d The source tarball can be found at: https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0-incubating/RC3/ The fingerprint of key to sign release artifacts: 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784 Release artifacts are signed with the following key: https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS Release note about this version: https://issues.apache.org/jira/browse/WEEX-26 This vote will remain open for at least 72 hours. Please vote on releasing this RC. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Best Regards! -- sospartan https://weex-project.io
Re: View archive on podling private@ list
Thank you. On Tue, Apr 25, 2017 at 11:10 AM, Dave Fisher <dave2w...@comcast.net> wrote: > You must be on the PPMC(podling), a Mentor, or an Apache Member for > private ML access. > > Mentors should be helping podlings with these tasks. > > Regards, > Dave > > Sent from my iPhone > > > On Apr 24, 2017, at 7:02 PM, sospartan <sospar...@gmail.com> wrote: > > > > Yes, that the RESULT I need. Thank you. > > But It's empty in content when I open this address. > > I want make sure. So, Is there a specific rule that committer can not > view > > these archives of private podling mail list? > > > >> On Tue, Apr 25, 2017 at 2:41 AM, Josh Elser <els...@apache.org> wrote: > >> > >> To avoid disclosing the name included in the subject, here is a > permalink > >> to the RESULT message for a VOTE for a new committer sent by Adam Feng > at > >> 2017-04-24 02:51 (-0400). > >> > >> https://lists.apache.org/thread.html/c26b89e59557ae8793bac1e > >> ddeb9d03bfa3e4203da0e50face55193b@%3Cprivate.weex.apache.org%3E > >> > >> Hopefully this is the one you meant... Pinging your mentors in the > future > >> might be better to avoid any chance of accidentally leaking some private > >> context :) > >> > >> - Josh > >> > >> sospartan wrote: > >> > >>> Hi, > >>> May I ask who has karma to view archives of podling private@ list? I'm > >>> weex-incubating committer, but can't view archive of private. When I > try > >>> to open > >>> > >>> https://lists.apache.org/list.html?priv...@weex.apache.org , it's > >>> redirect > >>> to commits@ list. > >>> > >>> I need to get permalink of a vote thread. > >>> > >>> > >> - > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > >> For additional commands, e-mail: general-h...@incubator.apache.org > >> > >> > > > > > > -- > > sospartan > > Phone:13588488290 > > HangZhou > > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- sospartan Phone:13588488290 HangZhou
Re: View archive on podling private@ list
Yes, that the RESULT I need. Thank you. But It's empty in content when I open this address. I want make sure. So, Is there a specific rule that committer can not view these archives of private podling mail list? On Tue, Apr 25, 2017 at 2:41 AM, Josh Elser <els...@apache.org> wrote: > To avoid disclosing the name included in the subject, here is a permalink > to the RESULT message for a VOTE for a new committer sent by Adam Feng at > 2017-04-24 02:51 (-0400). > > https://lists.apache.org/thread.html/c26b89e59557ae8793bac1e > ddeb9d03bfa3e4203da0e50face55193b@%3Cprivate.weex.apache.org%3E > > Hopefully this is the one you meant... Pinging your mentors in the future > might be better to avoid any chance of accidentally leaking some private > context :) > > - Josh > > sospartan wrote: > >> Hi, >> May I ask who has karma to view archives of podling private@ list? I'm >> weex-incubating committer, but can't view archive of private. When I try >> to open >> >> https://lists.apache.org/list.html?priv...@weex.apache.org , it's >> redirect >> to commits@ list. >> >> I need to get permalink of a vote thread. >> >> > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- sospartan Phone:13588488290 HangZhou
Re: [VOTE]: Apache Weex-incubating Release 0.12.0-RC2
he Bitcoin > > blockchain > > > > toolchain, as they distrust everything, and settled on some binary > from > > > > decades ago with a known hash as the starting point. In any event, > ASF > > > > would collapse under the "they may contain malware" banner of > paranoia. > > > > > > > > I don't buy it, since I trust my fellow folks at ASF rather than > assume > > > > malevolence from everyone. > > > > > > > > > > > I don't disagree with you. And now may be a good time to bring this > back > > > up. But for now, its not allowable in the release. See also > > > https://issues.apache.org/jira/browse/LEGAL-288 > > > > > > > > > > > > > In this particular case, I don't think that gradle-wrapper.jar ever > > > > changes, so committing a new version would set off red flags, at > least > > > with > > > > me (used Gradle for about 7 years now). A small script that traverse > > all > > > of > > > > Apache GitHub and compares them all?? > > > > > > > > > > > > > > > Note on LICENSE; > > > > > > IIUIC, the source distribution doesn't ship any dependencies > > (except > > > > Gradle > > > > > > above), and there is only Apache License to be considered. > > > > > > > > > > > > As for NOTICE, the ASF documentation you point to, basically says > > > that > > > > a) > > > > > > don't put in anything that is not bundled (i.e. just about > nothing > > in > > > > the > > > > > > source release), b) no burden on downstream users. HOWEVER, by > > > > excluding > > > > > > the list of dependencies that will be in the resulting product, > we > > > > would > > > > > > actually increase the burden of downstream users as they would > need > > > to > > > > > > figure out what licensing requirements will come out of it all, > if > > > they > > > > > > choose to distribute. > > > > > > Therefor, I would argue that documentation is in this case > arguing > > > > against > > > > > > itself in a single sentence, and think that the approach taken by > > > Weex > > > > is > > > > > > appropriate. > > > > > > > > > > > > > > > > I disagree. I think you're thinking of source release vs binary > > > release. > > > > > Weex has only presented a source release. > > > > > > > > I am aware of that, but the documentation says "make it easier for > the > > > > downstream" and by "excluding all non-bundled, but required, > > dependencies > > > > from NOTICE" we actually make it harder for the downstream. And > sorry, > > I > > > > place "common sense" and "tribal knowledge" way over someone writing > a > > > > documentation and perhaps didn't realize the consequences. I never > stop > > > > thinking, just because I read something somewhere. > > > > > > > > > > > I'm not sure what a valid response to this would be. I don't believe > we > > > should be taking into account ease of use for downstream consumers, > > however > > > at the end of the day those downstream consumers of a source release > > > eventually get a binary and that binary should include proper data. > > What I > > > am trying to say is that these contents look more appropriate for the > > > binary release, which would be a satisfactory use case for downstream > > > consumers. > > > > > > > > > > > > > > > > > Cheers > > > > -- > > > > Niclas Hedhman, Software Developer > > > > http://polygene.apache.org - New Energy for Java > > > > > > > > > > > > > > > -- > > Niclas Hedhman, Software Developer > > http://polygene.apache.org - New Energy for Java > > > -- sospartan Phone:13588488290 HangZhou
View archive on podling private@ list
Hi, May I ask who has karma to view archives of podling private@ list? I'm weex-incubating committer, but can't view archive of private. When I try to open https://lists.apache.org/list.html?priv...@weex.apache.org , it's redirect to commits@ list. I need to get permalink of a vote thread. -- Best Regards! -- sospartan https://weex-project.io
[VOTE]: Apache Weex-incubating Release 0.12.0-RC2
Hi all, I'll calling a vote for Weex-incubating 0.12.0-RC2 release. The PPMC vote for this release has passed: https://lists.apache.org/thread.html/d544a60a4038f9d053f7ea1eca0d162b9aef392551a02a0401041e8f@%3Cdev.weex.apache.org%3E The tag to be voted upon: https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git ;a=shortlog;h=refs/tags/0.12.0-rc1 The commit hash: https://git-wip-us.apache.org/repos/asf?p=incubator-weex.git;a=commit;h= 9ac0c82443e65b1c9d8a2714fea6b9a5b8af9907 The source tarball can be found at: https://dist.apache.org/repos/dist/dev/incubator/weex/0.12.0-incubating/RC1/ The fingerprint of key to sign release artifacts: 97B9 6598 A6A3 B63C 53BD 77E9 44C5 2286 22B9 7784 Release artifacts are signed with the following key: https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS Release note about this version: https://issues.apache.org/jira/browse/WEEX-26 This vote will remain open for at least 72 hours. Please vote on releasing this RC. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) -- Best Regards! -- sospartan https://weex-project.io
Re: Request karma for editing podling report wiki
Thanks. On Wed, Apr 5, 2017 at 4:12 PM, Nick Burch <apa...@gagravarr.org> wrote: > On Wed, 5 Apr 2017, sospartan wrote: > >> I'm request for the karma to editing podling report wiki. >> My wiki username: sospartan >> > > Karma granted, happy reporting! > > Nick > > - > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > -- sospartan Phone:13588488290 HangZhou
Request karma for editing podling report wiki
Hi , I'm request for the karma to editing podling report wiki. Could anyone please grant me that? My wiki username: sospartan Thanks. Best Regards! -- sospartan https://weex-project.io
