Re: [DISCUSS] Release Apache VXQuery Incubating 0.2 (RC4)

2013-10-16 Thread Vinayak Borkar 

Hi Marvin,


Thanks for your email. I was unaware that votes are allowed to take a 
long time. My understanding (albeit flawed, I guess) was that votes are 
allowed to be outstanding for only 72 hours. Hence my email.


I do agree that retirement is a valid part of a software system's 
lifecycle. However, in the case of VXQuery the committers have quite 
some juice left in them to make more progress at this time. In fact a 
lot more work gets done on the project than what appears on "visible" 
forums like mailing lists. We use IM and Skype much more than we use 
mailing lists.


The whole release process has been pretty frustrating due to a 
combination of two orthogonal factors that have just been a drain on the 
team.


1. While there are guidelines that need to be adhered to by a release, 
we were struggling for a long time to automate the release process so 
that it produced all the artifacts that were needed to satisfy Apache's 
requirements. Instead of all the guidelines as the primary pointer to 
how releases should be made, having one link to the parent pom that can 
be inherited by a Maven-driven Java project that does all the heavy 
lifting of creating a release that meets Apache guildelines would have 
got us to a release a year ago. We finally found this POM by looking at 
the Helix project that had made a successful release.


2. It feels that the whole voting process around releases is very ad-hoc 
and not very efficient. In fact at times it appears very subjective. As 
an example, look at the voting process around the RCs for VXQuery. All 
the issues raised around RC_i (i > 1) have been true of the first RC 
created. So clearly all the issues could have been raised at one go with 
RC1 and we could have been done with this whole process months ago. If 
the Incubator is serious about projects creating releases and going 
through the "process", I think it is only fair to the projects that the 
IPMC tightens the review process so that things get done more 
efficiently. I would like to see some accountability with the IPMC 
regarding the review process when it comes to voting down an RC when the 
same issue was true of a previous RC and could have been pointed out before.


Thanks for the ODC-BY comment. I do hope that issue is resolved quickly 
so we can create a successful release.



Thanks,
Vinayak

On 10/16/13 7:13 PM, Marvin Humphrey wrote:

Hi Vinayak,

On Thu, Oct 10, 2013 at 3:40 PM, Vinayak Borkar  wrote:


It has been over 72 hours since the vote for the first VXQuery release has
been open, and we still do not have the one vote we need from an IPMC
member. I am unsure how this process works.


For the last four months, I've been tracking the elapsed time between when a
release candidate is published on a podling dev list and the arrival of the
third IPMC +1 vote.  These stats are going into the Incubator's monthly
report to the Board.  The average is roughly a week.

However, it's not unusual for some release votes to take longer.  One of the
risk factors associated with long VOTE times is incubating for a long time (as
VXQuery has), because Mentors tend to drift away and leave a podling with
insufficient active IPMC representation[1].

