Re: Minified Javascript in source releases (was Re: [VOTE] Release Apache ECharts (incubating) 4.1.0.rc3)

[Christopher]

On Wed, May 23, 2018 at 12:16 AM Greg Stein  wrote:

> On Mon, May 21, 2018 at 2:52 AM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > > Javascript code that is minified or combined in any major way is much
> > more
> > > like binary code in that respect. It is true that somebody *could*
> > inspect
> > > the correlation, but it is not true that this inspection is either
> > normally
> > > done or easily done.
> >
> > Thanks Ted I’ve not thought of it in that way before. I've seen several
> > source releases that include minified javascript I'm just curious what
> > people think about this.
> >
> > Do people think it OK to include minified JS in a source release if:
> > 1. It's ASF developed code and the full unminified source code is
> included
> > as well.
> >
>
> Absolutely.
>
>
Also agree, yes.


> Think "autoconf" ... the resulting "configure" file is as opaque as a
> minified JS file or a binary. Nobody edits/modifies that shell script. And
> we've been doing this for *years* ... it's natural and normal.
>
>
I agree. It's only a problem if the project does not include the original
source, like in https://issues.apache.org/jira/browse/THRIFT-4119 (an
outstanding omission of source issue currently described as "intended
behavior").


> The general rule is "don't place generated artifacts into source control",
> but we nearly always include generated artifacts in our source releases.
>
>
> > 2. The minified JS is 3rd party code, is identified by version (and thus
> > can be checked via a comparison with the canonical minified version)
> >
>
> I recommend using a CDN for these, when possible (eg. bootstrap and jquery)
> as noted else-thread. That works well for the end-user, and avoids many of
> these questions.
>
>
Accumulo recently addressed a similar situation. We ended up bundling
non-minimized, but made the webapp configurable, in case users want to
switch to a non-bundled minimized version, a more up-to-date version
(jQuery gets a lot of security updates), or one from their preferred CDN. I
would strongly agree with Greg's recommendation to use a CDN by default...
but if you need to bundle... making it user-configurable might be an option.

