[VOTE] Release Apache SkyWalking (incubating) version 5.0.0-GA
Hi All, This is a call for vote to release Apache SkyWalking (Incubating) version 5.0.0-GA The Apache SkyWalking community has tested, voted and approved the proposed release of Apache SkyWalking (Incubating) 5.0.0-GA 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/020de64d4fff795d6bda04c7e7ec180bff7cb4bd6e06db21fe38bf1e@%3Cdev.skywalking.apache.org%3E Release notes: * https://github.com/apache/incubator-skywalking/blob/v5.0.0-GA/CHANGES.md#500-ga Release Candidate: * https://dist.apache.org/repos/dist/dev/incubator/skywalking/5.0.0-GA/ * sha512 checksums - b09bf390092f41a745a8c6f46cb891894375c8c13a1c2789dbc57c3d89f63d835058e1e41bdd816be1cbf2aa7461501db97f35952419dcc854203650cbfb676f apache-skywalking-apm-incubating-5.0.0-GA-src.tgz - 7d3a0f8acd82973dd4d31ef9e4edffe89b33bc538b12735140d2dc9129f1233ec25ac4ef124ad519685adde639acb5f631dac3a59da18c8c9c9d701f46efe8b3 apache-skywalking-apm-incubating-5.0.0-GA.tar.gz - 39d6d9c28844c447776511aab9fdbb6d015ce8834e295d394d523f9fd2d99ad1ac05697dbf9a99781219e26624a7f30987bc099e8e1a9bf014873d4ccdfadee4 apache-skywalking-apm-incubating-5.0.0-GA.zip Maven 2 staging repository: * https://repository.apache.org/content/repositories/orgapacheskywalking-1022/org/apache/skywalking Release Tag : * (GitHub Tag) https://github.com/apache/incubator-skywalking/tree/v5.0.0-GA Release CommitID : * https://github.com/apache/incubator-skywalking/tree/7070e90809a647c3fc2ede518a70afa755856dcc * Git submodule * skywalking-ui: https://github.com/apache/incubator-skywalking-ui/tree/ad3ee45dbadfae35d77238bdd7a1df593158f109 * apm-protocol/apm-network/src/main/proto: https://github.com/apache/incubator-skywalking-data-collect-protocol/tree/c02c12af12116121e25155d1f3fca0fadee5f2e9 Keys to verify the Release Candidate : * https://dist.apache.org/repos/dist/release/incubator/skywalking/KEYS corresponding to wush...@apache.org Guide to build the release from source : * https://github.com/apache/incubator-skywalking/blob/v5.0.0-GA/docs/en/How-to-build.md#build-from-apache-source-codes Voting will start now (2018/10/10 date) and will remain open for at least 72 hours, Request IPMC to give their vote. [ ] +1 Release this package. [ ] +0 No opinion. [ ] -1 Do not release this package because -- Sheng Wu Apache SkyWalking
[jira] [Commented] (INCUBATOR-222) Donation of ibm-functions/composer code to Apache OpenWhisk
[ https://issues.apache.org/jira/browse/INCUBATOR-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16643593#comment-16643593 ] Bertrand Delacretaz commented on INCUBATOR-222: --- Ok thank you, we're good in terms of iCLAs then. I'm not totally convinced that a Software Grant is not needed in this case - Our IP clearance docs have changed in 2017 and I need a confirmation, created LEGAL-420 for that. Also, I see that the code has already been imported at [https://github.com/apache/incubator-openwhisk-composer] - that's not how it should have been, the IP clearance must happen before that in principle. Considering that this ticket should be closed soon I don't think that's a major problem, but we won't be able to release that module before this IP clearance is completed. I'll add a note to the README there. > Donation of ibm-functions/composer code to Apache OpenWhisk > --- > > Key: INCUBATOR-222 > URL: https://issues.apache.org/jira/browse/INCUBATOR-222 > Project: Incubator > Issue Type: New Feature >Reporter: Dave Grove >Priority: Major > Attachments: composer-master-8403e58.20181003.tar.bz2 > > > IBM is donating the implementation of Composer (previously available > [https://github.com/ibm-functions/composer] at under the Apache 2 license) to > the Apache OpenWhisk project. > This code base has 6 contributors. Five of them are IBM employees who have > Apache CLAs already on file (Olivier Tardieu, Rodric Rabbah, Dave Grove, > Kerry Chang, Nick Mitchell). The 6th contributor does not have an Apache CLA > on file, but his contribution was a trivial fix of a typo in the > docs/README.md file > ([https://github.com/ibm-functions/composer/commit/5ea5ac009f7ca6d4b9fd313dcfd507b3c6c36083).] > Attached is a tarball of the donated code at git commit hash > 8403e587ed73097b4794096e7afa7b166012f912. This code will be submitted as a > PR to the github repository github.com/apache/incubator-openwhisk-composer by > IBM. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-222) Donation of ibm-functions/composer code to Apache OpenWhisk
[ https://issues.apache.org/jira/browse/INCUBATOR-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16643532#comment-16643532 ] Dave Grove commented on INCUBATOR-222: -- Nick, Kerry, and Olivier are listed in [http://people.apache.org/unlistedclas.html.] They are not OpenWhisk committers and thus do not have apache ids. I updated the xml to indicate that. Next time the website rebuilds it should be there. The only missing CLA is from the 6th individual with a single, 1 character typo fix in the documentation. I believe we agreed that falls below the threshold of requiring any formal software grant. > Donation of ibm-functions/composer code to Apache OpenWhisk > --- > > Key: INCUBATOR-222 > URL: https://issues.apache.org/jira/browse/INCUBATOR-222 > Project: Incubator > Issue Type: New Feature >Reporter: Dave Grove >Priority: Major > Attachments: composer-master-8403e58.20181003.tar.bz2 > > > IBM is donating the implementation of Composer (previously available > [https://github.com/ibm-functions/composer] at under the Apache 2 license) to > the Apache OpenWhisk project. > This code base has 6 contributors. Five of them are IBM employees who have > Apache CLAs already on file (Olivier Tardieu, Rodric Rabbah, Dave Grove, > Kerry Chang, Nick Mitchell). The 6th contributor does not have an Apache CLA > on file, but his contribution was a trivial fix of a typo in the > docs/README.md file > ([https://github.com/ibm-functions/composer/commit/5ea5ac009f7ca6d4b9fd313dcfd507b3c6c36083).] > Attached is a tarball of the donated code at git commit hash > 8403e587ed73097b4794096e7afa7b166012f912. This code will be submitted as a > PR to the github repository github.com/apache/incubator-openwhisk-composer by > IBM. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-222) Donation of ibm-functions/composer code to Apache OpenWhisk
[ https://issues.apache.org/jira/browse/INCUBATOR-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16643472#comment-16643472 ] Bertrand Delacretaz commented on INCUBATOR-222: --- Website is fixed, the form is up at [http://incubator.apache.org/ip-clearance/openwhisk-composer.html] I see that you have set a date for "Check that all active committers have a signed CLA on record" but I didn't find all names in the roster at [https://whimsy.apache.org/roster/ppmc/openwhisk] - if I missed something, could you add the Apache IDs of those people after their names? Otherwise, if not all contributors to the donated software have an Apache iCLA on file, best is to file a Software Grant as per [https://www.apache.org/licenses/software-grant.txt] > Donation of ibm-functions/composer code to Apache OpenWhisk > --- > > Key: INCUBATOR-222 > URL: https://issues.apache.org/jira/browse/INCUBATOR-222 > Project: Incubator > Issue Type: New Feature >Reporter: Dave Grove >Priority: Major > Attachments: composer-master-8403e58.20181003.tar.bz2 > > > IBM is donating the implementation of Composer (previously available > [https://github.com/ibm-functions/composer] at under the Apache 2 license) to > the Apache OpenWhisk project. > This code base has 6 contributors. Five of them are IBM employees who have > Apache CLAs already on file (Olivier Tardieu, Rodric Rabbah, Dave Grove, > Kerry Chang, Nick Mitchell). The 6th contributor does not have an Apache CLA > on file, but his contribution was a trivial fix of a typo in the > docs/README.md file > ([https://github.com/ibm-functions/composer/commit/5ea5ac009f7ca6d4b9fd313dcfd507b3c6c36083).] > Attached is a tarball of the donated code at git commit hash > 8403e587ed73097b4794096e7afa7b166012f912. This code will be submitted as a > PR to the github repository github.com/apache/incubator-openwhisk-composer by > IBM. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
FYI, incubator website deployment is currently failing
Hi, I have asked on the bui...@apache.org list, https://lists.apache.org/thread.html/1d362ca3367c5bb23f46db893b320f03ff5f18d1d4c819ad8749bcaa@%3Cbuilds.apache.org%3E -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[jira] [Commented] (INCUBATOR-222) Donation of ibm-functions/composer code to Apache OpenWhisk
[ https://issues.apache.org/jira/browse/INCUBATOR-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16643209#comment-16643209 ] Bertrand Delacretaz commented on INCUBATOR-222: --- Thank you, https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/openwhisk-composer.xml is there indeed but the Incubator website deployment is currently failing, I have asked on the bui...@apache.org list about that, https://lists.apache.org/thread.html/1d362ca3367c5bb23f46db893b320f03ff5f18d1d4c819ad8749bcaa@%3Cbuilds.apache.org%3E > Donation of ibm-functions/composer code to Apache OpenWhisk > --- > > Key: INCUBATOR-222 > URL: https://issues.apache.org/jira/browse/INCUBATOR-222 > Project: Incubator > Issue Type: New Feature >Reporter: Dave Grove >Priority: Major > Attachments: composer-master-8403e58.20181003.tar.bz2 > > > IBM is donating the implementation of Composer (previously available > [https://github.com/ibm-functions/composer] at under the Apache 2 license) to > the Apache OpenWhisk project. > This code base has 6 contributors. Five of them are IBM employees who have > Apache CLAs already on file (Olivier Tardieu, Rodric Rabbah, Dave Grove, > Kerry Chang, Nick Mitchell). The 6th contributor does not have an Apache CLA > on file, but his contribution was a trivial fix of a typo in the > docs/README.md file > ([https://github.com/ibm-functions/composer/commit/5ea5ac009f7ca6d4b9fd313dcfd507b3c6c36083).] > Attached is a tarball of the donated code at git commit hash > 8403e587ed73097b4794096e7afa7b166012f912. This code will be submitted as a > PR to the github repository github.com/apache/incubator-openwhisk-composer by > IBM. > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
[VOTE][LAZY][IP CLEARANCE] Mojohaus Maven Utilities, for the NetBeans podling
Hi Incubator PMC members, The NetBeans podling would like to accept a donation of the Mojohaus Maven Utilities. See http://incubator.apache.org/ip-clearance/netbeans-mojohaus-utilities.html Please vote to approve this contribution. This majority vote is open for at least 72 hours and as usual lazy consensus applies. -Bertrand - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Signoff for PPMC reports for October 2018 due Tuesday
> On 9 Oct 2018, at 10:18, Justin Mclean wrote: > > Hi, > >> They're due today. Where's the panic? > > Um nowhere, but if the report has no sign off it's likely the podling needs > to report next month. I'd like to save the mentors and podling unnecessary > work. > > Recent board comments have cited a lack of mentor sign off as an issue for > the Incubator, so reminding podlings who may not sign a day or so before it > due will hopefully make that less of an issue. Yes, you're addressing an issue that's been treated differently in the past. There have been no such reminders to mentors (only to podlings to write a report), and a de-facto view that "If at least one mentor has signed off then mine doesn't really matter". I appreciate that you're trying to change that. What gets my back up is the Presumption of Guilt (which, as we've seen with Annotator, was based at least in part on incorrect data concerning past reporting). > Tone in email is notoriously hard to read right and is often taken the wrong > way. Why assume ill intent? I'm sorry if you took it that way, it certainly > wasn't intended as you said. I reread the text and don't see anything > confrontational in it. What in particular made you take it that way? (So I > can change what I send in the future.) No ill intent assumed. Let's look at the actual text: "Hi, Your mentors haven't yet signed off Octobers 2017 [1] report. Hopefully they see this and do so, but if not you may have to remind them. It is due Tuesday." OK, message to podling: "your mentors are failing you". It might or might not be merited, but it's hardly friendly to mentors! My own reaction: "Oh no, I've missed a deadline: I was sure it was this week!" OK it's only momentary before I've got the whole message, but that moment of panic puts my back up when it turns out it's not my fault. A simple: "Reminder to mentors: signoff is due by Tuesday if you haven't already" would have spared me that moment of panic and done the job. > I'm also curious to know if you hadn't seen the reminder would you have > remembered to sign off the reports by the due date? A fair question. In my case, yes this month and usually, but it might be helpful from time to time when my attention is elsewhere. -- Nick Kew - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Signoff for PPMC reports for October 2018 due Tuesday
Hi, > They're due today. Where's the panic? Um nowhere, but if the report has no sign off it's likely the podling needs to report next month. I'd like to save the mentors and podling unnecessary work. Recent board comments have cited a lack of mentor sign off as an issue for the Incubator, so reminding podlings who may not sign a day or so before it due will hopefully make that less of an issue. It's unfortunate that you are the only active mentor on those projects, I suggest you (or even better suggest it the PPMC to do) reach out to this list and ask for more mentors. > You pinged the projects yesterday. The tone of that ping - as if we > had done something wrong - felt to me rather confrontational. Tone in email is notoriously hard to read right and is often taken the wrong way. Why assume ill intent? I'm sorry if you took it that way, it certainly wasn't intended as you said. I reread the text and don't see anything confrontational in it. What in particular made you take it that way? (So I can change what I send in the future.) I'm also curious to know if you hadn't seen the reminder would you have remembered to sign off the reports by the due date? Thanks, Justin - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Signoff for PPMC reports for October 2018 due Tuesday
> On 9 Oct 2018, at 08:46, Justin Mclean wrote: > > Hi, > >> Podlings with no sign offs: >> Annotator >> Milagro >> ODF Toolkit >> Warble > > I’m yet to see a single sign off on any of these projects from their mentors. > Hopefully they are reading the list and will do so ASAP as they are due > today. I’ve pinged each project individually but had no response. They're due today. Where's the panic? You pinged the projects yesterday. The tone of that ping - as if we had done something wrong - felt to me rather confrontational. Enough to provoke an "I won't be bullied" reaction. I will sign off (and I still need to raise one podling separately), but surely it could be better accomplished by a non-confrontational reminder? > Assuming the mentors are missing ... might look fairer if the deadline had indeed passed and a reminder gone unheeded! -- Nick Kew - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Signoff for PPMC reports for October 2018 due Tuesday
Hi, > Podlings with no sign offs: > Annotator > Milagro > ODF Toolkit > Warble I’m yet to see a single sign off on any of these projects from their mentors. Hopefully they are reading the list and will do so ASAP as they are due today. I’ve pinged each project individually but had no response. Assuming the mentors are missing and we don’t get signoff, what should we do? Asking the podling to report again seems hard on them as they took the time to submit the report, but without sigh off can it be included in the board report? Thanks, Justin
