Re: [DISCUSS] Incubator exit criteria
This is quite a long thread now so its not that clear what the actual proposal is now, could you maybe state what the current proposal is? I think its something like If a podling is over a year old and not done a release then retire it. As i've said i don't think thats a very good rule and doesn't seem like its really been thought through properly. For example, its kept saying that the podling would go to the ASF Attic but the Attic is only for TLPs so retired podlings don't go there. How about before adding a new rule to the policy page we just try it with a few of the old podlings first to see what happens and from that find what sort of rule might work? ...ant On Wed, Jul 9, 2014 at 8:23 AM, Roman Shaposhnik r...@apache.org wrote: On Tue, Jul 1, 2014 at 11:01 PM, ant elder ant.el...@gmail.com wrote: Right, and thats why i don't think a rule like that would be useful. I still don't quite follow. Are you saying that the rule wouldn't be useful, or that incubator - attic migration wouldn't be? If Droids was made to retire the code would be frozen in the attic or forced out to github, That would be true. But what's the harm in that? The code still exists and can be checked out. What we're essentially signaling to the outside world is that ASF can no longer vouch for the viability of the community around it. Isn't it the truth of the matter? forced to change its package name I don't really see any reason to do that for code that got moved to that attic. Am I missing something? in the code and so probably lose existing users, Again, why would code lose users? Remember we're talking about a situation of no releases here. Presumably those users who are comfortable building from the repo would just keep doing so. And since there was no release, what else is out there for us to worry about? and remove all references to apache in the project and doc and website etc etc. All tons of work which being a small project they'd probably never get done so it would likely be the death of the project. I see no reason to do any of that for the project that's in the attic. And for what purpose? To quote one of them from their dev list a couple of months ago: Going to the attic would suck. It's a solid code base, it's just one of those things that doesn't necessarily need to change much.. The main people in Droids we know and trust, they are ASF members and PMC chairs. We in the Incubator should be helping them graduate not looking for ways to retire the project. The quote feels a little bit misinformed about the attic/ASF policies. Thanks, Roman. - 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
Re: Question on report
Hi, On Wed, Jul 9, 2014 at 1:21 AM, Joe Brockmeier j...@zonker.net wrote: ...So - one of the podlings did not file a report, but one of the mentors did fill it in. Am I correct in assuming this would still count as a missed report?... I suppose you mean DeviceMap - we'll probably have to write a book on that one at some point ;-) The challenges I sent to their dev list (see [1]) have started good (and somewhat interesting) activity towards finally making a release, and the podling does not require much energy from the Incubator PMC so IMO it's still not urgent to fail its incubation. -Bertrand [1] http://wiki.apache.org/incubator/July2014 - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: Wiki Access
On Thu, 10 Jul 2014, Alan Cabrera wrote: Does one have to be a infrastructure team member to grant access or can IPMC members provide that? You need to be listed on the AdminGroup page: https://wiki.apache.org/incubator/AdminGroup There's currently 21 IPMC members on there who can grant karma. If another IPMC member would like to be number 22, I'd suggest a suitable post to private@ Nick - To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
Re: [VOTE] Release Apache Tez-0.4.1-incubating RC0
+1 (binding) Thanks, Ashutosh On Tue, Jul 8, 2014 at 1:38 PM, Arun C Murthy a...@hortonworks.com wrote: +1 (binding) Arun On Jul 7, 2014, at 1:20 PM, Siddharth Seth ss...@apache.org wrote: The Apache Tez Incubating PPMC has voted to release Apache Tez-0.4.1-incubating (RC0). Result Mail: http://mail-archives.apache.org/mod_mbox/incubator-tez-dev/201407.mbox/%3CCAOapipsBOizkB5yOmCxT1UP9%2BCL%2BHjtxcy39mzFNFkZXeocaxA%40mail.gmail.com%3E Initial Vote Thread: http://mail-archives.apache.org/mod_mbox/incubator-tez-dev/201406.mbox/%3CCAOapipsP5KfMD2_imfubp%2BUKc9qPA5b4EVAmRPqbv-utt%3DSNkQ%40mail.gmail.com%3E This thread is for the IPMC to vote on this release. GIT source tag: https://git-wip-us.apache.org/repos/asf/incubator-tez/repo?p=incubator-tez.git;a=log;h=refs/tags/release-0.4.1-incubating-rc0 Staging site: https://dist.apache.org/repos/dist/dev/incubator/tez/tez-0.4.1-incubating-src-rc0/ Nexus Staging URL: https://repository.apache.org/content/repositories/orgapachetez-1006/ PGP release keys: http://pgp.mit.edu/pks/lookup?op=getsearch=0x477E02D33DD51430 KEYS file available at https://dist.apache.org/repos/dist/release/incubator/tez/KEYS List of issues fixed in the release: *https://issues.apache.org/jira/browse/TEZ/fixforversion/12327143/ https://issues.apache.org/jira/browse/TEZ/fixforversion/12327143/* Also available in CHANGES.txt within the release tarball. Vote will be open for at least 72 hours ( until the required number of IPMC votes are obtained). [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Thanks - Sid -- 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.