There might be another good reason to avoid bundling minified versions, and
this reason specifically applies to *minified* (obfuscated) source (rather
than to all generated code): that is, it's not considered "free software"
according to the Free Software Foundation (
http://www.gnu.org/philosophy/free-sw.html), nor are they considered "open
source" according to the Open Source Initiative (http://opensource.org/osd).
Of course, these definitions aren't necessarily ASF definitions... but they
do tend to be respected definitions (this was first brought to my attention
by the Fedora/RedHat community, which tends to be very strict about these
things).


> Cheers,
> -g
>

Re: Minified Javascript in source releases (was Re: [VOTE] Release Apache ECharts (incubating) 4.1.0.rc3)

[Greg Stein]

On Mon, May 21, 2018 at 2:52 AM Justin Mclean 
wrote:

> Hi,
>
> > Javascript code that is minified or combined in any major way is much
> more
> > like binary code in that respect. It is true that somebody *could*
> inspect
> > the correlation, but it is not true that this inspection is either
> normally
> > done or easily done.
>
> Thanks Ted I’ve not thought of it in that way before. I've seen several
> source releases that include minified javascript I'm just curious what
> people think about this.
>
> Do people think it OK to include minified JS in a source release if:
> 1. It's ASF developed code and the full unminified source code is included
> as well.
>

Absolutely.

Think "autoconf" ... the resulting "configure" file is as opaque as a
minified JS file or a binary. Nobody edits/modifies that shell script. And
we've been doing this for *years* ... it's natural and normal.

The general rule is "don't place generated artifacts into source control",
but we nearly always include generated artifacts in our source releases.


> 2. The minified JS is 3rd party code, is identified by version (and thus
> can be checked via a comparison with the canonical minified version)
>

I recommend using a CDN for these, when possible (eg. bootstrap and jquery)
as noted else-thread. That works well for the end-user, and avoids many of
these questions.

Cheers,
-g

Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-beta

[彭勇升 Peng Yongsheng]

Hi all,

The vote for releasing Apache SkyWalking 5.0.0-beta (incubating) is closed, now.

Vote result:
3 (+1 binding) (st...@apache.org , m...@apache.org 
 and willem.ji...@gmail.com 
)
No -1.

Thank you everyone for taking the time to review the release and help us. 

I will procedd to publish the release and send ANNOUNCE.

—
Yongsheng Peng
Apache SkyWalking PPMC member


—
Yongsheng Peng
Apache SkyWalking PPMC member

Re: Minified Javascript in source releases (was Re: [VOTE] Release Apache ECharts (incubating) 4.1.0.rc3)

[Hen]

On Mon, May 21, 2018 at 4:22 PM, Ted Dunning  wrote:

> On Mon, May 21, 2018, 21:12 Justin Mclean 
> wrote:
>
> > Hi,
> >
> > > Why does this need to be included at all? Why not just provide a
> pointer
> > to
> > > the canonical minified version?
> >
> > Most common occurrence (off the top of my head) is a minified version of
> > bootstrap for project site / documentations. So your view is that that
> > shouldn’t be included in a source release?
> >
>
> Sure. D3 and jQuery will wind up in the same boat.
>
> I would not go so far as to emphatically say not to include them, but I
> don't see the real need to include them given that they are so easily
> downloadable. A URL and a checksum keeps the distro clean.
>

Point to a CDN instead of copying into the distro?

On the one hand, one can argue a CDN is bad if someone wants to read
offline. On the other, I don't like being added to the security update
chain if there is an issue in D3/jQuery/bootstrap etc.

Hen

Re: [VOTE] Apache Crail 1.0-incubating (RC3)

[Willem Jiang]

Hi,

I just tried to build from the source kit and got the test error due to
missing crail-site.conf.
I checked the README and cannot find any note for solving this problem.

testRenameFile(org.apache.crail.ClientTest): null/conf/crail-site.conf (No
such file or directory)
  testRenameFile(org.apache.crail.ClientTest)
  testlookupDirectory(org.apache.crail.ClientTest):
null/conf/crail-site.conf (No such file or directory)


Willem Jiang

Blog: http://willemjiang.blogspot.com (English)
  http://jnn.iteye.com  (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem

On Tue, May 22, 2018 at 3:28 PM, Jonas Pfefferle  wrote:

> Please vote to approve the source release of Apache Crail 1.0-incubating
> (RC3).
> This release candidate fixes all issues raised in the last IPMC vote:
> - Add DISCLAIMER
> - Move IBM copyright from NOTICE file to CREDITS file and fix formatting
> of Apache copyright
> - Leading directory name in tar/zip file is now
> "apache-crail-1.0-incubating-src"
>
> The podling dev vote thread:
>
> https://www.mail-archive.com/dev@crail.apache.org/msg00268.html
>
> The result:
>
> https://www.mail-archive.com/dev@crail.apache.org/msg00274.html
>
> Commit hash: 0db64fddad52044eab75ee73e1857c7bcf6fae7d
>
> https://git1-us-west.apache.org/repos/asf?p=incubator-crail.
> git;a=commit;h=0db64fddad52044eab75ee73e1857c7bcf6fae7d
>
> Release files can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/crail/1.0-rc3/
>
> The vote is open for at least 72 hours and passes if a majority of at least
> 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Crail 1.0-incubating
> [ ] -1 Do not release this package because ...
>
> Thanks,
> Jonas
>
>
>
>
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Retire the Slider podling

[Craig Russell]

+1

Thanks for handling this so well instead of making others step in.

Craig

> On May 20, 2018, at 10:59 AM, Billie Rinaldi  wrote:
> 
> After a long period of low activity, the Slider PPMC has recently decided
> upon retirement [1]. Please vote on whether we should retire the Slider
> podling. Here is my +1 (binding).
> 
> [ ] +1 Retire Slider
> [ ] +0 No opinion
> [ ] -1 Do not retire Slider because ...
> 
> This vote will remain open for 72 hours.
> 
> [1]: https://s.apache.org/V8SB

Craig L Russell
c...@apache.org


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache NetBeans 9.0 RC1 (incubating) rc1

[Emilian Bold]

> b) Justin provided detailed feedback on the 9.0-Beta-RC3 on (possible) 
> needed improvements/fixes for the binary dist LICENSE/NOTICE file [2],
> thereafter recorded as a todo action list on the wiki [3] (end of page).
> Some of those points have been addressed (marked DONE), but many/most
> are not, and neither resolved/fixed (or otherwise marked as NVT).
> As just an example, Justin noticed for the ./ide/modules/ext/smackx.jar
> file that it included the BSD licensed JZlib, which wasn't mentioned in
> the LICENSE file. And still isn't for this 9.0-RC1.
> I don't think any of those are blockers, but it would be good to address
> these (create NETBEANS issues for them) before the final 9.0 release.

I have created 26 NETBEANS JIRA issues with Justin's remarks and we'll go 
through them before the final 9.0 release.

--emi

‐‐‐ Original Message ‐‐‐

On 21 May 2018 3:54 PM, Ate Douma  wrote:

