I'm trying to commit to https://dist.apache.org/repos/dist and get the error below. Does this mean that my account does not have access to svn.
``` Adding toree svn: E195023: Commit failed (details follow): svn: E195023: Changing directory '/Users/ginobustelo/Dev/spark/apache-dist-dev/toree' is forbidden by the server svn: E175013: Access to '/repos/dist/!svn/txr/16406-dyo/dev/toree' forbidden ``` On Thu, Oct 6, 2016 at 9:34 AM Gino Bustelo <g...@bustelos.com> wrote: > So our intention was to put things somewhere for our mentors to help out > vetting what we will eventually put out for the vote. According to Hitesh > in this thread... "only one single source release which is going to be > voted upon". > > It is confusing where things need to go. I can't find documentation that > says that we need to upload to a specific place for voting. It may be > documented, but seriously... this process if full of confusion and poorly > documented (maybe overly documented) and it seems that not all projects do > the same thing. > > We need the following from our Mentors as it regards to "*GETTING READY > FOR THE VOTE*" > > 1. We followed the checklist here ( > http://incubator.apache.org/guides/releasemanagement.html#check-list) > and wanted to get a verification that we've done this right. You should be > able to verify this using the link above. > 2. Clear instructions of where we put all our candidate assets (FOR > THE VOTE) > 1. source package > 2. simple binary package > 3. pip release (we want to push this to pypi once accepted) > 4. maven artifacts > > Thanks, > Gino > > On Wed, Oct 5, 2016 at 4:42 PM Luciano Resende <luckbr1...@gmail.com> > wrote: > > This is not following the release guidelines. Did you check the release > script I sent [1] ? Also, I know you guys are subscribed to general@a.o, > it's good to check how some other podlings are handling releases just to > have a feeling of things to watch for. > > > - Don't pollute your official source repository with these artifacts, git > is for source code, the release candidate should be stored at > https://dist.apache.org/repos/dist/dev/ inside a toree/rc folder. Once > approved, it then gets moved to > https://dist.apache.org/repos/dist/release/ > inside a toree folder/r. See other projects how they work. > > - Maven artifacts if any should go into a staging repository at > repository.apache.org > > - If distributing scala binary artifacts, you might want to publish > artifacts for all supported scala versions _2.10 and _2.11 > > Other then these, a minor thing is that I would call the folder where the > archive gets installed as apache-toree instead of toree only. > > [1] https://github.com/apache/bahir/blob/master/dev/release-build.sh > > > On Wed, Oct 5, 2016 at 2:03 PM, Gino Bustelo <g...@bustelos.com> wrote: > > > We did a build and placed the source and bin package here ( > > https://github.com/apache/incubator-toree/tree/ > > 70c2b7d55ed3f42400844c2c5c311a70d5afbefe). > > If this is fine, we can then go and call for a vote. > > > > On Wed, Oct 5, 2016 at 12:34 PM Hitesh Shah <hit...@apache.org> wrote: > > > > > Additionally to clarify, there is only one single source release which > is > > > going to be voted upon. You can provide multiple binary artifacts for > > > convenience along with the main source release ( these will be looked > at > > > for correctness of the contents but not voted upon). The binary bits > > could > > > be different to match which version of spark they were built against. > All > > > of these artifacts (source tarball, binary tarball for spark 1.6, > binary > > > tarball for spark2 ) will need their own different license and notice > > files. > > > > > > — Hitesh > > > > > > > > > > On Oct 5, 2016, at 1:10 AM, Luciano Resende <luckbr1...@gmail.com> > > > wrote: > > > > > > > > On Tue, Oct 4, 2016 at 11:18 PM, Chip Senkbeil < > > chip.senkb...@gmail.com> > > > > wrote: > > > > > > > >> Sure. > > > >> > > > >> On Wed, Oct 5, 2016 at 12:46 AM Luciano Resende < > luckbr1...@gmail.com > > > > > > >> wrote: > > > >> > > > >>> Can we move this discussion to public ? > > > >>> > > > >>> On Tue, Oct 4, 2016 at 10:27 PM, Chip Senkbeil < > > > chip.senkb...@gmail.com> > > > >>> wrote: > > > >>> > > > >>> Was starting to read through this link: > > > >>> http://incubator.apache.org/guides/releasemanagement.html# > > > >> best-practice-incubator-release-vote > > > >>> > > > >>> A lot of the content has "TODO: Blah blah link" in place of actual > > > links > > > >>> to content, so was hoping to get a rough outline from a mentor, if > > > >>> possible. Since we're wanting to release for two different versions > > of > > > >>> Toree (one supporting Spark 1.x and the other for 2.x), I'm > assuming > > we > > > >>> need two separate vote threads with artifacts for each, right? > > > >>> > > > >>> > > > >>> > > > >>> > > > >> > > > > > > > > First, the most important thing for the first release will make sure > > that > > > > we try to clear all the legal files, so things like running RAT and > > also > > > > double checking the license/notice, signatures, etc will take most of > > the > > > > time. After that, we could borrow scripts from different projects to > > > > actually do the release, see this from Bahir as an example : > > > > https://github.com/apache/bahir/blob/master/dev/release-build.sh. As > > for > > > > voting, as long it's all one "release", even tough it might be > multiple > > > > packages/artifacts, you can combine the votes as one... > > > > > > > > > > > > > > > > -- > > > > Luciano Resende > > > > http://twitter.com/lresende1975 > > > > http://lresende.blogspot.com/ > > > > > > > > > > > > -- > Luciano Resende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/ > >
