incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ant elder <>
Subject Re: Followup to VXQuery July 2013 report
Date Wed, 04 Sep 2013 05:42:11 GMT
Hi Marvin, I had a look, that README being pointed to is just build
instructions on how to build the svn trunk isn't it, so not to some
released artifacts. Thats allowed isn't it, i'm pretty sure other projects
and podlings have done something similar anyway. Is it that the website
describes it as user installation instructions rather than developer build
instructions thats the issue?


On Wed, Sep 4, 2013 at 12:30 AM, Marvin Humphrey <>wrote:

> On Thu, Aug 22, 2013 at 9:52 AM, Till <> wrote:
> >> Marvin Humphrey <> hat am 22. August 2013 um
> 18:21
> >> geschrieben:
> >> Let me be blunt: VXQuery needs to make an incubating release.
> >>
> >> Personally, I think it's important that we see one before your next
> >> quarterly report.
> >
> > Yes, I agree. And probably "important" is an understatement.
> Today, I was wondering how VXQuery could have made it through four
> years in the Incubator without making a release, and I took a look at the
> website.
> I note that in the navigation bar on the left hand side there is a "For
> Users"
> section which includes an "Installation" link.  The page at the link
> points to
> the README file in svn.
>     Install instructions can be found in the README file.
> We must not distribute to users from our source repositories:
>     During the process of developing software and preparing a release,
> various
>     packages are made available to the developer community for testing
>     purposes. 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. The only people who
> are
>     supposed to know about such packages are the people following the dev
> list
>     (or searching its archives) and thus aware of the conditions placed on
> the
>     package. If you find that the general public are downloading such test
>     packages, then remove them.
>     Under no circumstances are unapproved builds a substitute for
> releases. If
>     this policy seems inconvenient, then release more often. Proper release
>     management is a key aspect of Apache software development.
> Here's some background about the policy in a message from Roy Fielding to
> the
> legal-discuss list.
>     The release process is critical because it is the point at which the
>     as an organization approves a release to the public. It is the point at
>     which the ASF's liability and goodwill comes into play. The checkpoints
>     are necessary to ensure that we don't release a product that isn't open
>     source or that hasn't been reviewed by the peers, since either one
> would
>     seriously damage the foundation. The consistency is necessary because
> it
>     establishes a well-worn set of procedures that distinguish ASF projects
>     from those at Sourceforge or Google code.
> Speaking as the Incubator PMC Chair:
> Please remove the user installation links immediately.  VXQuery is not
> allowed
> to distribute code which has not passed an IPMC vote to the general public.
> Speaking as a member of the Incubator PMC:
> If VXQuery has not released by the next report, I expect to initiate a
> discussion on retiring the podling.
> Marvin Humphrey
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message