> I'm inclined to vote positive on this RC1, overall looks great!
> 
> -   verified the MD5 and SHA1, and PGP signatures with the ASC files.
> -   executed rat check (ant rat) and verified the report.
> -   build and run the source (using JDK8), and all seems fine.
> 
> However I still have two questions:
> 
> a) nbbuild/licenses folder still has the GPL license file, which I
> 
> thought/expected no longer should be needed with the fix from
> 
> NETBEANS-305 [1]?
> 
> Is there still a GPL usage left? If so this then could be a blocker IMO.
> 
> b) Justin provided detailed feedback on the 9.0-Beta-RC3 on (possible)
> 
> needed improvements/fixes for the binary dist LICENSE/NOTICE file [2],
> 
> thereafter recorded as a todo action list on the wiki [3] (end of page).
> 
> Some of those points have been addressed (marked DONE), but many/most
> 
> are not, and neither resolved/fixed (or otherwise marked as NVT).
> 
> As just an example, Justin noticed for the ./ide/modules/ext/smackx.jar
> 
> file that it included the BSD licensed JZlib, which wasn't mentioned in
> 
> the LICENSE file. And still isn't for this 9.0-RC1.
> 
> I don't think any of those are blockers, but it would be good to address
> 
> these (create NETBEANS issues for them) before the final 9.0 release.
> 
> Regards, Ate
> 
> [1] https://issues.apache.org/jira/browse/NETBEANS-305
> 
> https://github.com/apache/incubator-netbeans/pull/540
> 
> [2]
> 
> 
> http://mail-archives.apache.org/mod_mbox/incubator-general/201801.mbox/
> 
> [3]
> 
> 
> https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+9.0+Beta+rc3
> 
> On 2018-05-21 00:33, Emilian Bold wrote:
> 
> 
> > Hi all,
> > 
> > The Apache NetBeans community has voted on and approved a proposal to 
> > release Apache NetBeans 9.0 RC1 (incubating) rc1.
> > 
> > We now kindly request that the Incubator PMC members review and vote on 
> > this incubator release candidate.
> > 
> > Apache NetBeans 9.0 RC1 (incubating) vote thread:
> > 
> > https://lists.apache.org/thread.html/c2a06adc83e2819e6d96c7dff8d0e22a97001f99bfda12515d4d9609@
> > 
> > Apache NetBeans 9.0 RC1 (incubating) vote result thread:
> > 
> > https://lists.apache.org/thread.html/94f7a5e4601e26c7edb8264df7df53dd8ed215ecfc568816a162f2af@
> > 
> > Apache NetBeans 9.0 RC1 (incubating) constitutes all the modules in the 
> > Apache NetBeans Git repo, which together provide the NetBeans Platform 
> > (i.e., the underlying application framework), as well as all the modules 
> > that provide the Java SE-related features of Apache NetBeans.
> > 
> > In short, Apache NetBeans 9.0 RC1 (incubating) is a full IDE for Java SE 
> > development.
> > 
> > Build artifacts available here:
> > 
> > https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-rc1-rc1
> > 
> > The specific artifact to be voted on:
> > 
> > https://dist.apache.org/repos/dist/dev/incubator/netbeans/incubating-netbeans-java/incubating-9.0-rc1-rc1/incubating-netbeans-java-9.0-rc1-source.zip
> > 
> > Included in the above are the DEPENDENCIES, DISCLAIMER, LICENSE, and NOTICE 
> > files, as well as a README file with build instructions, which are the same 
> > as these:
> > 
> > https://github.com/apache/incubator-netbeans/blob/master/README.md
> > 
> > SHA1: a1a265455c8246f849b14982fa3c36b351b21876
> > 
> > KEYS file:
> > 
> > https://dist.apache.org/repos/dist/release/incubator/netbeans/KEYS
> > 
> > Apache NetBeans Git Repo tag: 9.0-rc1-rc1:
> > 
> > https://github.com/apache/incubator-netbeans/tree/9.0-rc1-rc1
> > 
> > Note: NetBeans license violation checks are managed via the 
> > rat-exclusions.txt file:
> > 
> > https://github.com/apache/incubator-netbeans/blob/master/nbbuild/rat-exclusions.txt
> > 
> > Rat report shows no unknown licenses, except for license files:

Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-beta

[mck]

> 
> Alternatively I think if committers use mail-relay.apache.org
> https://reference.apache.org/committer/email with an @apache.org From
> address then the 'real name' can be in any language or form, as
> demonstrated here by "mck" :)


Ha! Good catch Stian :-D
Yeah, it's not so much knowing your exact name. 
Any distinguishable (nick) name, or apache alias, works just fine.
If you had written Peng, or Yongsheng, or pengys, I would have identified you a 
whole lot easier.

regards,
Mick

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Crail 1.0-incubating (RC3)

[Luciano Resende]

+1 for releasing.

