spark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sean Owen <so...@cloudera.com>
Subject Re: Foundation policy on releases and Spark nightly builds
Date Sat, 11 Jul 2015 15:53:17 GMT
>From a developer perspective, I also find it surprising to hear that
nightly builds should be hidden from non-developer end users. In an
age of Github, what on earth is the problem with distributing the
content of master? However I do understand why this exists.

To the extent the ASF provides any value, it is at least a legal
framework for defining what it means for you and I to give software to
a bunch of other people. Software artifacts released according to an
ASF process becomes something the ASF can take responsibility for as
an entity. Nightly builds are not. It might matter to the committers
if, say, somebody commits a serious data loss bug. You don't want to
be on the hook individually for putting that into end-user hands.

More practically, I think this exists to prevent some projects from
lazily depending on unofficial nightly builds as pseudo-releases for
long periods of time. End users may come to perceive them as official
sanctioned releases when they aren't. That's not the case here of
course.

I think nightlies aren't for end-users anyway, and I think developers
who care would know how to get nightlies anyway. There's little cost
to moving this info to the wiki, so I'd do it.

On Sat, Jul 11, 2015 at 4:29 PM, Reynold Xin <rxin@databricks.com> wrote:
> I don't get this rule. It is arbitrary, and does not seem like something
> that should be enforced at the foundation level. By this reasoning, are we
> not allowed to list "source code management" on the project public page as
> well?
>
> The download page clearly states the nightly builds are "bleeding-edge".
>
> Note that technically we did not violate any rules, since the ones we showed
> were not "nightly builds" by the foundation's definition: "Nightly Builds
> are simply built from the Subversion trunk, usually once a day.". Spark
> nightly artifacts were built from git, not svn trunk. :)  (joking).
>
>
>
> On Sat, Jul 11, 2015 at 7:44 AM, Sean Busbey <busbey@cloudera.com> wrote:
>>
>> That would be great.
>>
>> A note on that page that it's meant for the use of folks working on the
>> project with a link to your "get involved" howto would be nice additional
>> context.
>>
>> --
>> Sean
>>
>> On Jul 11, 2015 6:18 AM, "Sean Owen" <sowen@cloudera.com> wrote:
>>>
>>> I suggest we move this info to the developer wiki, to keep it out from
>>> the place all and users look for downloads. What do you think about
>>> that Sean B?
>>>
>>> On Sat, Jul 11, 2015 at 5:34 AM, Sean Busbey <busbey@cloudera.com> wrote:
>>> > Hi Folks!
>>> >
>>> > I noticed that Spark website's download page lists nightly builds and
>>> > instructions for accessing SNAPSHOT maven artifacts[1]. The ASF policy
>>> > on
>>> > releases expressly forbids this kind of publishing outside of the
>>> > dev@spark
>>> > community[2].
>>> >
>>> > If you'd like to discuss having the policy updated (including expanding
>>> > the
>>> > definition of "in the development community"), please contribute to the
>>> > discussion on general@incubator[3] after removing the offending items.
>>> >
>>> > [1]:
>>> > http://spark.apache.org/downloads.html#nightly-packages-and-artifacts
>>> > [2]: http://www.apache.org/dev/release.html#what
>>> > [3]: http://s.apache.org/XFP
>>> >
>>> > --
>>> > Sean
>
>

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


Mime
View raw message