[jira] [Commented] (INCUBATOR-231) Cleanup Git-generated Incubator website

[ https://issues.apache.org/jira/browse/INCUBATOR-231?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16807414#comment-16807414 ] Dave Fisher commented on INCUBATOR-231: --- I've split up the process as so and plan to put it into

[jira] [Commented] (INCUBATOR-234) Incubator Cookbook

[ https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16807412#comment-16807412 ] Dave Fisher commented on INCUBATOR-234: --- In general I like the idea. Some thoughts: * We should

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

Sure, policy is "Release votes SHOULD remain open for at least 72 hours." The reasons for the SHOULD have been outlined already and should be well known to anyone who is in a podling since it's core to everything we do. I would have hoped champions would have explained this before even making

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

TL;DR; I suppose is that in the case of 3 mentor/IPMC already +1 a release we can switch to a "review after commit" style notification so that folks eager to double check can, but not to burden the project or IPMC with a secondary step. This not only reduces bookkeeping but encourages each

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

one part that may not be obvious is the bookkeeping overhead on projects with many repositories and also the load on the IPMC. For example in zipkin, we are migrating several repositories. You can imagine a surge of release verification votes which if people here want to take the burden of

Re: Incubator (git) website published

All good now. New error state to add to the build - SVN connection reset. Anyway - I am splitting out the clutch analysis from normal builds tomorrow after I add that new protection. Regards, Dave > On Apr 1, 2019, at 7:05 PM, Dave Fisher wrote: > > The site is messed up. Checking. > > Sent

Re: Incubator (git) website published

The site is messed up. Checking. Sent from my iPhone > On Apr 1, 2019, at 6:39 PM, Apache Jenkins Server > wrote: > > The Apache Jenkins build system has built Incubator Site (build #887) > > Status: Successful > > Check console output at https://builds.apache.org/job/Incubator%20Site/887/

Re: List of Projects that went straight to Top Level Projects

On Mon, Apr 1, 2019 at 4:52 PM Dave Fisher wrote: > > > > > Pre-incubator: > > Ant, > Jakarta > > Avalon, > Jakarta > > DB, > Jakarta Thanks for the corrections! > > HTTP Server, Jakarta, Perl, PHP, TCL, XML > > > > Spun out from elsewhere: > > Archiva, > Maven ? Generally this information

Re: Setting up Tuweni

Thanks Dave! And thanks for updating in SVN too. Kenn On Sun, Mar 31, 2019 at 9:58 AM Dave Fisher wrote: > Hi - > > > On Mar 30, 2019, at 11:41 PM, Kenneth Knowles wrote: > > > > Hi Dave, > > > > What should a podling put here? I notice a few things: > > > > - you changed the start date from

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

> On Apr 1, 2019, at 3:42 PM, Justin Mclean wrote: > > Hi, > > When Ross wrote “72hrs or 3 +1” I think he was using shorthand, not >> intending to rewrite foundation policy. >> > > Sure I thought so as well, but other newer people here might not of been > aware of it. The only exception

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

Hi, When Ross wrote “72hrs or 3 +1” I think he was using shorthand, not > intending to rewrite foundation policy. > Sure I thought so as well, but other newer people here might not of been aware of it. Thanks, Justin >

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

Per my reading http://www.apache.org/legal/release-policy.html#release-approval it’s not OK to stop when you reach 3 +1 votes. Because it’s not 3 +1s absolute, it’s 3 more +1s than -1s. So, you have to have a fixed, reasonable

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

Hi, > 72 hours is a guide. As long as your project community is agreeable you can > say "72hrs or 3 +1”. 72 hours is a guide, but recommended, as it gives a chance for all PPMC members to have a look at the release. They may be in different timezone or have day jobs or other things going on,

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

Hi - > On Apr 1, 2019, at 2:51 PM, Justin Mclean wrote: > > Hi, > > I'd also like to see those mentors / IPMC members vote with more than just a > +1 and provide a list of what they checked. If they could use something like > this all the better [1]. > > I wouldn’t be for removing the

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

Hi, I'd also like to see those mentors / IPMC members vote with more than just a +1 and provide a list of what they checked. If they could use something like this all the better [1]. I wouldn’t be for removing the second step of letting the IPMC look at it, reasonably often serious issues are

Re: List of Projects that went straight to Top Level Projects

On Mon, Apr 1, 2019 at 1:08 PM Lars Francke wrote: > > Straight to TLP: > > Bahir, DRAT, Kibble, Orc, Serf, STeVe, Whimsy, Zest > > ORC was spun out of Hive as far as I remember. In that sense Bahir was also spun out of Spark, although it added a lot of things after that. -- Marcelo

Re: List of Projects that went straight to Top Level Projects

Hi Sam Thanks for the rough cut list as it gives me more of the context so I can see where to select projects from for comparison. My thought is to do some analysis with Kibble as I did with my previous paper (summary version is here https://s.apache.org/rguz and full version is here

Re: [Cancelled] [VOTE] Heron Release 0.20.1-incubating (Release Candidate 2)

Let's cancel this vote for now and go back to dev mailing list to discuss more. On Mon, Apr 1, 2019 at 1:53 PM Ning Wang wrote: > Ok. Thanks! > > On Mon, Apr 1, 2019 at 11:55 AM Dave Fisher wrote: > >> -1 - we need to carefully discuss this on dev@heron. >> >> I seem to be the only Heron

Re: [VOTE] Heron Release 0.20.1-incubating (Release Candidate 2)

Ok. Thanks! On Mon, Apr 1, 2019 at 11:55 AM Dave Fisher wrote: > -1 - we need to carefully discuss this on dev@heron. > > I seem to be the only Heron Mentor paying attention. We need more than me! > > (1) I cannot really follow this email > (2) We still need to discuss the docker hub image. (I

Re: List of Projects that went straight to Top Level Projects

Hi - I took Greg’s challenge and did research on the roots. Mailing List Archives are important resources! > On Apr 1, 2019, at 12:21 PM, Sam Ruby wrote: > > On Mon, Apr 1, 2019 at 2:28 PM Greg Stein wrote: >> >> On Mon, Apr 1, 2019 at 1:11 PM Julian Hyde wrote: >> >>> Most of the

Re: List of Projects that went straight to Top Level Projects

Wow - thanks everyone for the feedback. And Sam this is great. Thanks Sharan On 2019/04/01 00:08:47, Sam Ruby wrote: > In March, I wrote a script to find establishment resolutions, and to > scan those resolutions for the word 'incubator': > >

Re: List of Projects that went straight to Top Level Projects

> On Apr 1, 2019, at 11:19 AM, Greg Stein wrote: > > I would disagree with your latter statement; they went to TLP based > on oversight, rather than on userbase/impact. I didn’t mean to suggest that we treated them differently because they had a large user base. By “important” I meant

Re: List of Projects that went straight to Top Level Projects

> > > Straight to TLP: > Bahir, DRAT, Kibble, Orc, Serf, STeVe, Whimsy, Zest > ORC was spun out of Hive as far as I remember.

Re: [VOTE] Release Apache Netbeans 11.0 (incubating) [vote candidate 4]

I understand the frustration here. I'd suggest that with a large project like this [1], that has had many cases where the release would appear to be in violation of standards, that the [DISCUSS] and [VOTE] threads explicitly call out the issues, the RAT exclusions, and a small discussion of

Re: List of Projects that went straight to Top Level Projects

On Mon, Apr 1, 2019 at 2:28 PM Greg Stein wrote: > > On Mon, Apr 1, 2019 at 1:11 PM Julian Hyde wrote: > > > Most of the projects mentioned so far have been “internal” > > > Only because all the umbrella-derived projects haven't been mentioned. Most > of that "spin out to a TLP" was done a

Re: [VOTE] Heron Release 0.20.1-incubating (Release Candidate 2)

-1 - we need to carefully discuss this on dev@heron. I seem to be the only Heron Mentor paying attention. We need more than me! (1) I cannot really follow this email (2) We still need to discuss the docker hub image. (I suggest that this be unofficial for this round.) (3) The binaries on

Re: List of Projects that went straight to Top Level Projects

On Mon, Apr 1, 2019 at 1:11 PM Julian Hyde wrote: > Most of the projects mentioned so far have been “internal” Only because all the umbrella-derived projects haven't been mentioned. Most of that "spin out to a TLP" was done a decade ago, so they've been omitted from discussion. > - code

[VOTE] Heron Release 0.20.1-incubating (Release Candidate 2)

*Hello, dear IPMC members,This is a call for a vote to release Apache Heron (Incubating) version 0.20.1.The Apache Heron Community has voted to make the Heron Release 0.20.1-incubating release. We kindly request the Incubator PMC members review and vote on this incubator release.The dev voting

Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2

Hi - > On Apr 1, 2019, at 10:54 AM, Marcelo Vanzin > wrote: > > On Fri, Mar 29, 2019 at 10:41 PM Felix Cheung wrote: >> I switched to another environment, found out I needed to manually pip >> install configparser just to build (skipTest) > > There are probably things that could be better

Re: List of Projects that went straight to Top Level Projects

Most of the projects mentioned so far have been “internal” - code developed to help run the ASF. “External” projects also go straight-to-TLP and are more important because they have many more users and greater impact on the world. A couple of examples I am aware of have been “refactorings”,

[VOTE][RESULT] Release Apache Livy 0.6.0 (incubating) based on RC2

Thanks for everybody who voted on the podling and general threads. Vote passes with the following votes (* = binding): - Justin Mclean (*) - Luciano Resende (*) - Felix Cheung (*) Vote thread:

Re: [VOTE] Release Apache Livy 0.6.0 (incubating) based on RC2

On Fri, Mar 29, 2019 at 10:41 PM Felix Cheung wrote: > I switched to another environment, found out I needed to manually pip > install configparser just to build (skipTest) There are probably things that could be better documented. Or maybe could be handled better by the build scripts. But

Re: [VOTE][RESULT] release Apache OpenWhisk Package Alarm, Package Cloudant, and Package Kafka 2.0.0 (incubating)

Thanks to all who participated in this vote. It has passed with 4 +1 (binding) votes (Matt Sicker, Justin Mclean, Krzysztof Sobkowiak, Bertrand Delacretaz) and no other votes. We will proceed with the 2.0.0 release of these three components. Thanks also to Justin and Bertrand for pointing out

Re: [VOTE] release Apache OpenWhisk Package Alarm, Package Cloudant, and Package Kafka 2.0.0 (incubating)

Hey Dave, I believe Jason Peterson did an emergency patch this weekend for the alarms provider. We should use hash 92b0ac8b0b006ef6c9395271fd17afa6c83c14b1 instead for alarms for the release. Other than that +1. Regards, James Dubee -"David P Grove" wrote: - To: Incubator From:

Vote started on graduation of Apache PLC4X (incubating) pooling to TLP on d...@plc4x.apache.org

Hi all, I just wanted to inform you all, that on our dev-list we have just started a VOTE thread for proposing Apache PLC4X (incubating) for graduation to TLP. Here’s a link to the vote thread:

[jira] [Commented] (INCUBATOR-234) Incubator Cookbook

[ https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806744#comment-16806744 ] Bertrand Delacretaz commented on INCUBATOR-234: --- Once we're happy with the contents of

Re: [VOTE] release Apache OpenWhisk Package Alarm, Package Cloudant, and Package Kafka 2.0.0 (incubating)

Hi, +1 for the releases of the 3 packages listed below. Checked signatures, digests and build with "gradle distDocker". As things to fix for next time, which do not block this release IMO, I see several source files using a short-form Apache license header: // Licensed to the Apache Software

Re: List of Projects that went straight to Top Level Projects

Hi, On Sun, Mar 31, 2019 at 1:58 PM Geertjan Wielenga wrote: > ...I don’t > think it’s common to skip incubation and I’m sure a lot would not be > learned by skipping it The rationale for the very few projects that have gone direct to TLP is that there was nothing to learn. A good example

[jira] [Updated] (INCUBATOR-234) Incubator Cookbook

[ https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated INCUBATOR-234: -- Description: As discussed at [1] the goal is to create a single page

[jira] [Updated] (INCUBATOR-234) Incubator Cookbook

[ https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated INCUBATOR-234: -- Description: As discussed at [1] the goal is to create a single page

[jira] [Updated] (INCUBATOR-234) Incubator Cookbook

[ https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bertrand Delacretaz updated INCUBATOR-234: -- Description: As discussed at [1] the goal is to create a single page

Re: [VOTE] Release Apache Netbeans 11.0 (incubating) [vote candidate 4]

OK, that’s fair. And possibly an indicator that when a podling is large, and there are many moving parts, it would be best to, when needed, assume the podling is doing the best they can under complex circumstances, rather than that the podling is not following guidelines, ignoring advice, etc. Gj

[jira] [Commented] (INCUBATOR-234) Incubator Cookbook

[ https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806609#comment-16806609 ] Bertrand Delacretaz commented on INCUBATOR-234: --- [~isa...@apache.org] I have reworked

Re: [VOTE] Release Apache Netbeans 11.0 (incubating) [vote candidate 4]

One also has to see that NetBeans is an exceptionally big and complex podling! For most other projects the existing process works really fine. LieGrue, strub > Am 01.04.2019 um 11:35 schrieb Geertjan Wielenga > : > > On Mon, Apr 1, 2019 at 11:27 AM Mark Struberg > wrote: > >> We have also

Re: [ANNOUNCE] Release Apache ECharts (incubating) 4.2.1

Sorry. I've fixed that now. Zhang Wenli http://zhangwenli.com sebb 于2019年4月1日周一 下午4:02写道： > On Mon, 1 Apr 2019 at 07:58, Ovilia wrote: > > > > Thanks Craig. > > > > I've updated the download page. Please help check again. > > Thank you! > > The page says "please check the md5sum and ...". >

Re: [VOTE] Release Apache Netbeans 11.0 (incubating) [vote candidate 4]

On Mon, Apr 1, 2019 at 11:27 AM Mark Struberg wrote: > We have also previously already checked those files and also have the > sources at hand afaict. > So they should be perfectly fine - as they have been in older NB releases > (where we had the question as well). > I think this is the

Re: [VOTE] Release Apache Netbeans 11.0 (incubating) [vote candidate 4]

Indeed, and thanks again for jumping in and pushing the review forward! NB is such a huge codebase that it is really hard to do a full cycle review. So any attempt is really appreciated! LieGrue, strub > Am 31.03.2019 um 10:04 schrieb Justin Mclean : > > Hi, > >> It has never been a practice

Re: [VOTE] Release Apache Netbeans 11.0 (incubating) [vote candidate 4]

I started my review on the IPMC list but did also test-drive NB11 for a few days because I had functional issues (quirks with missing JavaFX on Fedora). Thus I only casted my +1 only after the vote got moved to general@a.o. Trying to move faster in the future. txs and LieGrue, strub > Am

Re: [VOTE] Release Apache Netbeans 11.0 (incubating) [vote candidate 4]

We have also previously already checked those files and also have the sources at hand afaict. So they should be perfectly fine - as they have been in older NB releases (where we had the question as well). LieGrue, strub > Am 30.03.2019 um 07:23 schrieb Wade Chandler : > > On Fri, Mar 29,

[jira] [Commented] (INCUBATOR-234) Incubator Cookbook

[ https://issues.apache.org/jira/browse/INCUBATOR-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16806538#comment-16806538 ] Bertrand Delacretaz commented on INCUBATOR-234: --- In

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

Hi, On Mon, Apr 1, 2019 at 5:30 AM Craig Russell wrote: > > ...This is a proposal to recommend that all Mentors SHOULD vote on podling > releases > prior to sending the release for a vote to the IPMC There's already something about this in the (work in progress)

Re: Voting on releases with serious unaddressed issues

On Mon, Apr 1, 2019 at 10:26 AM Bertrand Delacretaz < bdelacre...@codeconsult.ch> wrote: > Hi, > > On Sat, Mar 30, 2019 at 8:01 PM Geertjan Wielenga > wrote: > >...what comes closest to what > > you're looking for is the Rat exclusions file... > > > >

Re: Voting on releases with serious unaddressed issues

Hi, On Sat, Mar 30, 2019 at 3:34 AM Justin Mclean wrote: > ...What do other IPMC members think?... I'm coming late to this discussion but I think it would have been better to point to specific issues so people can reply in a more concrete way. Generally, I think it can be ok for podling

Re: Voting on releases with serious unaddressed issues

Hi, On Sat, Mar 30, 2019 at 8:01 PM Geertjan Wielenga wrote: >...what comes closest to what > you're looking for is the Rat exclusions file... > https://github.com/apache/incubator-netbeans/blob/master/nbbuild/rat-exclusions.txt ... And note that that file is mentioned in the

Re: [ANNOUNCE] Release Apache ECharts (incubating) 4.2.1

On Mon, 1 Apr 2019 at 07:58, Ovilia wrote: > > Thanks Craig. > > I've updated the download page. Please help check again. > Thank you! The page says "please check the md5sum and ...". However MD5 checksums are deprecated and anyway the podling does not use them. The text and the link need to be

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

On Mon, 1 Apr 2019 at 05:15, Ross Gardler wrote: > > Just like so many things, this is how it used to be. In fact, back in the day > the only time the IPMC was asked to vote was when there were not enough > mentor votes. > > If you look at all the podlinga I've mentored I have only ever asked

Re: [DISCUSS] Mentors SHOULD vote on podling releases prior to asking IPMC to vote

72 hours is a guide. As long as your project community is agreeable you can say "72hrs or 3 +1". Get Outlook for Android From: Adrian Cole Sent: Sunday, March 31, 2019 9:26:08 PM To: general@incubator.apache.org Subject: Re: [DISCUSS]

Re: [ANNOUNCE] Release Apache ECharts (incubating) 4.2.1

Thanks Craig. I've updated the download page. Please help check again. Thank you! Zhang Wenli http://zhangwenli.com Craig Russell 于2019年3月30日周六 下午1:06写道： > The page http://echarts.apache.org/download.html is very close, but: > > The Source link is fine. > The Signature link and SHA512 link