Validated package contents, rat, etc...

And thanks to the Crail community for all the work getting this process
going.


On Tue, May 22, 2018 at 12:28 AM, Jonas Pfefferle  wrote:

> Please vote to approve the source release of Apache Crail 1.0-incubating
> (RC3).
> This release candidate fixes all issues raised in the last IPMC vote:
> - Add DISCLAIMER
> - Move IBM copyright from NOTICE file to CREDITS file and fix formatting
> of Apache copyright
> - Leading directory name in tar/zip file is now
> "apache-crail-1.0-incubating-src"
>
> The podling dev vote thread:
>
> https://www.mail-archive.com/dev@crail.apache.org/msg00268.html
>
> The result:
>
> https://www.mail-archive.com/dev@crail.apache.org/msg00274.html
>
> Commit hash: 0db64fddad52044eab75ee73e1857c7bcf6fae7d
>
> https://git1-us-west.apache.org/repos/asf?p=incubator-crail.
> git;a=commit;h=0db64fddad52044eab75ee73e1857c7bcf6fae7d
>
> Release files can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/crail/1.0-rc3/
>
> The vote is open for at least 72 hours and passes if a majority of at least
> 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Crail 1.0-incubating
> [ ] -1 Do not release this package because ...
>
> Thanks,
> Jonas
>
>
>
>
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Luciano Resende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: [VOTE] Apache Crail 1.0-incubating (RC3)

[Julian Hyde]

Forwarding my vote from the PPMC vote:

+1 (binding)

Julian


> On May 22, 2018, at 12:29 AM, Jonas Pfefferle  wrote:
> 
> Forgot to add:
> 
> Release artifacts have been signed with the following key:
> https://people.apache.org/keys/committer/pepperjo.asc
> 
> Thanks,
> Jonas
> 
> On Tue, 22 May 2018 09:28:01 +0200
> "Jonas Pfefferle"  wrote:
>> 
>> Please vote to approve the source release of Apache Crail 1.0-incubating 
>> (RC3).
>> This release candidate fixes all issues raised in the last IPMC vote:
>> - Add DISCLAIMER
>> - Move IBM copyright from NOTICE file to CREDITS file and fix formatting of 
>> Apache copyright
>> - Leading directory name in tar/zip file is now 
>> "apache-crail-1.0-incubating-src"
>> 
>> The podling dev vote thread:
>> 
>> https://www.mail-archive.com/dev@crail.apache.org/msg00268.html
>> 
>> The result:
>> 
>> https://www.mail-archive.com/dev@crail.apache.org/msg00274.html
>> 
>> Commit hash: 0db64fddad52044eab75ee73e1857c7bcf6fae7d
>> 
>> https://git1-us-west.apache.org/repos/asf?p=incubator-crail.git;a=commit;h=0db64fddad52044eab75ee73e1857c7bcf6fae7d
>> 
>> Release files can be found at:
>> https://dist.apache.org/repos/dist/dev/incubator/crail/1.0-rc3/
>> 
>> The vote is open for at least 72 hours and passes if a majority of at least
>> 3 +1 PMC votes are cast.
>> 
>> [ ] +1 Release this package as Apache Crail 1.0-incubating
>> [ ] -1 Do not release this package because ...
>> 
>> Thanks,
>> Jonas
> 


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-beta

[Stian Soiland-Reyes]

On Tue, 22 May 2018 22:33:21 +1000, mck  wrote:
>  - Peng Yongsheng, please remember to keep your english (ascii) name in the 
> email from field along with your real name: 彭勇升 
> When you sent the mail to IPMC there was no english name accompanying your 
> chinese name. Sheng is consistent in this practice, so is a good example. 
> I know it's unfortunate, but those of us that can't speak chinese simply find 
> it too difficult to distinguish and remember the chinese characters and names.
> This will also hinder you from getting responses and votes.

Alternatively I think if committers use mail-relay.apache.org
https://reference.apache.org/committer/email with an @apache.org From
address then the 'real name' can be in any language or form, as
demonstrated here by "mck" :)

(enabling Unicode-names in @apache.org usernames, that's
another battle for another decade..)

-- 
Stian Soiland-Reyes
The University of Manchester
https://www.esciencelab.org.uk/
https://orcid.org/-0001-9842-9718


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-beta

[彭勇升 Peng Yongsheng]

> - Peng Yongsheng, please remember to keep your english (ascii) name in the 
> email from field along with your real name: 彭勇升 
> When you sent the mail to IPMC there was no english name accompanying your 
> chinese name. Sheng is consistent in this practice, so is a good example. 
> I know it's unfortunate, but those of us that can't speak chinese simply find 
> it too difficult to distinguish and remember the chinese characters and names.
> This will also hinder you from getting responses and votes.

