Re: [VOTE] Release Apache SPOT 1.0-incubating

Its very hard to understand this release. How do I build it? How do I run RAT? John On Fri, Jul 28, 2017 at 11:50 AM Raymundo Panduro wrote: > Dear IPMC team, > > This is the vote for *Apache SPOT 1.0 (incubating) release*. This is > the first release of SPOT. > > > The

[VOTE] Apache Pulsar 1.19.0-incubating Release Candidate 0

This is the first release candidate for Apache Pulsar, version 1.19.0-incubating. Pulsar is a highly scalable, low latency messaging platform running on commodity hardware. It provides simple pub-sub semantics over topics, guaranteed at-least-once delivery of messages, automatic cursor management

Re: Urgent: Regarding Java package name change to org.apache.*

When Storm was incubating, our package names started with backtype.* and storm.* and it stayed that way through graduation and there was never any mention of a need to change. In fact, Storm only moved to org.apache.* with the 1.0 release in April 2016, about 1.5 years after graduation. There

Re: Urgent: Regarding Java package name change to org.apache.*

Which must's do you see greg? On Aug 3, 2017 1:09 PM, "Greg Trasuk" wrote: > Does this actually need to be policy? What’s the harm to the foundation > if a project continues to use a non-Apache package name, assuming that the > code was donated appropriately? > >

Re: Urgent: Regarding Java package name change to org.apache.*

Thanks all for your replies. We decided to bite the bullet and do it since we are half way already through our work. We will try to address backward incompatibilities via package shims, and special handling of configs. On a side note, I think for matters such as these Incubator should document

Re: Urgent: Regarding Java package name change to org.apache.*

Does this actually need to be policy? What’s the harm to the foundation if a project continues to use a non-Apache package name, assuming that the code was donated appropriately? Certainly, it should be a goal for all projects to use o.a.* package names, but if you look around the

Re: Urgent: Regarding Java package name change to org.apache.*

One caveat - if your packages are "com.theoldcompany.someproject" they should be renamed to "org.apache.someproject" before graduation. If you have "org.someproject" already or just "someproject" as your package names, that's not a naming issue so I don't see that ever blocking graduation. John

Re: Urgent: Regarding Java package name change to org.apache.*

> > > On Aug 3, 2017, at 12:25, Alex Harui wrote: > > OK, so to summarize a more refined recommendation: > > 1) package names with reverse domains MUST be renamed before graduation or > have an IPMC approved plan for renaming NetBeans uses org.netbeans, and the

Re: Urgent: Regarding Java package name change to org.apache.*

OK, so to summarize a more refined recommendation: 1) package names with reverse domains MUST be renamed before graduation or have an IPMC approved plan for renaming 2) Projects who expect that their future users outnumber current users are highly encouraged to rename packages 3) Other projects

Re: Urgent: Regarding Java package name change to org.apache.*

On 03/08/17 15:51, Julian Hyde wrote: It rarely comes down to the IPMC or the Board dictating how a project names its java classes (does anyone recall an instance?), so it’s mainly the project’s discretion. In my opinion, where the project is on its adoption curve is an important

Re: Code contribution to Apache MXNet with a BSD 3 clause

+general@incubator On Thu, Aug 3, 2017 at 8:22 AM Dominic Divakaruni < dominic.divakar...@gmail.com> wrote: > Legal-discuss@ to Bcc > > Thanks, John. The code will be part of Apache MXNet and our team will > commit to maintaining this. I will reach out to Apple, but I am not > optimistic they

Re: Code contribution to Apache MXNet with a BSD 3 clause

On Thu, Aug 3, 2017 at 11:26 AM Dominic Divakaruni < dominic.divakar...@gmail.com> wrote: > +general@incubator > > On Thu, Aug 3, 2017 at 8:22 AM Dominic Divakaruni < > dominic.divakar...@gmail.com> wrote: > >> Legal-discuss@ to Bcc >> >> Thanks, John. The code will be part of Apache MXNet and

Re: Urgent: Regarding Java package name change to org.apache.*

On Thu, Aug 3, 2017 at 8:42 AM Shane Curcuru wrote: > John D. Ament wrote on 8/2/17 9:13 PM: > > On Wed, Aug 2, 2017 at 8:54 PM Roman Shaposhnik > > wrote: > > > >> On Wed, Aug 2, 2017 at 5:40 PM, Abhishek Tiwari > wrote: > >>> Hi

Re: Urgent: Regarding Java package name change to org.apache.*

Alex Harui wrote on 8/3/17 10:37 AM: > From the peanut gallery: > > Does the PPMC get to decide what constitutes a "very good reason" or does > the IPMC and after graduation, the board? > > Flex has not changed its packages in the 5 years at Apache. We felt > backward compatibility was and is a

Re: Urgent: Regarding Java package name change to org.apache.*

It rarely comes down to the IPMC or the Board dictating how a project names its java classes (does anyone recall an instance?), so it’s mainly the project’s discretion. In my opinion, where the project is on its adoption curve is an important consideration. Most projects that enter the

Re: Urgent: Regarding Java package name change to org.apache.*

From the peanut gallery: Does the PPMC get to decide what constitutes a "very good reason" or does the IPMC and after graduation, the board? Flex has not changed its packages in the 5 years at Apache. We felt backward compatibility was and is a "very good reason". It was way more important to

Ping for Apache SPOT 1.0 (Incubating) Voting Thread

Hi IPMC members... Just Wondering if you saw the voting email of Apache SPOT 1.0 (Incubating) Release on this thread: https://lists.apache.org/thread.html/32d7c93fe66cc256ed12a5b8f91b57b1d0d659b9012c8f4f13c11191@%3Cgeneral.incubator.apache.org%3E Any comments or feedback regarding the release

Re: Urgent: Regarding Java package name change to org.apache.*

John D. Ament wrote on 8/2/17 9:13 PM: > On Wed, Aug 2, 2017 at 8:54 PM Roman Shaposhnik > wrote: > >> On Wed, Aug 2, 2017 at 5:40 PM, Abhishek Tiwari wrote: >>> Hi all, >>> >>> In regards to the recently incubated project - Gobblin, we were wondering >>>

Re: [IP CLEARANCE] Arrow Plasma Object Store

On Wed, Aug 2, 2017 at 5:50 PM Wes McKinney wrote: > We have the git history from the project of origin; the entire Ray > project (Apache 2.0) git history is commingled with the Plasma Object > Store code, so it would be possible with some effort to extract only > the

Re: Urgent: Regarding Java package name change to org.apache.*

On Thu, Aug 3, 2017 at 2:42 AM, Andy Seaborne wrote: > On 03/08/17 05:13, Roman Shaposhnik wrote: > >> On Wed, Aug 2, 2017 at 6:13 PM, John D. Ament >> wrote: >> >>> On Wed, Aug 2, 2017 at 8:54 PM Roman Shaposhnik >>> wrote: >>> >>>

Re: Urgent: Regarding Java package name change to org.apache.*

On 03/08/17 05:13, Roman Shaposhnik wrote: On Wed, Aug 2, 2017 at 6:13 PM, John D. Ament wrote: On Wed, Aug 2, 2017 at 8:54 PM Roman Shaposhnik wrote: On Wed, Aug 2, 2017 at 5:40 PM, Abhishek Tiwari wrote: Hi all, In regards