On 7 September 2014 21:31, Jacques Nadeau <jacq...@apache.org> wrote:

> As I understand the release guidelines, one is not allowed to put something
> on dist.apache.org until after a release vote by the Incubator PMC
> approves
> that release:
>
> "Only formally-approved releases may be distributed from the main
> directories" [1]
>
> For this candidate, as with our last two releases, we followed this piece
> of information:
>
> "It is traditional that release managers use their Apache home space to
> make available release candidates. " [1]
>
I do agree with your POW. Important is:
- The release bits are in SVN
- The PMC vote is based on the same location presented for IPMC vote.

dist.a.o is for approved releases, and I have found no "rule" stating a
mandatory location to use for the vote itself.


rgds
jan i.

>
> To date, we only push to dist.apache.org once we have received approval
> here.  Can you point me to the guidelines that lead you to believe that
> this must be staged on dist.apache.org?
>
> Thanks,
> Jacques
>
> [1]
>
> http://incubator.apache.org/guides/releasemanagement.html#best-practice-incubator-release-vote
>
>
>
>
>
>
>
> On Sun, Sep 7, 2014 at 11:48 AM, John D. Ament <john.d.am...@gmail.com>
> wrote:
>
> > Sorry, I have to vote -1
> >
> > The release is not staged in the proper place (e.g.
> > https://dist.apache.org/repos/dist/dev/incubator/ )
> >
> > If this gets moved, I can vote +1
> >
> > On Sun, Sep 7, 2014 at 11:29 AM, Jacques Nadeau <jacq...@apache.org>
> > wrote:
> >
> > > Hi John,
> > >
> > > Thanks for the feedback.  I'd like to respond to each of your concerns:
> > >
> > > >>Your NOTICE file is missing MIT license.
> > >
> > > The notice file states:  "Please see LICENSE for additional copyright
> and
> > > licensing information." The LICENSE file contains the MIT license.
> > >
> > > >>Your source file includes binaries in the sample-data directory.
> > >
> > > These are small sample data files that are used to do various unit
> tests.
> > >  They have been approved on both of our previous releases because of
> > their
> > > small size (<24k combined) and the fact that they are not source code.
> > >  These are raw data files that happen to be binary in nature but are
> for
> > > all purposes the same as example json files we include for testing
> > > purposes.
> > >
> > > >> Ideally, your directory name should match the release version
> > (0.5.0.rc2
> > > vs 0.5.0)
> > >
> > > The name of the release candidate directory is due to the nature of the
> > > Apache voting process.  Each time we have a release candidate in the
> > > community, we hold a vote.  We always maintain past release candidates
> so
> > > that we can refer back to them.  All artifacts in the release candidate
> > > hold the release/public names and will ultimately be hosted on the
> Apache
> > > distribution servers at the appropriately named release directory.  For
> > > historical perspective on this, see the following that has been our
> > > strategy thus far:
> > >
> > > our m1 release:
> > > http://people.apache.org/~jacques/apache-drill-1.0.0-m1 (fail)
> > > http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc2 (fail)
> > > http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc3 (fail)
> > > http://people.apache.org/~jacques/apache-drill-1.0.0-m1.rc4 (approved)
> > -->
> > > and distributed as
> > >
> >
> https://archive.apache.org/dist/incubator/drill/drill-1.0.0-m1-incubating/
> > >
> > > our 0.4.0 release:
> > > http://people.apache.org/~jacques/apache-drill-0.4.0.rc0 (fail)
> > > http://people.apache.org/~jacques/apache-drill-0.4.0.rc1 (approved)
> -->
> > > distributed as
> > >
> https://archive.apache.org/dist/incubator/drill/drill-0.4.0-incubating/
> > >
> > > our 0.5.0 release:
> > > http://people.apache.org/~jacques/apache-drill-0.5.0.rc0 (fail)
> > > http://people.apache.org/~jacques/apache-drill-0.5.0.rc1 (fail)
> > > http://people.apache.org/~jacques/apache-drill-0.5.0.rc2 (pending)
> > >
> > >
> > > As you can see, the rc numbers are only used during the voting process.
> > >  Once we get approval from the incubator, we drop the rc so that
> external
> > > consumers aren't confused by failed released candidates.
> > >
> > > Hopefully this satisfies your concerns and you can vote +1 for our
> > release.
> > >
> > > thanks again for your feedback,
> > > Jacques
> > >
> > >
> > > On Sun, Sep 7, 2014 at 5:09 AM, John D. Ament <john.d.am...@gmail.com>
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > Your NOTICE file is missing MIT license.
> > > > Your source file includes binaries in the sample-data directory.
> > > > Ideally, your directory name should match the release version
> > (0.5.0.rc2
> > > vs
> > > > 0.5.0)
> > > >
> > > > John
> > > >
> > > >
> > > > On Sat, Sep 6, 2014 at 11:36 PM, Jacques Nadeau <jacq...@apache.org>
> > > > wrote:
> > > >
> > > > > It is my pleasure to present the Apache Drill 0.5.0-incubating
> > release
> > > to
> > > > > the general incubator list for a vote.  This set of artifacts have
> > > passed
> > > > > our drill-dev vote and incorporate a number of improvements with
> over
> > > 100
> > > > > JIRAs closed in the last month.
> > > > >
> > > > > As part of this release, we looked to address the feedback in our
> > > > previous
> > > > > release from the general list.  This included enhancing our license
> > and
> > > > > notice files as well as clearly delineating binary dependencies
> that
> > > are
> > > > > distributed as part of our convenience binary.
> > > > >
> > > > > The vote thread can be found here:
> > > > >
> > > > >
> > > >
> > >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-drill-dev/201409.mbox/%3CCAKa9qD=L9KLQbNe2BKXKn=H34r0=3boobbd_3uhzeojc9k8...@mail.gmail.com%3E
> > > > >
> > > > > The vote passed with:
> > > > > +5 binding
> > > > > +6 non-binding
> > > > >
> > > > > You can find the artifacts for the release at this location:
> > > > > http://people.apache.org/~jacques/apache-drill-0.5.0.rc2/
> > > > >
> > > > > I look forward to your feedback.
> > > > >
> > > > > Thanks,
> > > > > Jacques
> > > > >
> > > >
> > >
> >
>

Reply via email to