This is done, and yes I believe that resolves the issue as far all here know.
http://spark.apache.org/downloads.html
-
https://cwiki.apache.org/confluence/display/SPARK/Useful+Developer+Tools#UsefulDeveloperTools-NightlyBuilds
On Sun, Jul 19, 2015 at 5:26 PM, Patrick Wendell pwend...@gmail.com
Thanks, Sean.
On Mon, Jul 20, 2015 at 12:22 AM, Sean Owen so...@cloudera.com wrote:
This is done, and yes I believe that resolves the issue as far all here
know.
http://spark.apache.org/downloads.html
-
I am going to make an edit to the download page on the web site to
start, as that much seems uncontroversial. Proposed change:
Reorder sections to put developer-oriented sections at the bottom,
including the info on nightly builds:
Download Spark
Link with Spark
All Releases
Spark Source
Sean B.,
Thank you for giving a thorough reply. I will work with Sean O. and
see what we can change to make us more in line with the stated policy.
I did some research and it appears that some time between October [1]
and December [2] 2006, this page was modified to include stricter
policy
Hey Sean,
One other thing I'd be okay doing is moving the main text about
nightly builds to the wiki and just have header called Nightly
builds at the end of the downloads page that says For developers,
Spark maintains nightly builds. More information is available on the
[Spark developer
To move this forward, I think one of two things needs to happen:
1. Move this guidance to the wiki. Seems that people gathered here
believe that resolves the issue. Done.
2. Put disclaimers on the current downloads page. This may resolve the
issue, but then we bring it up on the right mailing
Responses inline, with some liberties on ordering.
On Sun, Jul 12, 2015 at 10:32 PM, Patrick Wendell pwend...@gmail.com
wrote:
Hey Sean B,
Would you mind outlining for me how we go about changing this policy -
I think it's outdated and doesn't make much sense. Ideally I'd like to
propose a
Point well taken. Allow me to walk back a little and move us in a more
productive direction.
I can personally empathize with the desire to have nightly builds. I'm a
passionate advocate for tight feedback cycles between a project and its
downstream users. I am personally involved in several
Please keep in mind that you are also ASF people, as is the entire Spark
community (users and all)[4]. Phrasing things in terms of us and them by
drawing a distinction on [they] get in a fight on our mailing list is not
helpful.
whineBut they started it!/whine
A bit more seriously, my
Please note that when the policy refers to developers it means the
developers of the project at hand, that is participants on the dev@spark
mailing list.
As I stated in my original email, you're welcome to continue the discussion
on the policy including the definition of developers on
(This sounds pretty good to me. Mark it developers-only, not formally
tested by the community, etc.)
On Sun, Jul 12, 2015 at 7:50 PM, Patrick Wendell pwend...@gmail.com wrote:
Hey Sean B.,
Thanks for bringing this to our attention. I think putting them on the
developer wiki would
Thanks Sean O. I was thinking something like NOTE: Nightly builds are
meant for development and testing purposes. They do not go through
Apache's release auditing process and are not official releases.
- Patrick
On Sun, Jul 12, 2015 at 3:39 PM, Sean Owen so...@cloudera.com wrote:
(This sounds
Hey Sean B.,
Thanks for bringing this to our attention. I think putting them on the
developer wiki would substantially decrease visibility in a way that
is not beneficial to the project - this feature was specifically
requested by developers from other projects that integrate with Spark.
If the
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
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
15 matches
Mail list logo
