[RESULT] [VOTE] Apache Drill 0.5.0-incubating release

[Jacques Nadeau <ja...@apache.org>]

Thanks for everybody's input.  The release vote passes with three +1's and
no -1's.

The votes were from:
Ted +1
Jan +1
John +1

Note that sebb also has a +1 on this thread but it is about improving the
documentation, not the Drill release artifacts.

Thanks to everyone.  We'll move forward with propagating to Apache mirrors.

Jacques


On Tue, Sep 9, 2014 at 5:50 AM, sebb <se...@gmail.com> wrote:

> On 9 September 2014 13:24, jan i <ja...@apache.org> wrote:
> > On 9 September 2014 06:51, Ted Dunning <te...@gmail.com> wrote:
> >
> >> John,
> >>
> >> Actually, on reading the links you provide, neither provides solid
> guidance
> >> about the issue in question.  The second link comes closest where it
> says
> >> that projects typically use one of three different methods.  How does
> this
> >> document your strong preference for a single one of these alternatives?
> >>
> > If we really have a strong preference or even a mandatory way of doing
> > this, then it should be clearly stated and not something different people
> > interpret differently.
> >
> > I see
> > https://dist.apache.org/repos/dist/dev/xyz
> >
> > as an elegant way of doing it, let me put it differently if a project
> > prefer to it differently it might not be elegant enough (or well
> > documented).
> >
> > I think we really need to be careful not to make rules just because we
> can.
> > Giving projects freedom where possible should be our goal.
>
> +1
>
> However, we need to document what functions the process needs to support.
>
> For example, the release vote e-mail should uniquely identify the
> release artifacts so that they can be traced back from the public
> release area to the vote e-mail.
>
> Also the vote email should provide sufficient information that anyone
> can check the release without needing to search for additional
> information (e.g. it should link to KEYS etc)
>
> i.e. we need to document _what_ must be done, without necessarily
> prescribing _how_ to do it.
> Though of course it helps to document a recommended process that meets
> the requirements.
>
> > just my opinion.
> > rgds
> > jan i.
> >
> >
> >>
> >>
> >>
> >> On Mon, Sep 8, 2014 at 4:27 PM, John D. Ament <jo...@gmail.com>
> >> wrote:
> >>
> >> > Ted,
> >> >
> >> > Do you mean more than here:
> >> >
> >> > [1]: http://www.apache.org/dev/publishing-maven-artifacts.html
> >> > [2]: http://www.apache.org/dev/release.html#host-rc
> >> >
> >> > On Mon, Sep 8, 2014 at 7:12 PM, Ted Dunning <te...@gmail.com>
> >> wrote:
> >> >
> >> > > Is the new process documented somewhere?
> >> > >
> >> > >
> >> > >
> >> > >
> >> > > On Mon, Sep 8, 2014 at 3:17 PM, sebb <se...@gmail.com> wrote:
> >> > >
> >> > > > On 7 September 2014 20:31, Jacques Nadeau <ja...@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]
> >> > > >
> >> > > > Historic tradition; that was before svnpubsub.
> >> > > >
> >> > > > Note that the DEV tree at
> >> > > >
> >> > > > https://dist.apache.org/repos/dist/dev/xyz
> >> > > >
> >> > > > is NOT published to www.apache.org/dist
> >> > > >
> >> > > > The svnpubsub process takes releases from the RELEASE tree at
> >> > > >
> >> > > > https://dist.apache.org/repos/dist/release/xyz
> >> > > >
> >> > > > Since they have the same parent, one can use svn move (or
> svnmucc) to
> >> > > > transfer the files from dev to release area.
> >> > > > This provides traceability (assuming the the release vote includes
> >> the
> >> > > > SVN revision number)
> >> > > >
> >> > > > > 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.ament@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 <
> >> jacques@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.ament@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 <
> >> > > jacques@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_3UHzeojC9K84Pg@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
> >> > > > >> > > >
> >> > > > >> > >
> >> > > > >> >
> >> > > > >>
> >> > > >
> >> > > >
> ---------------------------------------------------------------------
> >> > > > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> >> > > > For additional commands, e-mail:
> general-help@incubator.apache.org
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>