On Mon, May 7, 2012 at 9:48 PM, Bruno Mahé <bm...@apache.org> wrote:
>...

It seems that we're talking about this location:
  http://www.apache.org/dist/incubator/bigtop/bigtop-0.3.0-incubating/

> Again, we don't distribute non-Apache software,

I didn't find any non-Apache software in the location noted above.

> as well as we don't
> distribute other Apache software either.

I found a bunch of Apache software in there.

So I'd say you're distributing it.

(not that I believe that is a problem, but let's try and get things
straight here)

> Since you keep on doing this mistake, there is surely a
> misunderstanding. So it would probably be easier if you could point us
> to other Apache (or non-Apache) software being distributed as part as
> any Apache Bigtop (incubating) releases on which members have voted on?

I can see anybody looking at that URL location believing that you're
distributing both Bigtop *AND* other Apache software.

If you're using a different definition of "distributing", then we need
to resolve that situation. I see lots of ASF software being
distributed via that URL.

> And again, Apache releases are what people vote on. not the convenience
> artefacts which are there for convenience and are not voted on. So I
> still don't see any reason to not withdraw your -1 since your only issue
> seems to be related to the dependencies in the convenience artefacts
> (which is standard practice, even within Apache Hadoop)

It is true that votes only apply to Bigtop releases and not those
artifacts under bigtop-0.3.0-incubating/repos/.

It is also true that (in normal PMC operation) it is not possible to
veto a release. I have no strong opinion, but would believe the that a
podling can also make a release with three IPMC +1 votes (and, again,
vetoes do not apply). Note: IPMC votes, not PPMC votes. If somebody
raises a -1, then I suspect getting those IPMC votes might be
difficult until the concern is discussed.

Regarding the release artifacts: I don't have any strong opinions
right now. I can see the confusion with them all in the same location.
I can also see that Infra should probably get involved in some way to
deal with mirroring issues and to somehow distinguish, verify, and
validate these binary artifacts.

>...

Cheers,
-g

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Reply via email to