Github user asfgit closed the pull request at:
https://github.com/apache/commons-rdf/pull/51
---
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Github user wikier commented on the issue:
https://github.com/apache/commons-rdf/pull/51
VOTE passed, see:
https://lists.apache.org/thread.html/c7440213bd41f9839fdce7aab957e686a954affdf5378ff40ea23dbe@%3Cdev.commons.apache.org%3E
---
GitHub user wikier opened a pull request:
https://github.com/apache/commons-rdf/pull/51
0.5.0 Release Candidate
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/apache/commons-rdf 0.5.0-RC
Alternatively you can review and apply
Hi Gary,
Am Fri, 22 Dec 2017 12:34:13 -0700 schrieb Gary Gregory:
> Hi Jörg,
>
> Thank you for taking the time to review.
>
> The -sources jar are built by 'mvn deploy' I believe.
We should change the parent and tie this goal to package phase. That phase is
supposed to produce anything
that
+1
Works fine for me building from source with my compiler zoo from Java 1.7 to 9.
-Cheers,
Jörg
Am Thu, 21 Dec 2017 11:23:10 -0700 schrieb Gary Gregory:
> We have fixed quite a few bugs and added some enhancements since Apache
> Commons DBCP 2.1.1 was released, so I would like to release
Hi,
This VOTE passes with 3 +1 VOTEs from the following PMC members:
- Gary Gregory
- Jörg Schaible
- Bruno P. Kinoshita
In addition, thank you to the following for casting 3 +1 non-binding VOTEs:
- Aaron Coburn
- Adam Soroka
- Sergio Fernández
I will proceed with the release.
Thank you all,
Yeah, we'll try to prepare a 0.6 release to verify all those missing
details before moving to 1.0 somewhen in 2018.
Thanks for all the votes! I'll send inmediatelly the result mail.
On Thu, Dec 21, 2017 at 11:05 AM, Bruno P. Kinoshita
wrote:
> +1 didn't take into
+1 (non-binding)
So far I've checked:
* signatures and digests
* source releases file layouts,
* matched git tag and commit ids
* NOTICE and LICENSE files
* license headers
* build sources in a clean environment (Maven 3.5.0, OpenJDK 1.8.0_144
64-Bit, Debian amd64)
On Thu, Dec 21, 2017 at
On Fri, Dec 22, 2017 at 5:23 PM, Bruno P. Kinoshita <
brunodepau...@yahoo.com.br.invalid> wrote:
> Hi Gary,
>
> Thanks for the advice. It worked.
>
>
[ X ] +1 Release these artifacts
>
Thanks Bruno, I am glad you were able to get your build environment cleaned
up!
More reviews and VOTEs please
Hi Gary,
Thanks for the advice. It worked.
[ X ] +1 Release these artifacts
> rm ~/.m2/repository/* -rf
> git clone https://github.com/apache/commons-dbcp.git
> cd commons-dbcp
> git checkout c5b86d834a53b4891487e62671873d054a6f38d8
> mvn -v
Apache Maven 3.5.2
Hi All,
In light of the [math] work being done, does anyone have thoughts on what
should happen to the stat packages? As in stay in [math] or [split] into a
new component or module?
Gary
Hi Jörg,
Thank you for taking the time to review.
The -sources jar are built by 'mvn deploy' I believe. How are they broken
for you?
Gary
On Fri, Dec 22, 2017 at 12:28 PM, Jörg Schaible
wrote:
> Hi,
>
> the build from source is fine for my compiler zoo from Java 1.7 to
Hi,
the build from source is fine for my compiler zoo from Java 1.7 to 9. However,
if the final release contains
broken -sources files, my vote is -1.
Those files are very valuable e.g. developing with Eclipse, because they are
used in the debugger to jump
directly into the source, if you
When can we get a [compress] release? It would be nice to get Zstandard out
there.
Gary
Hello.
Sorry for not replying earlier (and the top-post).
I've a bad feeling about "Field" and "FieldElement" as
they exist in "Commons Math".
I'd like to see whether/how we can do better starting
from "scratch"[1].
I started to make changes in the CM codes but more and
more were necessary
Hi.
[Sorry for not replying earlier; I've been quite diverted
by what happened around the RNG-37 issue[1].]
On Mon, 11 Dec 2017 16:16:34 +, Stephen Colebourne wrote:
This all seems reasonable. One things I'd suggest is getting at least
one new component to a full release as soon as
Very odd indeed.
I would blow away commons pool and commons dbcp from your local Maven repo.
Just in case...
I'd want to see Maven download the pool2 jars.
You can also run Maven in debug mode and make sure it is building the
classpath to run the tests as expected.
Gary
On Fri, Dec 22, 2017
Having the same issue as before when I was testing commons-pool. Some tests are
hanging and the console is just waiting for some threads to finish.
When I complained about this test failure last week while voting on
commons-pool, I went to work and tested it, and it actually worked. For some
18 matches
Mail list logo