Some VOTEs are outliers, though.  ODF Toolkit's last release waited 20 days;
the recent VOTE for Allura's first incubating release stayed open for several
weeks awaiting IPMC approval before the release candidate was finally
withdrawn.  (We've yet to see a new one.)

A number of us have been trying to address the structural flaws in the
Incubator for several years now, but it is challenging to strike a balance
between granting podlings more autonomy and exercising our oversight
responsibilities -- so most proposals do not achieve consensus.  Personally, I
now try to spend my cycles approaching the problem from another angle, by
working on ways to lower the cost of reviewing releases.


Until a few weeks ago, we heard from quite a few vocal IPMC members about
how the project did not deserve to remain in incubation


We don't want podlings to "remain in incubation" indefinitely -- we want them
to either graduate, or retire.  Please take my followup of the VXQuery July
report in that context -- and please understand that there's nothing wrong
with retiring, since all software has a life cycle and sometimes it's better
for the individual members of the community to move on to other interests.
Nevertheless, graduation is of course the desired outcome every time a podling
enters incubation and it is great to see VXQuery's increased activity.


because it was
unable to make a release.


Apache projects release.  Communities which don't release don't belong here.

Should VXQuery graduate and become a TLP, you will be expected to keep making
releases according to Apache guidelines -- and demonstrating that the
community is capable of making such releases is a crucial test.


Now there is an attempt at a release that has been voted in by the PPMC, but
there is c

Re: [VOTE] Release of Apache MRQL 0.9.0 incubating (RC5)

2013-10-16 Thread Alan D. Cabrera 
72 hour is not a maximum requirement, it's a minimum requirement.  So, you can 
keep it open.

With that said, I'm sorry that you don't have any binding votes yet.  I should 
be able to look at this sometime tomorrow.


Regards,
Alan

On Oct 16, 2013, at 5:55 AM, Leonidas Fegaras  wrote:

> Helo,
> This is a reminder that this vote is scheduled to close in about 24
> hours out of 72 hours and we still have no binding votes from the
> Incubator PMC.
> This is our first release and we have spent a lot of time to migrate
> our old source code to the Apache infrastructure and to adapt the
> Apache policies in all parts of the project.
> Please vote on releasing Apache MRQL 0.9.0 incubating.
> Thank you
> Leonidas Fegaras
> 
> 
> On 10/14/2013 07:37 AM, Leonidas Fegaras wrote:
>> Hello,
>> This is a call for a vote on Apache MRQL 0.9.0 incubating. This is our
>> third try for our first release. We have resolved all the issues that
>> have been discussed in our previous tries.
>> Apache MRQL is a query processing and optimization system for
>> large-scale, distributed data analysis, built on top of Apache Hadoop,
>> Hama, and Spark.
>> A vote was held on the MRQL developer mailing list and it passed with
>> three +1 PPMC votes, and zero -1 or 0 votes (see the vote thread [1]
>> and result thread [2]), and now requires a vote on this list.
>> The vote will be open for 72 hours and passes if a majority of at
>> least 3 +1 IPMC votes are cast.
>> 
>> [ ] +1 Release this package as Apache MRQL 0.9.0-incubating
>> [ ] -1 Do not release this package because ...
>> 
>> The release tarballs, including signatures, digests, etc can be found at:
>> https://dist.apache.org/repos/dist/dev/incubator/mrql/0.9.0-incubating-RC5/
>> The release candidate consists of the following source distribution
>> archives:
>> - mrql-dist-0.9.0-incubating-src.[tar.gz|zip]
>>SHA1 of TGZ: C99D 6789 BD67 8764 52AC  DF5F 0F0D 4D72 6106 2141
>>SHA1 of ZIP: BEBA FE68 6A77 38BC 937C  24B3 959A 400D 001F B39F
>> You can compile the sources using 'mvn install'.
>> In addition, the following supplementary binary distributions are
>> provided for user convenience at the same location:
>> - mrql-dist-0.9.0-incubating-bin.[tar.gz|zip]
>>SHA1 of TGZ: 4C04 E4F5 36F5 631E 6552  AB2E 8CBB 6171 2942 AF90
>>SHA1 of ZIP: 6165 8DCD 178C 094D 21E3  3B1B AA46 1028 9CB6 B5F7
>> 
>> A staged Maven repository is available for review at:
>> https://repository.apache.org/content/repositories/orgapachemrql-140/
>> 
>> The release candidate has been signed through the key 798764F1 in:
>> http://www.apache.org/dist/incubator/mrql/KEYS
>> 
>> The release candidate is based on the sources tagged with
>> MRQL-0.9.0-incubating-RC5 in:
>> https://git-wip-us.apache.org/repos/asf?p=incubator-mrql.git;a=commit;h=7386f5d7edeea21d38e7a6c95e8fbe5e59e27d26
>> 
>> RAT check:
>> http://people.apache.org/~fegaras/dist/mrql-0.9.0-incubating-RC5/rat.txt
>> 
>> To learn more about Apache MRQL, please visit:
>> http://wiki.apache.org/mrql/
>> Thanks,
>> Leonidas Fegaras
>> 
>> [1] http://markmail.org/message/5okv2n6lshd3tgh6
>> [2] http://markmail.org/message/alyra637j5djxcrv
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>> .
>> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


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

[VOTE][RESULT] Retire the Tashi podling

2013-10-16 Thread Marvin Humphrey 
On Wed, Oct 2, 2013 at 4:45 PM, Marvin Humphrey  wrote:
>  [ ] +1 Retire the Tashi podling
>  [ ] +0 Neither here nor there
>  [ ] -1 Do not retire the podling because ...

The VOTE passes, with binding +1 votes from the following IPMC members:

Alan D. Cabrera
Chip Childers
Matthew Franklin
Marvin Humphrey
Olivier Lamy
Roman Shaposhnik
Mark Struberg

If a volunteer can be found to take care of the retirement steps for Tashi,
that would be great.

http://incubator.apache.org/guides/retirement.html#steps-to-retirement

If no one steps forward within a week, I'll take it on.

Marvin Humphrey

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

[DISCUSS] Release Apache VXQuery Incubating 0.2 (RC4)

2013-10-16 Thread Marvin Humphrey 
Hi Vinayak,

On Thu, Oct 10, 2013 at 3:40 PM, Vinayak Borkar  wrote:

> It has been over 72 hours since the vote for the first VXQuery release has
> been open, and we still do not have the one vote we need from an IPMC
> member. I am unsure how this process works.

For the last four months, I've been tracking the elapsed time between when a
release candidate is published on a podling dev list and the arrival of the
third IPMC +1 vote.  These stats are going into the Incubator's monthly
report to the Board.  The average is roughly a week.

However, it's not unusual for some release votes to take longer.  One of the
risk factors associated with long VOTE times is incubating for a long time (as
VXQuery has), because Mentors tend to drift away and leave a podling with
insufficient active IPMC representation[1].

Some VOTEs are outliers, though.  ODF Toolkit's last release waited 20 days;
the recent VOTE for Allura's first incubating release stayed open for several
weeks awaiting IPMC approval before the release candidate was finally
withdrawn.  (We've yet to see a new one.)

A number of us have been trying to address the structural flaws in the
Incubator for several years now, but it is challenging to strike a balance
between granting podlings more autonomy and exercising our oversight
responsibilities -- so most proposals do not achieve consensus.  Personally, I
now try to spend my cycles approaching the problem from another angle, by
working on ways to lower the cost of reviewing releases.

> Until a few weeks ago, we heard from quite a few vocal IPMC members about
> how the project did not deserve to remain in incubation

We don't want podlings to "remain in incubation" indefinitely -- we want them
to either graduate, or retire.  Please take my followup of the VXQuery July
report in that context -- and please understand that there's nothing wrong
with retiring, since all software has a life cycle and sometimes it's better
for the individual members of the community to move on to other interests.
Nevertheless, graduation is of course the desired outcome every time a podling
enters incubation and it is great to see VXQuery's increased activity.

> because it was
> unable to make a release.

Apache projects release.  Communities which don't release don't belong here.

Should VXQuery graduate and become a TLP, you will be expected to keep making
releases according to Apache guidelines -- and demonstrating that the
community is capable of making such releases is a crucial test.

> Now there is an attempt at a release that has been voted in by the PPMC, but
> there is complete radio silence on the vote.

Be persistent and polite and eventually you will break through.

If you are unlucky enough to duplicate Allura's experience, you can at least
rest assured that the Board is going to hear about it.

> I appeal to the same people who expressed their opinions a few weeks ago to
> at least look at the release we have created and vote either for or against
> it.

I rarely perform freelance release reviews any more because the current system
infuriates me and I do not wish to spend my volunteer time perpetuating it.
However, I'm pleased that the opportunity arose to contribute via the ODC-BY
licencing question.

Good luck,

Marvin Humphrey

[1] For more thoughts on the subject of Mentor attrition, see
.

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

Re: [IP Clearance] CouchDB: rcouch

2013-10-16 Thread Noah Slater 
+1

Thanks for managing this, Jan!

For reference:

http://incubator.apache.org/ip-clearance/couchdb-rcouch.html


On 14 October 2013 21:59, Jan Lehnardt  wrote:

> Dear Incubator,
>
> A committer offers a future-port of CouchDB to be merged back into the
> mainline project.
>
> The code is up on:
>
>  zip: http://dl.refuge.io/rcouch-0.7.1.tar.gz
>  sha: 332b09635d9ca55122ee02903984808f183a4674
>
> The IP Clearance document:
>
>
> http://svn.apache.org/viewvc/incubator/public/trunk/content/ip-clearance/couchdb-rcouch.xml?view=co&content-type=text%2Fplain
>
>
> Thanks!
> Jan
> --
>



-- 
Noah Slater
https://twitter.com/nslater

Re: [VOTE] Release of Apache MRQL 0.9.0 incubating (RC5)

2013-10-16 Thread Leonidas Fegaras 

Helo,
This is a reminder that this vote is scheduled to close in about 24
hours out of 72 hours and we still have no binding votes from the
Incubator PMC.
This is our first release and we have spent a lot of time to migrate
our old source code to the Apache infrastructure and to adapt the
Apache policies in all parts of the project.
Please vote on releasing Apache MRQL 0.9.0 incubating.
Thank you
Leonidas Fegaras


On 10/14/2013 07:37 AM, Leonidas Fegaras wrote:

Hello,
This is a call for a vote on Apache MRQL 0.9.0 incubating. This is our
third try for our first release. We have resolved all the issues that
have been discussed in our previous tries.
Apache MRQL is a query processing and optimization system for
large-scale, distributed data analysis, built on top of Apache Hadoop,
Hama, and Spark.
A vote was held on the MRQL developer mailing list and it passed with
three +1 PPMC votes, and zero -1 or 0 votes (see the vote thread [1]
and result thread [2]), and now requires a vote on this list.
The vote will be open for 72 hours and passes if a majority of at
least 3 +1 IPMC votes are cast.

[ ] +1 Release this package as Apache MRQL 0.9.0-incubating
[ ] -1 Do not release this package because ...

The release tarballs, including signatures, digests, etc can be found at:
https://dist.apache.org/repos/dist/dev/incubator/mrql/0.9.0-incubating-RC5/
The release candidate consists of the following source distribution
archives:
- mrql-dist-0.9.0-incubating-src.[tar.gz|zip]
SHA1 of TGZ: C99D 6789 BD67 8764 52AC  DF5F 0F0D 4D72 6106 2141
SHA1 of ZIP: BEBA FE68 6A77 38BC 937C  24B3 959A 400D 001F B39F
You can compile the sources using 'mvn install'.
In addition, the following supplementary binary distributions are
provided for user convenience at the same location:
- mrql-dist-0.9.0-incubating-bin.[tar.gz|zip]
SHA1 of TGZ: 4C04 E4F5 36F5 631E 6552  AB2E 8CBB 6171 2942 AF90
SHA1 of ZIP: 6165 8DCD 178C 094D 21E3  3B1B AA46 1028 9CB6 B5F7

A staged Maven repository is available for review at:
https://repository.apache.org/content/repositories/orgapachemrql-140/

The release candidate has been signed through the key 798764F1 in:
http://www.apache.org/dist/incubator/mrql/KEYS

The release candidate is based on the sources tagged with
MRQL-0.9.0-incubating-RC5 in:
https://git-wip-us.apache.org/repos/asf?p=incubator-mrql.git;a=commit;h=7386f5d7edeea21d38e7a6c95e8fbe5e59e27d26

RAT check:
http://people.apache.org/~fegaras/dist/mrql-0.9.0-incubating-RC5/rat.txt

To learn more about Apache MRQL, please visit:
http://wiki.apache.org/mrql/
Thanks,
Leonidas Fegaras

[1] http://markmail.org/message/5okv2n6lshd3tgh6
[2] http://markmail.org/message/alyra637j5djxcrv


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

.




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

Fwd: [RESULT][VOTE] Release Apache Knox (Incubator) 0.3.0 (PASSED)

2013-10-16 Thread Kevin Minder 

Hi Everyone,
Below is the result of the [VOTE] thread from the Knox project to create 
release 0.3.0.  We will wait a minimum of 72 hours for review and 
feedback before proceeding with publishing the release.  The release is 
currently available in the dev staging area in will be moved to the 
release area after 72 hours if no issues are raised. The link to the dev 
staging area is provided below for convenience.

https://dist.apache.org/repos/dist/dev/incubator/knox/knox-incubating-0.3.0/
Thanks!
Kevin.

 Original Message 
Subject:[RESULT][VOTE] Release Apache Knox (Incubator) 0.3.0 (PASSED)
Date:   Tue, 15 Oct 2013 20:16:48 -0400
From:   Kevin Minder 
To: d...@knox.incubator.apache.org 



Hi Everyone,

More than 72 hours have passed and the current vote thread is considered
concluded and passes with the following resolution:

Three +1 binding votes from the following IPMCs:

* Devaraj Das
* Chris A. Mattmann
* Mahadev Konar

Two +1 binding votes from the following PPMCs:

* Kevin Minder
* Larry McCay

Four +1 non-binding votes

* Dilli Arumugam
* Maksim Kononenko
* Vladimir Tkhir
* Sergey Balan

Zero -1 votes

I will notify general@incubator and wait an additional 72 hours for
feedback before beginning the process of moving the release artifacts to
the mirrors.

For reference here is the link to the [VOTE] thread
http://mail-archives.apache.org/mod_mbox/knox-dev/201310.mbox/%3c5255ac37.9060...@hortonworks.com%3E

Kevin.




--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to 
which it is addressed and may contain information that is confidential, 
privileged and exempt from disclosure under applicable law. If the reader 
of this message is not the intended recipient, you are hereby notified that 
any printing, copying, dissemination, distribution, disclosure or 
forwarding of this communication is strictly prohibited. If you have 
received this communication in error, please contact the sender immediately 
and delete it from your system. Thank You.

[RESULT][VOTE] Release of Apache Olingo 1.0.0 incubating (RC03)

2013-10-16 Thread Klevenz, Stephan 
Dear all,

Thanks for your support! The 72 hours have passed and we have 9
positive votes, of which 3 are binding and 6 are non-binding. We now have
the required number of positive binding votes and will therefore proceed
with the release.

Greetings,
Stephan


Binding votes (3)
+1 Florian Mueller
+1 Dave Fisher
+1 Alan D. Cabrera

Non-binding votes (6)
+1 Michael Bolz 
+1 Jens Huesken 
+1 Chandan V.A 
+1 Christian Amend 
+1 Stephan Klevenz 
+1 Carl Mosca

Votes from the Incubator mailing list
[1] http://markmail.org/message/inmqzvd5h5npdu2c

Votes from the Olingo mailing list:
[2] http://markmail.org/message/2gqhcvfzg7atz7cr
[3] http://markmail.org/message/kpofoobx4k6mxtle



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