Thanks mck. I changed it.

—
Yongsheng Peng
Apache SkyWalking PPMC member

Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-beta

[???? Sheng Wu]

Hi, Willem


Thanks, sorry for we didn't remove this since the last vote. We spent some time 
to make sure the UI licenses are all right and necessary.


I will submit an issue soon, and try to remove those in our next (beta2) 
release, which should be soon, expected in 3 weeks.


--
Sheng Wu
Apache SkyWalking 


 




-- Original --
From:  "willem.jiang";
Date:  Tue, May 22, 2018 09:31 PM
To:  "general";

Subject:  Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-beta



Hi,

+1 for this release.

I checked the signing key, and verify the check sum.
Built the binary kit from source.

There are bunch of Apache Licenses in the binary kit which are stand Apache
Licenses.
We can do some clean up these License file in the next release.


Willem Jiang

Blog: http://willemjiang.blogspot.com (English)
  http://jnn.iteye.com  (Chinese)
Twitter: willemjiang
Weibo: willem

On Sun, May 20, 2018 at 5:08 PM,  Sheng Wu  wrote:

> Hi, IPMC
> I am asking the release vote, again. :)  Haven't had one yet. Hope we can
> have enough vote in 72 hours.
>
>
> Thanks.
>
>
>
> Sheng Wu
> Apache SkyWalking
>
> From Wu Sheng 's phone.
>
> ---Original---
> From: ".??"<8082...@qq.com>
> Date: Fri, May 18, 2018 10:06 AM
> To: "general";
> Subject: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-beta
>
>
> Hi All,
> This is a call for vote to release Apache SkyWalking (Incubating) version
> 5.0.0-beta.
>
>
> The Apache SkyWalking community has tested, voted and approved the proposed
> release of Apache SkyWalking (Incubating) 5.0.0-beta
>
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
>
> SkyWalking: APM (application performance monitor) tool for distributed
> systems,
> especially designed for microservices, cloud native and container-based
> (Docker, Kubernetes, Mesos) architectures.
> Underlying technology is a distributed tracing system.
>
>
>
> Vote Thread:
> https://lists.apache.org/thread.html/77df7fc536a95d2e3c4121a
> 3f2faf61371c31a22f1678a9d45134904@%3Cdev.skywalking.apache.org%3E
>
>
> Result Thread:
> https://lists.apache.org/thread.html/ba0939023e7e856b79093be
> 1f0b9e4e15520e5f5f67344260cb5c3ff@%3Cdev.skywalking.apache.org%3E
>
>
> Release notes:
> * https://github.com/apache/incubator-skywalking/blob/master/
> CHANGES.md#500-beta
> Release Candidate:
>
>
> *https://dist.apache.org/repos/dist/dev/incubator/skywalking/5.0.0-beta/
>
>
> Maven 2 staging repository:
> *https://repository.apache.org/content/repositories/orgapach
> eskywalking-1011/org/apache/skywalking/
>
>
> Release Tag :
> * v5.0.0-beta
>
>
> Release CommitID :
> * 5ddc4e714f2570421779a11f2589ffc32d2b8b21
>
>
> Keys to verify the Release Candidate :
> *  http://pgp.mit.edu:11371/pks/lookup?op=get=0x2EF5026E70A55777
> corresponding to pen...@apache.org
>
>
> Guide to build the release from source :
> * https://github.com/apache/incubator-skywalking/blob/master/
> docs/en/How-to-build.md
>
>
> Voting will start now (May 18th, 2018) and will remain open for at least
> 72 hours, Request all IPMC members to give their vote.
> [ ] +1 Release this package.
> [ ] +0 No opinion.
> [ ] -1 Do not release this package because??.
>
>
> ??
> Yongsheng Peng
> Apache SkyWalking PPMC member
>

Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-beta

[Willem Jiang]

Hi,

+1 for this release.

I checked the signing key, and verify the check sum.
Built the binary kit from source.

There are bunch of Apache Licenses in the binary kit which are stand Apache
Licenses.
We can do some clean up these License file in the next release.


Willem Jiang

Blog: http://willemjiang.blogspot.com (English)
  http://jnn.iteye.com  (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem

On Sun, May 20, 2018 at 5:08 PM, 吴晟 Sheng Wu  wrote:

