As well as the legal issue 'nightly builds haven't been through the strict review and license check process for ASF releases', and the engineering issue 'release off a nightly and your users will hate you', there's an ASF community one: ASF projects want to build a dev community as well as a user one —and encouraging users to jump to coding for/near a project is a way to do this.
1. Anyone on user@ lists are strongly encouraged to get on the dev@ lists, not just to contribute code but to contribute to discourse on project direction, comment on issues, review other code. 2. Its really good if someone builds/tests their downstream apps against pre-releases; catching problems early is the best way to fix them. 3. it really, really helps if the people doing build/tess of downstream apps have their own copy of the source code, in sync with the snapshots they use. That puts them in the place to start debugging any problems which surface, identify if it is a bug in their own code surfacing, vs a regression in the dependency —and, if it is the latter, they are in the position to start working on a fix * and test it in the exact environment where the problem arises* That's why you wan't to restrict these snapshots to developers: it's not "go away, user", it's "come and join the developers' > On 15 Aug 2016, at 09:08, Sean Owen <so...@cloudera.com> wrote: > > I believe Chris was being a bit facetious. > > The ASF guidance is right, that it's important people don't consume > non-blessed snapshot builds as like other releases. The intended > audience is developers and so the easiest default policy is to only > advertise the snapshots where only developers are likely to be > looking. > > That said, they're not secret or confidential, and while this probably > should go to dev@, it's not a sin to mention the name of snapshots on > user@, as long as these disclaimers are clear too. I'd rather a user > understand the full picture, than find the snapshots and not > understand any of the context. > > On Mon, Aug 15, 2016 at 2:11 AM, Jacek Laskowski <ja...@japila.pl> wrote: >> Hi Chris, >> >> With my ASF member hat on... >> >> Oh, come on, Chris. It's not "in violation of ASF policies" >> whatsoever. Policies are for ASF developers not for users. Honestly, I >> was surprised to read the note in Mark Hamstra's email. It's very >> restrictive but it says about what committers and PMCs should do not >> users: >> >> "Do not include any links on the project website that might encourage >> non-developers to download and use nightly builds, snapshots, release >> candidates, or any other similar package." >> >> Pozdrawiam, >> Jacek Laskowski >> ---- >> https://medium.com/@jaceklaskowski/ >> Mastering Apache Spark 2.0 http://bit.ly/mastering-apache-spark >> Follow me at https://twitter.com/jaceklaskowski > > --------------------------------------------------------------------- > To unsubscribe e-mail: dev-unsubscr...@spark.apache.org > >
