Mailing-List: contact dev-help@spark.apache.org; run by ezmlm
Precedence: bulk
To: dev@spark.apache.org
Subject: Re: Spark 2.0.0-preview artifacts still not available in Maven
From: Shane Curcuru <asf@shanecurcuru.org>
Message-ID: <c58b84d6-4118-ae56-f53d-811a33c5f130@shanecurcuru.org>
Date: Mon, 6 Jun 2016 08:34:44 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0)
 Gecko/20100101 Thunderbird/45.1.1
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 06 Jun 2016 12:34:54 -0000


On 2016-06-04 18:42 (-0400), Sean Owen <sowen@cloudera.com> wrote:
...
> The question is, can you just not fully release it? I don't think so,
> even as a matter of process, and don't see a good reason not to.
> 
> To Reynold's quote, I think that's suggesting that not all projects
> will release to a repo at all (e.g. OpenOffice?). I don't think it
> means you're free to not release some things to Maven, if that's
> appropriate and common for the type of project.
> 
> Regarding risk, remember that the audience for Maven artifacts are
> developers, not admins or end users. I understand that developers can
> temporarily change their build to use a different resolver if they
> care, but, why? (and, where would someone figure this out?)
> 
> Regardless: the 2.0.0-preview docs aren't published to go along with
> the source/binary releases. Those need be released to the project
> site, though probably under a different /preview/ path or something.
> If they are, is it weird that someone wouldn't find the release in the
> usual place in Maven then?
> 
> Given that the driver of this was concern over wide access to
> 2.0.0-preview, I think it's best to err on the side openness vs some
> theoretical problem.

The mere fact that there continues to be repeated pushback from PMC
members employed by DataBricks to such a reasonable and easy question to
answer and take action on for the benefit of all the project's users
raises red flags for me.

Immaterial of the actual motivations of individual PMC members, this
still gives the *appearance* that DataBricks as an organization
effectively exercises a more than healthy amount of control over how the
project operates in simple, day-to-day manners.

I strongly urge everyone participating in Apache Spark development to
read and take to heart this required policy for Apache projects:

  http://community.apache.org/projectIndependence

- Shane, speaking as an individual

(If I were speaking in other roles I hold, I wouldn't be as polite)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@spark.apache.org
For additional commands, e-mail: dev-help@spark.apache.org