> Hi, IPMC
> I am asking the release vote, again. :)  Haven't had one yet. Hope we can
> have enough vote in 72 hours.
>
>
> Thanks.
>
>
>
> Sheng Wu
> Apache SkyWalking
>
> From Wu Sheng 's phone.
>
> ---Original---
> From: ".彭勇升"<8082...@qq.com>
> Date: Fri, May 18, 2018 10:06 AM
> To: "general";
> Subject: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-beta
>
>
> Hi All,
> This is a call for vote to release Apache SkyWalking (Incubating) version
> 5.0.0-beta.
>
>
> The Apache SkyWalking community has tested, voted and approved the proposed
> release of Apache SkyWalking (Incubating) 5.0.0-beta
>
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
>
> SkyWalking: APM (application performance monitor) tool for distributed
> systems,
> especially designed for microservices, cloud native and container-based
> (Docker, Kubernetes, Mesos) architectures.
> Underlying technology is a distributed tracing system.
>
>
>
> Vote Thread:
> https://lists.apache.org/thread.html/77df7fc536a95d2e3c4121a
> 3f2faf61371c31a22f1678a9d45134904@%3Cdev.skywalking.apache.org%3E
>
>
> Result Thread:
> https://lists.apache.org/thread.html/ba0939023e7e856b79093be
> 1f0b9e4e15520e5f5f67344260cb5c3ff@%3Cdev.skywalking.apache.org%3E
>
>
> Release notes:
> * https://github.com/apache/incubator-skywalking/blob/master/
> CHANGES.md#500-beta
> Release Candidate:
>
>
> *https://dist.apache.org/repos/dist/dev/incubator/skywalking/5.0.0-beta/
>
>
> Maven 2 staging repository:
> *https://repository.apache.org/content/repositories/orgapach
> eskywalking-1011/org/apache/skywalking/
>
>
> Release Tag :
> * v5.0.0-beta
>
>
> Release CommitID :
> * 5ddc4e714f2570421779a11f2589ffc32d2b8b21
>
>
> Keys to verify the Release Candidate :
> *  http://pgp.mit.edu:11371/pks/lookup?op=get=0x2EF5026E70A55777
> corresponding to pen...@apache.org
>
>
> Guide to build the release from source :
> * https://github.com/apache/incubator-skywalking/blob/master/
> docs/en/How-to-build.md
>
>
> Voting will start now (May 18th, 2018) and will remain open for at least
> 72 hours, Request all IPMC members to give their vote.
> [ ] +1 Release this package.
> [ ] +0 No opinion.
> [ ] -1 Do not release this package because….
>
>
> —
> Yongsheng Peng
> Apache SkyWalking PPMC member
>

Re: [VOTE] Release Apache SkyWalking (incubating) version 5.0.0-beta

[mck]

> Voting will start now (May 18th, 2018) and will remain open for at least 72 
> hours, Request all IPMC members to give their vote.

> [ ] +1 Release this package.
> [ ] +0 No opinion.
> [ ] -1 Do not release this package because….


My vote: +1 (binding)


My notes:

 - Peng Yongsheng, please remember to keep your english (ascii) name in the 
email from field along with your real name: 彭勇升 
When you sent the mail to IPMC there was no english name accompanying your 
chinese name. Sheng is consistent in this practice, so is a good example. 
I know it's unfortunate, but those of us that can't speak chinese simply find 
it too difficult to distinguish and remember the chinese characters and names.
This will also hinder you from getting responses and votes.

 - I agree with Stian that '5.0.0-beta' should have been labeled either 
'5.0.0-beta-0' or '5.0.0-rc1'. 
You can't make any presumption about how many release attempts will be required 
to get a successful vote.
And each attempt requires a new version name, that is you should not overwrite 
release tags nor uploaded binaries. 
Even if you make a mistake, just move onto the next version: 5.0.0-beta-1, 
5.0.0-beta-2, 5.0.0-beta-3, etc
That is, it's perfectly acceptable to "skip" version numbers, because you made 
a mistake during the release process or the vote fails. You also can't make any 
presumption about how many beta or rc releases you'll need to make _before_ the 
community is ready for a GA release. The number of beta/rc releases is not 
fixed or predetermine. I also think it is good habit to never re-tag or 
uploaded over an existing version. If you take this approach Peng, then the 
releasing step becomes less ambiguous, for example the binary and source 
version is always the same as the git tag. 

 - "72 hours is not a time-out, but a minimum period"
This is important. It is crucial to be patient. There's nothing wrong with 
waiting a week, it's all up to the cadence of the developers you've got.  For 
those that have families, or for whatever other reason, it is all too easy to 
be missing-in-action for a few days.

 - "sponsored by Incubator" instead of "sponsored by the Apache Incubator PMC"
Good catch Stian. Something to fix in master so it's correct when the next 
release comes around.

regards,
Mick

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Taverna Language 0.16.0-incubating RC1

[Andy Seaborne]

bcc: dev@taverna

+1 (binding)

