[
https://issues.apache.org/jira/browse/INCUBATOR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264433#comment-17264433
]
Josh Elser commented on INCUBATOR-245:
--
[~jmclean], seems like I'm la
+1 binding
* I think you might have missed the bin tarball (you have the supporting
xsums and sigs, but no tarball ;))
* Can build from src
* Src tarball looks good, no unexpected files
* Required files (license, notice, disclaimer) all look present
* rat:check says license headers are good
On
I really don't care one way or the other for the terminology we use and,
as VP Phoenix, am happy to use whatever terminology is deemed "most
correct".
If anything, I like Justin's use of "exited" to not attach feelings to
how a podling leaves the incubator. I think attaching "good" and "bad"
;s going on the whole way.
Alan.
On Thu, Nov 14, 2019 at 8:32 AM Josh Elser wrote:
I'm a bit confused about where we go from this point.
Given the doc[1] that Alan shared last time, we are good to move ahead
with the logistical changes.
Further, the next guide[2] simply says that VP
I'm a bit confused about where we go from this point.
Given the doc[1] that Alan shared last time, we are good to move ahead
with the logistical changes.
Further, the next guide[2] simply says that VP Phoenix (me) should
coordinate with VP Incubator.
Should I go ahead and file the TLP Paren
Carrying over +1 (binding) from PPMC.
On 11/5/19 3:36 AM, Elek, Marton wrote:
Hi,
Apache Ratis Thirdpardy 0.3.0-rc0 vote [1] is just passed on the PPMC
vote [2].
Apache Ratis is an embaddable Raft implementation but this release
artifact is only the packaging of some of the 3rd party depen
I like the idea of opt-in for committership for the current podling
membership (without any "time to respond" limitation). I don't foresee
any concerns doing that, but will shout if that becomes an issue.
On 10/28/19 3:09 PM, Justin Mclean wrote:
Hi,
According to [4] the first step of gradua
(w/ VP Phoenix hat)
My current expectation is that we'd just rename the existing Git
repositories and change the LDAP group which are used to determine write
access. In other words, your Git repos will exist just as they do now,
but only at different coordinates.
On 10/25/19 12:27 AM, Ohad S
[
https://issues.apache.org/jira/browse/INCUBATOR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16953781#comment-16953781
]
Josh Elser commented on INCUBATOR-245:
--
The Apache Slider podling retired in
Haven't heard back from Justin -- broadening to general@incubator.
On 9/30/19 5:31 PM, Josh Elser wrote:
Hey Justin,
Would you like a final "Rya Graduated" podling report or just to drop
Rya from the October2019 report?
- Josh
On 9/28/19 8:46 PM, jmcl...@apache.org wrote
+1 (binding)
* Can build from source
* Your version is 0.4.0-rc4. Are you sure this is what you want, and not
just 0.4.0?
* You have pom.xml.versionsBackup is the source tarball you probably
don't want :)
* DISCLAIMER present
* L&N look reasonable.
Please make sure to update dist/release/incu
oject:
* Aaron Mihalik
* Adina Crainiceanu
* Billie Rinaldi
* Caleb Meier
* David Lotts
* David Rapp
* Jennifer Brown
* Josh Elser
* Puja Valiyil
* Roshan Punnoose
* Steve R Wagner
NOW, THEREFORE, BE IT FURTHER RESOLVED, that Adina
serve as the initial members of the Apache Rya Project:
* Aaron Mihalik
* Adina Crainiceanu
* Billie Rinaldi
* Caleb Meier
* David Lotts
* David Rapp
* Jennifer Brown
* Josh Elser
* Puja Valiyil
* Roshan Punnoose
* Steve R Wagner
+1 (binding)
* KEYS is updated
* xsums/sigs OK (SHA512 is good)
* No binaries in the source release
* Can build from source!
* DISCLAIMER/LICENSE/NOTICE all OK (need to update copyright year in
NOTICE, fwiw)
Good work, folks!
- Josh
On 7/22/19 6:24 PM, Aaron D. Mihalik wrote:
The Apache Rya
Thanks!
On 12/8/18 8:42 PM, Justin Mclean wrote:
Hi,
Also this may help [1] along with the other link I’ve sent.
Thanks,
Justin
1. https://wiki.apache.org/incubator/IncubatorReleaseChecklist
-
To unsubscribe, e-mail: general-
I guess I just need to accept that I'll never have a firm grasp on L&N
construction. I'm still a bit befuddled. Thanks for taking the time to
explain, Justin.
I would have confidently thought that bundled software's copyright
statements always had a place in NOTICE. Also, a surprise to me that
This vote passes with 3 binding +1's and 1 non-binding +1.
Thanks all.
On 12/3/18 3:48 PM, Josh Elser wrote:
IPMC,
Please find the following PPMC VOTE information which just passed.
Note that the delta over the 0.1.0 is extremely small, should be a
super-trivial vote.
VOTE (original
Thanks for the quick vote, Justin!
On 12/4/18 2:14 AM, Justin Mclean wrote:
Hi,
+1 binding but there probably an issue you’ll need to look into before ether
net release.
I checked:
- incubating in name
- signatures and hashes good
- DISCLAIMER exists
- LICENSE and NOTICE correct
- All ASF fil
myself and Jitendra.
- Josh
Forwarded Message
Subject: [VOTE] Ratis Thirdparty 0.2.0 rc0
Date: Fri, 30 Nov 2018 15:33:19 -0500
From: Josh Elser
To: d...@ratis.incubator.apache.org
Hi,
Please on the following as Ratis Thirdparty 0.2.0:
The release artifact (in source form only) is
+1 (binding)
The RAT plugin fails but these look fine to fix for the next release:
Unapproved licenses:
.travis.yml
bintray-settings.xml
misc/findbugs-exclude.xml
misc/omid_checks.xml
Everything else looks good to me.
On 11/18/18 2:45 AM, Ohad Shacham wrote:
Hi,
The Apache Omid com
This vote passes with 3 binding +1's (Justin, Jitendra, Josh) and
nothing else.
Thanks, all.
On 11/5/18 2:09 PM, Josh Elser wrote:
IPMC,
Please vote on the following release candidate to become Apache Ratis
Thirdparty 0.1.0.
You may find the PPMC VOTE thread at
https://lists.apach
Thanks, Justin.
Will take an action-item for the file extensions.
On 11/8/18 11:09 PM, Justin Mclean wrote:
Hi,
+1 (binding)
I checked:
- incubating in name
- signature and hashes fine, but you may want to check the file extensions as
policy changed a little while back to what was allowed
-
Looks like I forgot to include duration in my initial message. Of
course, this will run for at least the customary 72hours.
And on that note: those 72hours elapses today. Any IPMC votes would be
greatly appreciated!
- Josh
On 11/5/18 2:09 PM, Josh Elser wrote:
IPMC,
Please vote on the
IPMC,
Please vote on the following release candidate to become Apache Ratis
Thirdparty 0.1.0.
You may find the PPMC VOTE thread at
https://lists.apache.org/thread.html/000d9c6f69b6ddcda5391134df8666c7df83193dd01b97218579069c@%3Cdev.ratis.apache.org%3E,
with the RESULT at
https://lists.apache.
Well, then. Mark that up as my "one" for the year ;)
Thanks boss.
On 10/3/18 7:19 PM, Justin Mclean wrote:
Hi,
That was put in to see if anyone was paying attention:-)
Thanks,
Justin
On 4 Oct. 2018 9:17 am, "Josh Elser" wrote:
Justin -- I thought we retired the Slide
Justin -- I thought we retired the Slider podling. Going off my mail
client, INFRA-16568 tracked this and was done at the end of May.
Maybe some podling metadata didn't get cleaned up fully?
On 10/2/18 6:36 PM, Justin Mclean wrote:
Hi,
Here the list of podlings that currently have one or two
+1 (binding)
On 8/26/18 11:14 PM, Mick Semb Wever wrote:
After a brief discussion¹ I would like to call a VOTE to accept Zipkin into the
Apache Incubator.
The full proposal is available on the wiki² and is pasted below in text form as
well.
This vote will run at least 72 hours. Please VOTE as
+1 (binding)
* tephra_distribution/NOTICE_BINARY needs a year update
* files under tephra_distribution need exclusions on apache-rat-plugin
* Can build from src (tests don't pass though)
* I see lots of really old HBase versions in the dep list, would be a
good idea to prune them (no longer rece
This vote passes with 4 +1's and nothing else.
Sorry for the (extreme) delay on calling it.
On 8/9/18 6:52 PM, Josh Elser wrote:
Hi,
The Gossip podling has voted to retire from incubation.
DISCUSS:
https://lists.apache.org/thread.html/8acab107a15a6bc50253cb20aa633a3ac36b70364294f149660
Thanks, Taylor. Appreciate that!
On 8/9/18 8:51 PM, P. Taylor Goetz wrote:
+1 (binding)
As the champion for this project, I’ll volunteer to take care of the retirement
tasks.
-Taylor
On Aug 9, 2018, at 6:52 PM, Josh Elser wrote:
Hi,
The Gossip podling has voted to retire from incubation
Hi,
The Gossip podling has voted to retire from incubation.
DISCUSS:
https://lists.apache.org/thread.html/8acab107a15a6bc50253cb20aa633a3ac36b70364294f149660fc6c4@%3Cdev.gossip.apache.org%3E
VOTE:
https://lists.apache.org/thread.html/d725e5f03ecbd516613b9a75abd9178936e578b38c3793933f571caf@%3C
+1 (binding)
* Source release contains only source files
* Can build from source
* Couldn't get tests to pass (oh well)
* Nice work on the bin release's L&N files
* Glanced at website, too; looks like you have necessary info
* Smoketest on the bin release worked
* Tag and commit exist in SCM
Wou
ings don't fail, the people behind them simply had a change in
priorities.
Gossip is a great toolkit that I believe people will continue to use.
John
On Thu, Jun 28, 2018, 12:44 PM Josh Elser wrote:
I've been trying to be patient around this, but I think this month's
incubator r
I've been trying to be patient around this, but I think this month's
incubator report must be "Gossip is going to exit incubation" (I'm not
sure what the proper verb is here; I only know that "retire" is wrong)
We've gone through many months where the only traffic I've seen on the
mailing list
+1 (binding), but with one issue ;)
The source release looks fine, as do sigs/xsums. DISCLAIMER, LICENSE and
NOTICE are all fine too.
Only thing I see is that your new additions made in
https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.0-rc3/KEYS
must be reflected in
https://dist.
+1 (binding)
Things look good for the most part, a few things I noticed which can be
fixed next release:
* NOTICE needs an updated copyright year
* `mvn apache-rat:check` fails on the below files
apache-tephra-0.14.0-incubating/tephra-distribution/licenses/Aopa.PL
apache-tephra-0.14.0-incuba
+1 (binding)
Thanks for pushing this to completion, Billie!
On 5/20/18 1:59 PM, Billie Rinaldi wrote:
After a long period of low activity, the Slider PPMC has recently decided
upon retirement [1]. Please vote on whether we should retire the Slider
podling. Here is my +1 (binding).
[ ] +1 Retir
This (lazy-consensus) VOTE passes with no objections.
On 3/15/18 1:10 PM, Josh Elser wrote:
The Apache Phoenix PMC has completed the IP Clearance to adopt the
Python-based driver to the Apache Phoenix Query Server called "Python
PhoenixDB".
http://incubator.apache.org/ip-clearan
Oops, will do. I thought that got auto-updated generated.
Thanks for the catch, Craig.
On 3/16/18 3:53 PM, Craig Russell wrote:
Hi Josh,
When you get a chance, please update the index page
http://incubator.apache.org/ip-clearance/
Thanks,
Craig
On Mar 15, 2018, at 10:10 AM, Josh Elser
Gotcha. Thanks for taking a look, John! Much appreciated.
On 3/16/18 4:22 PM, John D. Ament wrote:
Yeah, its just a bit weird. The IP clearance mentions he's a copyright
holder, but the file headers don't mention that. Its fine either way.
On Fri, Mar 16, 2018 at 1:23 PM Josh El
is, I understand that Mark and Lukas are the two contributors with
non-trivial contributions.
Craig
Yup, Craig says it all. Does that help, John?
John
On Thu, Mar 15, 2018 at 1:10 PM Josh Elser wrote:
The Apache Phoenix PMC has completed the IP Clearance to adopt the
Python-based driver t
The Apache Phoenix PMC has completed the IP Clearance to adopt the
Python-based driver to the Apache Phoenix Query Server called "Python
PhoenixDB".
http://incubator.apache.org/ip-clearance/phoenix-phoenixdb.html
This is subject to the 72-hr lazy consensus window (2018/03/18 1700GMT).
Please
+1 (binding)
* Can build from src
* apache-rat check passes (exclusion list looks OK)
* xsums/sigs OK
* KEYS is good
* Commit is published
* DISCLAIMER is present
On 2/24/18 10:18 PM, Adina Crainiceanu wrote:
The Apache Rya community has voted and approved the proposed release of
Apache Rya 3.2
Thanks, John. That helps and I agree with your assessment.
Let me leave comment to that effect.
On 10/11/17 10:50 PM, John D. Ament wrote:
Josh,
On Wed, Oct 11, 2017 at 9:48 PM Josh Elser wrote:
(trimming CC since asking a specific question)
John -- how would you like to handle Gossip&#
] Working towards first release
[ ] Community building
[ ] Nearing graduation
[ ] Other:
Date of last release:
XXXX-XX-XX
When were the last committers or PPMC members elected?
Signed-off-by:
[ ](gossip) P. Taylor Goetz
Comments:
[ ](gossip) Josh Elser
Comments:
[
Forwarding my +1 (binding)
On 10/2/17 12:38 PM, David Lotts wrote:
The Apache Rya community has voted and approved the proposed release of
Apache Rya 3.2.11 (Incubating) RC3.
We now kindly request the Incubator PMC members review and vote on
this incubator
release.
Rya (pronounced "ree-uh" /rē
+1 (binding)
(going to try to avoid repeating issues Justin has already done)
* L&N look OK
* License headers look good
* DISCLAIMER is present
* Incubating in name
* Can build from src
On 8/15/17 8:49 PM, DO YUNG YOON wrote:
Hi all
This is a call for a releasing Apache S2Graph 0.2.0-incubati
+1 (binding)
It looks like you're missing a Copyright propagation for work by Trevor
Robinson in your NOTICE file. The license headers are for ASL (you are
correct to have omitted this from LICENSE), but I believe you still need
to propagate the copyright notice to your NOTICE in the src relea
+1 (despite being lazy-consensus because I'm really glad to see this
happening!)
On 7/28/17 2:22 PM, Julian Hyde wrote:
Apache Calcite is receiving a code for an Avatica driver written in Go.
See http://incubator.apache.org/ip-clearance/calcite-avatica-go.html
and https://issues.apache.org/jir
To clarify just in case it's not clear (I had to read it twice to get
it): notifications@f.a.o[1] is what Christopher meant by "the
notifications list" and is probably the discussion you're looking for,
Bertrand :)
[1] https://lists.apache.org/list.html?notificati...@fluo.apache.org
On 7/10/1
OLVED, that the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache Fluo Project:
* Billie Rinaldi
* Chris McTague
* Christopher Tubbs
* Corey J. Nolet
* Drew Farris
* Josh Elser
* Keith Turner
* Mike Walch
NOW, THEREFORE, BE IT FURTHER
Thanks, John. Consider this mentor +1 then.
On 7/5/17 7:03 PM, John D. Ament wrote:
For what it's worth, I have no concerns with Fluo's graduation based on the
conversation here.
John
On Wed, Jul 5, 2017 at 7:02 PM Josh Elser wrote:
On 7/5/17 1:51 PM, Dave Fisher wrote:
Hi Jos
On 7/5/17 1:51 PM, Dave Fisher wrote:
Hi Josh,
I have some questions:
On Jul 5, 2017, at 10:18 AM, Josh Elser wrote:
As a mentor, I consciously avoided an explicit "+1" until we got some IPMC
discussion. Let me expand:
The current members of Fluo are great, get the Apache Wa
the persons listed immediately below be and hereby are
appointed to serve as the initial members of the Apache Fluo Project:
* Billie Rinaldi
* Chris McTague
* Christopher Tubbs
* Corey J. Nolet
* Drew Farris
* Josh Elser
* Keith Turner
* Mike Walch
NOW, THEREFORE, BE IT FURTHER RESOLVED, that
and suggestion, Yes it makes sense to construct a set of pure Java memory services as fallback for the experience of first users. we would add this feature to Mnemonic later, Thanks!
Best Regards
Gary
(323)801-6286 (WhatsApp)
-Original Message-----
F
+1 (binding)
- xsums/sigs OK
- L&N look ok
- KEYS is good
- Could sort of build from source. On OSX, I can only get so far into
the build until I start running into native compilation failures. The
docs are a little sparse on this -- it would be awesome if there was
some non-native fallback me
+1 (binding)
All of the normal checks and can build from source.
On 6/19/17 1:49 PM, Keith Turner wrote:
Dear IPMC,
Please vote for the following release candidate of Apache Fluo Recipes
1.1.0-incubating.
PPMC vote threads:
https://lists.apache.org/thread.html/4c99f51ef5302506f518d692ff9d65a1
+1 (binding)
You must update the KEYS file in dist/release/incubator/tamaya [1]
before you release 0.3-incubating. It does not contain your signing key
(only dist/dev/incubator/tamaya/KEYS does).
* MD5 and SHA512 are good, sig is ok too
* commit exists in SCM, please include the SHA1 in the V
On 6/15/17 1:11 PM, Oliver B. Fischer wrote:
Please note:
This vote is a "majority approval" with a minimum of three +1 votes and
no -1’s (see [4]).
Just wanted to point out that your description of majority approval is
wrong. You need at least 3 +1's and more +1's than -1's. -1's are not
v
+1 (binding)
Forwarded from the ppmc VOTE thread.
On 6/6/17 4:15 PM, Keith Turner wrote:
Dear IPMC,
Please vote for the following release candidate of Apache Fluo
1.1.0-incubating.
PPMC vote thread:
https://lists.apache.org/thread.html/c815b7a22fab10281ab2d4e88418a47a5903ba85327058bb727c7ccd@
+1 (binding)
* Make sure https://dist.apache.org/repos/dist/dev/incubator/weex/KEYS
exists at https://dist.apache.org/repos/dist/release/incubator/weex/KEYS.
* Would recommend sha512 instead of sha1 for the future.
* Ran into an issue with node-7.7.4, upgrade to 8 seems to have gotten
past tha
+1 (binding)
* xsums/sigs OK
* DISCLAIMER present
* LICENSE looks good
* NOTICE file has some unnecessary stuff, IMO:
- "In addition, this product includes software dependencies. See the
accompanying LICENSE.txt for a listing of dependencies that are NOT
Apache licensed (with pointers to their
think a README would be a better name for the explanatory file.
On Fri, Jun 2, 2017 at 11:20 PM, James Bognar
wrote:
Thanks!
I haven't found a metadata editor that works yet, so I'll just add a
LICENSE.txt file to the directory. Hopefully that's enough.
On Fri, Jun 2, 2017
On 6/2/17 1:15 PM, James Bognar wrote:
I just added several png files to the source tree of our podling. I
created them myself. Are there any best-practices on how to mark these as
Apache licensed?
I'm not sure of a good way to track this. I'm not sure if png supports
arbitrary metadata whi
+1 (binding)
* sig/xsums OK
* NOTICE ok, LICENSE is good enough (see below)
* DISCLAIMER present
* Incubating is in artifact name
* Can build from source and could run tests
* All of your additions to LICENSE (over "stock") are unnecessary. The
trap you fell into is differentiating between what
+1 (binding)
* Please use sha512 in the future instead of sha1
* You probably didn't want to include pom.xml.releaseBackup and
release.properties in the src release
* Just above the node_modules section in LICENSE, you have some license
text with no context on what it applies to...
* DISCLAIME
+1 (binding)
* L&N look great (good job!)
* xsums/sigs are good (including your signing key in this message isn't
a bad idea)
* Could build from source (python setup.py build)
* Commit is in Git
* DISCLAIMER present
* Website looks nice too
Chris Riccomini wrote:
Hello Incubator PMC’ers,
The
To the best of my knowledge, the Pirk podling should be cleaned up.
INFRA plowed through the last administrative acts as outlined on the
retirement guide.
If I've missed anything, please let me know and I'll circle back around.
- Josh
Josh Elser wrote:
Just wanted to give a heads
To avoid disclosing the name included in the subject, here is a
permalink to the RESULT message for a VOTE for a new committer sent by
Adam Feng at 2017-04-24 02:51 (-0400).
https://lists.apache.org/thread.html/c26b89e59557ae8793bac1eddeb9d03bfa3e4203da0e50face55193b@%3Cprivate.weex.apache.org%
https://issues.apache.org/jira/browse/INFRA-13913
Josh Elser wrote:
The vote to retire Pirk passes with six binding +1's and one non-binding
+1.
Thanks folks. Will push the podling through the retirement steps.
Josh Elser wrote:
Folks,
The Pirk PPMC have recently voted unanimously to retire the pod
The vote to retire Pirk passes with six binding +1's and one non-binding +1.
Thanks folks. Will push the podling through the retirement steps.
Josh Elser wrote:
Folks,
The Pirk PPMC have recently voted unanimously to retire the podling.
This decision, while heavy-hearted, comes on the
Oops, I forgot to a duration: this vote will be open for the standard
72hrs (at least until ~2016/04/17 0600).
I should have known better to email late at night :)
On Thu, Apr 13, 2017 at 11:25 PM, Josh Elser wrote:
> Folks,
>
> The Pirk PPMC have recently voted unanimously to r
Folks,
The Pirk PPMC have recently voted unanimously to retire the podling.
This decision, while heavy-hearted, comes on the tails of months of no
development with no change on the horizon.
Context for those interesting in reading: DISCUSS [1], VOTE [2], RESULT [3].
[ ] +1: Retire Pirk
[ ] -1: D
Also, it may be worth mentioning: Metron is on its way out of the Apache
Incubator. A vote has recently passed at the Incubator level for their
graduation. It is likely that after the next ASF board meeting, Metron
will no longer be a podling.
I am worried that you did not receive a response f
Marvin Humphrey wrote:
On Mon, Apr 10, 2017 at 2:28 PM, Henry Saputra wrote:
The question is whether we need to keep this section:
Portions of this software were developed by Twitter.
Copyright Twitter, 2017
in the NOTICE file. Since Twitter already signed off the source
contributions, we cou
Marvin Humphrey wrote:
On Sun, Apr 9, 2017 at 3:40 PM, Josh Elser wrote:
- hide quoted text -- show quoted text -
> * It looks like your NOTICE file can be essentially encapsulated by
> the LICENSE file. If the only "text" you're adding to the NOTICE
>
-1 (binding) your source releases still do not contain the DISCLAIMER
file that John pointed out in rc2 [1].
* mvn apache-rat:check fails on `src/main/resources/DISCLAIMER.bin.txt`
* Don't include 'Copyright 2017 The Apache Software Foundation' in the
license headers of your source files. The N
+1 (binding)
You must add your GPG key to [1] before promoting this release.
* xsums/sigs OK
* DISCLAIMER present
* It looks like your NOTICE file can be essentially encapsulated by the
LICENSE file. If the only "text" you're adding to the NOTICE file is a
copyright text, you can just include
Mike Jumper wrote:
* guacamole-auth-header includes some copies of ALv2 and mentions in your
> LICENSE file. You only need to propagate the copyright notice here, not the
> license text (since you already have that once). Looks like this might be
> the case around the binary tarballs.
>
>
Are
+1 (binding)
* Could build the client, but I don't have a setup to build the server
* DISCLAIMER in every artifact
* Sufficient LICENSE & NOTICE files. Even in the WAR! Good job :)
* Commits exist in SCM
* Sigs/xsums OK
In the future:
* Your copyright in NOTICE files needs updating (2017)
* Doc
+1 (binding)
Casey Stella wrote:
Hi Everyone,
I propose that we graduate Apache Metron (incubating) from the incubator.
The full text of the proposal is below, with requisite modifications
applied from the discussion thread.
The discuss thread can be found at
https://lists.apache.org/thread.ht
+1 (binding)
* xsums/sigs OK
* Could build src and pip tarballs
* L&N look OK with caveats
* DISCLAIMER present
While I appreciate the obvious effort that went into the assembly of
your LICENSE file, there are some issues:
* The Copyright clauses are disjoint from the bundled software. How do
+1 from my limited interactions.
I've had a few run-ins with the Metron crowd (winks) over the last year
or so via IPMC votes. They've always been nice to work with and have
shown positive responses from any release-time issues (e.g.
licensing/branding).
Casey Stella wrote:
Hi Everyone,
Th
Fwding +1 (binding) from ppmc list.
On Mar 21, 2017 21:47, "Marc Spehlmann" wrote:
> The Apache Incubator Quickstep community has approved a vote to release
> Quickstep-0.1.0 RC7. Quickstep is a high performance relational database
> system built from the ground up for modern hardware.
>
> We ha
+1
John D. Ament wrote:
All,
Before I go ahead with it, wanted to see if others had any opinions. I'm
planning to ask infra to create a podlings@i.a.o mailing list, which would
go to all podlings dev@ list. There may be some scenarios where we need to
communicate out to all podlings. For ins
Switching this to a +1 (binding)
"sjanc" on IRC was able to point me in the right direction enough to
make me (think) that I have compiled everything from source :) (at least
for one target)
This would be a good area to include some clarity in the docs.
Josh Elser wrote:
+0 (bin
+0 (binding)
* L&N pretty good (caveat below)
* sigs/xsums OK
* Was able to build all but mynewt-core (thus the +0). Am still trying
to figure this out so I can switch to a +1.
* Didn't see any binaries in source release(s)
* DISCLAIMER is present
* Website has incubator reference
* incubating
+1 (binding)
* xsums/sigs OK
* rat check passed and can build from src (for both projects)
* Spot checked included files
* Commit is published in scm
* DISCLAIMER is OK
* L&N seem appropriate
* Spot checked dependencies
One suggestion for the future is to prune your RAT plugin
configurations' e
I'm so sorry, Marc.
I didn't want to force you to have to roll another RC after the LEGAL
issue John pointed out -- re-reading my last message, I didn't clearly
state my intent to switch my vote from -1 to +1 (I'll blame that on
being under the weather).
Marc Spehlmann wrote:
Hello IPMC,
T
Ugh, sorry for the duplicate votes folks...
Josh Elser wrote:
Fwd'ing my +1 (binding) from the ppmc
Edward Capriolo wrote:
I am pleased to call an IPMC vote for gossip-0.1.2-incubating.
The PPMC vote thread is here:
https://lists.apache.org/thread
Fwd'ing my +1 (binding) from the ppmc
Edward Capriolo wrote:
I am pleased to call an IPMC vote for gossip-0.1.2-incubating.
The PPMC vote thread is here:
https://lists.apache.org/thread.html/5571d2996633f3a7ed10f3b0de3366702027db3b2f7870403c390141@%3Cdev.gossip.apache.org%3E
Additionally a de
or the next release.
Here's a link to how to assemble the LICENSE contents, in case you need it:
http://www.apache.org/dev/licensing-howto.html#permissive-deps
John
On Thu, Mar 16, 2017 at 6:49 PM Josh Elser wrote:
Marc Spehlmann wrote:
Thank you for reviewing Apache Quickstep 0.1.0 rc6 (i
Marc Spehlmann wrote:
Thank you for reviewing Apache Quickstep 0.1.0 rc6 (incubating), everyone.
With this I will close the vote.
+1
Julian (binding)
Jignesh
-1
Josh (binding)
As we received one -1 binding vote, we will not release rc6.
___
The biggest issue seems to be our licensing check
-1 (binding)
* xsums/sigs OK
The key you provided isn't the one that was used to sign this release,
FYI. You have D280F52E up on your people space, but used 5A29899A to
sign this release.
* Artifact starts with "apache-quickstep" and includes "incubating"
* DISCLAIMER present
* Missing LICEN
+1 (binding)
* xsums/sigs OK -- might want to start including sha256
* Spot-checked L&N
* DISCLAIMER present
* Can build from source
* `mvn apache-rat:check -Prat` passes
* Spot-checked the list of included files
Sorry I missed this VOTE while on the podling list :). Thanks, Gour!
- Josh
Gour
Forwarding my +1 (binding) from the dev@ list.
Edward Capriolo wrote:
I am pleased to call an IPMC vote for gossip-0.1.2-incubating.
The PPMC vote thread is here:
https://lists.apache.org/thread.html/5571d2996633f3a7ed10f3b0de3366702027db3b2f7870403c390141@%3Cdev.gossip.apache.org%3E
Addition
+1 (binding)
First off, sorry for the delay on voting.
Let me also clarify that, at the time of this vote,
apache-metron-0.3.1-rc5-incubating was pointing to
7abd7e8a231c6cbe9ee4ab23a5df1e97344f5212. It's good to use the commit ID
instead of the tag name (as the latter is mutable whereas the
(so sorry, I think my fingers got a little antsy and sent a blank reply)
+1 on #1
+1 on #2 given the clarification later in the thread.
+1 on #3. I don't view it as a burden to leave a comment. Most of the
time, I can just parrot events I was involved with, or a slightly more
detailed version o
IMO, it prevents a one-line release command for Maven projects using the
standard conventions (I'm blindly assuming is Maven is the most common
tool used). However, I can also see where Justin is coming from with the
provenance side of things (the disconnect between what was voted on and
what g
Release this package?
[ ] +1 yes
[ ] +0 no opinion
[ ] -1 Do not release this package because because...
Thank you,
Edward
Below is a copy of the [RESULT] for voting:
-
The vote for gossip-0.1.1-incubating (RC2) has passed.
Josh Elser +1
P. Taylor Goetz +1
Gary Dusbabek +1
Chandresh Pancholi
1 - 100 of 186 matches
Mail list logo
