+1
I checked:
- DISCLAIMER exists
- NOTICE looks good.
- LICENSE looks good
- License headers present
- Can build from source (though I had to skip tests. I got the same failures as
Josh).
- Signatures/hashes check out.
Nice work on the quick turnaround.
-Taylor
> On Jan 3, 2017, at 3:47 PM,
+1.
Many emails today. I wanted to make sure this one did not get lost in the
shuffle.
On Tue, Jan 3, 2017 at 3:47 PM, Edward Capriolo
wrote:
> I am pleased to be calling this vote for the source release of Apache
> Gossip
>
> Ancillary artifacts such as poms, jars,
Josh is correct that there is some wiggle room on this specific issue (json.org
license). The wiggle room is that existing projects have a grace period for
removing the json.org dependency, with the deadline I think being June 2017.
Since Gossip has yet to make a release, I would lean toward
I am pleased to be calling this vote for the source release of Apache Gossip
Ancillary artifacts such as poms, jars, wars, ect. can be found here:
https://repository.apache.org/content/repositories/orgapachegossip-1002/
The Git commit ID is:
6720f35beb8718ae39018211f33bbff2ac782fb6
No worries I will tackle it today. I did not like the ugly class names hurt
my eyes.
import org.json.JSONObject;
STOP YELLING AT ME JSON!
On Tue, Jan 3, 2017 at 1:26 PM, Drew Farris wrote:
> I may be incorrect here, I need to do some research; The license issue may
> be a
I may be incorrect here, I need to do some research; The license issue may
be a barrier to graduation but may not prevent releases while incubating.
Josh, do you recall offhand?
Drew
On Tue, Jan 3, 2017 at 11:45 AM Josh Elser wrote:
> -1 due to a dependency on a project with
Edward Capriolo wrote:
On Tue, Jan 3, 2017 at 11:45 AM, Josh Elser wrote:
-1 due to a dependency on a project with a category-X license [1].
Gossip is transitively depending on org.json:json via
jackson-datatype-json-org.
```
[INFO]
* The git commit ID is good to see (not just the tag), but linking to
your personal github acct is a little out-of-the-normal to me.
Yes. I plan on pushing that commit to apache git as the tag once the vote
is complete. Normally the maven release WOULD push the tag but we are
voting on the tag
Edward,
Thanks for the release. Generally things looks pretty good. Aside from the
concerns with the vote e-mail Josh already shared, I can't seem to find the
commit referenced by commit id 7413387041 anywhere other than the
edwardcapriolo fork on GitHub. That's the only other showstopper I have
I'm just getting back from a little vacation. If you can hold off on
calling the vote strictly after 72hrs, I'll do my best to look at this
tmrw before it makes its way to the IPMC for a vote.
A couple of remarks on the VOTE email's content:
* The git commit ID is good to see (not just the
+1
On Fri, Dec 30, 2016 at 11:31 AM, Edward Capriolo
wrote:
> I am pleased to be calling this vote for the source release of Apache
> Gossip
>
> Ancillary artifacts such as poms, jars, wars, ect. can be found here:
>
I am pleased to be calling this vote for the source release of Apache Gossip
Ancillary artifacts such as poms, jars, wars, ect. can be found here:
https://repository.apache.org/content/repositories/orgapachegossip-1001
The Git commit ID is:
12 matches
Mail list logo