Source downloaded,built (java8 - fails on java10; the podling is aware 
of this) and tests pass.


Checksum and sigs verified

DISCLIAMER, LICENSE and NOTICE present.

---

The POM parent (separate release) includes other maven repos
  https://dl.bintray.com/
  https://repo.spring.io/
  https://jcenter.bintray.com/

but I'm told everything is in maven central. Raised TAVERNA-1051.

Andy

On 21/05/18 10:57, Stian Soiland-Reyes wrote:

The Taverna PPMC has voted to release:

   Apache Taverna Language 0.16.0-incubating

with +4 PPMC-binding votes. This email is the IPMC vote.

   
Vote thread:

https://lists.apache.org/thread.html/29405e13efcd3282e978982c2c4c02b1d1bf683460ce618c7248617a@%3Cdev.taverna.apache.org%3E

Result:
https://lists.apache.org/thread.html/6c30d76520c2e933c4b93db7dc87cef42f2d34871f0b6f334020d451@%3Cdev.taverna.apache.org%3E


This carries forward one +1 IPMC binding vote from myself.


Apache Taverna Language is a set of APIs for workflow definitions (SCUFL2),
Research Object Bundles and workflow inputs/outputs/run (DataBundle), as
consumed and produced by the Apache Taverna workflow system.

The API includes support for the legacy formats from Taverna 2 and Taverna 1,
and can be also used independently of Apache Taverna 3.  The command line tool
tavlang can be used for conversion and inspection of research objects and
workflow bundles.




The release candidate to be voted over is available at:

https://dist.apache.org/repos/dist/dev/incubator/taverna/source/taverna-language-0.16.0-incubating-RC1/


Checksums:

$ sha1sum *zip
1f6050994b4bd2661f343119cdcb18b83dc362cf  
apache-taverna-language-0.16.0-incubating-source-release.zip

$ sha256sum *zip
bcdba80fbea54b1532cb81b6846e5711f1efe98ad289ecd4a2c6dd2833767115  
apache-taverna-language-0.16.0-incubating-source-release.zip

$ sha512sum *zip
008672c7f7cb1e6e461a2d5113aa111208970cfe9e0b3507fb3a34bc95957db094f0d8e8829beca9496cfa6a6d023943409335839bacd0bdedc82db87d14b9aa
  apache-taverna-language-0.16.0-incubating-source-release.zip
s




Build the release candidate using:

 mvn clean install




The release candidates correspond to the following git commit:

https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-language.git;a=commit;h=c48ef9d339d7d68791691617ef2ddc56d195131e


The release candidate is signed with an (updated) GPG key:
https://www.apache.org/dist/incubator/taverna/KEYS


A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachetaverna-1019


The changelog for this release is available from JIRA:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12334881=12318322



Please vote on releasing these packages as:

   Apache Taverna Language 0.16.0-incubating


The vote is open for at least 72 hours and passes if a majority of at least
three +1 Apache Incubator PMC votes are cast.

[ ] +1 Release this package
[ ]  0 I don't feel strongly about it, but don't object
[ ] -1 Do not release this package because...


Anyone can participate in testing and voting, not just IPMC members,
please feel free to try out the release candidate and provide your
votes!

How to review a release? https://s.apache.org/review-release




-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Crail 1.0-incubating (RC3)

[Jonas Pfefferle]

Forgot to add:

Release artifacts have been signed with the following key:
https://people.apache.org/keys/committer/pepperjo.asc

Thanks,
Jonas

 On Tue, 22 May 2018 09:28:01 +0200
 "Jonas Pfefferle"  wrote:
Please vote to approve the source release of Apache Crail 
1.0-incubating (RC3).
This release candidate fixes all issues raised in the last IPMC 
vote:

- Add DISCLAIMER
- Move IBM copyright from NOTICE file to CREDITS file and fix 
formatting of Apache copyright
- Leading directory name in tar/zip file is now 
"apache-crail-1.0-incubating-src"


The podling dev vote thread:

https://www.mail-archive.com/dev@crail.apache.org/msg00268.html

The result:

https://www.mail-archive.com/dev@crail.apache.org/msg00274.html

Commit hash: 0db64fddad52044eab75ee73e1857c7bcf6fae7d

https://git1-us-west.apache.org/repos/asf?p=incubator-crail.git;a=commit;h=0db64fddad52044eab75ee73e1857c7bcf6fae7d

Release files can be found at:
https://dist.apache.org/repos/dist/dev/incubator/crail/1.0-rc3/

The vote is open for at least 72 hours and passes if a majority of 
at least

3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Crail 1.0-incubating
[ ] -1 Do not release this package because ...

Thanks,
Jonas


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org





-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Apache Crail 1.0-incubating (RC3)

[Jonas Pfefferle]

Please vote to approve the source release of Apache Crail 1.0-incubating 
(RC3).

This release candidate fixes all issues raised in the last IPMC vote:
- Add DISCLAIMER
- Move IBM copyright from NOTICE file to CREDITS file and fix formatting of 
Apache copyright
- Leading directory name in tar/zip file is now 
"apache-crail-1.0-incubating-src"


The podling dev vote thread:

https://www.mail-archive.com/dev@crail.apache.org/msg00268.html

The result:

https://www.mail-archive.com/dev@crail.apache.org/msg00274.html

Commit hash: 0db64fddad52044eab75ee73e1857c7bcf6fae7d

https://git1-us-west.apache.org/repos/asf?p=incubator-crail.git;a=commit;h=0db64fddad52044eab75ee73e1857c7bcf6fae7d

Release files can be found at:
https://dist.apache.org/repos/dist/dev/incubator/crail/1.0-rc3/

The vote is open for at least 72 hours and passes if a majority of at least
3 +1 PMC votes are cast.

[ ] +1 Release this package as Apache Crail 1.0-incubating
[ ] -1 Do not release this package because ...

Thanks,
Jonas







-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org




-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Retire the Slider podling

[Willem Jiang]

+1 (binding)


Willem Jiang



On Tue, May 22, 2018 at 4:28 AM, Vinod Kumar Vavilapalli  wrote:

> +1 (binding).
>
> With YARN services in Apache Hadoop 3.1 release, there is a good path
> forward.
>
> Thanks
> +Vind
>
> > On May 20, 2018, at 10:59 AM, Billie Rinaldi  wrote:
> >
> > After a long period of low activity, the Slider PPMC has recently decided
> > upon retirement [1]. Please vote on whether we should retire the Slider
> > podling. Here is my +1 (binding).
> >
> > [ ] +1 Retire Slider
> > [ ] +0 No opinion
> > [ ] -1 Do not retire Slider because ...
> >
> > This vote will remain open for 72 hours.
> >
> > [1]: https://s.apache.org/V8SB
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release of Apache Tephra-0.14.0-incubating [rc1]

[Jitendra Pandey]

+1 (binding)
Verified md5 of the source tarball. 
Downloaded source, built successfully, ran a few unit tests.

On 5/21/18, 9:02 PM, "Josh Elser"  wrote:

+1 (binding)

Things look good for the most part, a few things I noticed which can be 
fixed next release:

* NOTICE needs an updated copyright year
* `mvn apache-rat:check` fails on the below files


apache-tephra-0.14.0-incubating/tephra-distribution/licenses/Aopa.PL
apache-tephra-0.14.0-incubating/tephra-distribution/licenses/Asm.BSD
apache-tephra-0.14.0-incubating/tephra-distribution/licenses/JLine.BSD
apache-tephra-0.14.0-incubating/tephra-distribution/licenses/Logback.EPL
apache-tephra-0.14.0-incubating/tephra-distribution/NOTICE_BINARY


On 5/21/18 6:51 PM, James Taylor wrote:
> Hi all,
> 
> This is a call for a vote on releasing Apache Tephra 0.14.0-incubating,
> release candidate 1. This is the seventh release of Tephra. The Tephra dev
> community has voted on and approved a proposal to release Tephra
> 0.14.0-incubating, release candidate 1.
> 
> PPMC Vote Call: https://s.apache.org/jWVD
> 
> PPMC Vote Result: https://s.apache.org/zwog
> 
> The source tarball, including signatures, digests, etc. can be found at:
> 
https://dist.apache.org/repos/dist/dev/incubator/tephra/0.14.0-incubating-rc1/src
> 
> The tag to be voted upon is v0.14.0-incubating:
> 
https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=shortlog;h=refs/tags/v0.14.0-incubating
> 
> The release hash is e93942adae0ece286157a8f6a2e5c63b53669e03:
> 
https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=commit;h=e93942adae0ece286157a8f6a2e5c63b53669e03
> 
> The Nexus Staging URL:
> https://repository.apache.org/content/repositories/orgapachetephra-1011
> 
> Release artifacts are signed with the following key:
> http://people.apache.org/keys/committer/jamestaylor
> 
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
> 
> For information about the contents of this release, see:
> 
https://dist.apache.org/repos/dist/dev/incubator/tephra/0.14.0-incubating-rc1/CHANGES.txt
> 
> Please vote on releasing this package as Apache Tephra 0.14.0-incubating
> 
> The vote will be open for 72 hours.
> 
> [ ] +1 Release this package as Apache Tephra 0.14.0-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
> 
> Thanks,
> James
> 

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org