Happy to support you too
Le 19 avr. 2018 00:40, "Rob Tompkins" a écrit :
> Sure. I’ve done it a few times. I can help.
>
> -Rob
>
> > On Apr 18, 2018, at 6:31 PM, Matt Benson wrote:
> >
> > I'd like to migrate this component to git. Will anyone support me to the
> > point that I can start a vot
darkma773r opened a new pull request #1: GEOMETRY-1: Initial Code Commit
URL: https://github.com/apache/commons-geometry/pull/1
Moving over existing geometry code from commons-math.
This is an automated message from the Apach
Sure. I’ve done it a few times. I can help.
-Rob
> On Apr 18, 2018, at 6:31 PM, Matt Benson wrote:
>
> I'd like to migrate this component to git. Will anyone support me to the
> point that I can start a vote to do so?
>
> Thanks,
> Matt
---
I'd like to migrate this component to git. Will anyone support me to the
point that I can start a vote to do so?
Thanks,
Matt
On Wed, Apr 18, 2018 at 11:32 AM, Mark Thomas wrote:
> On 18/04/18 16:21, Gary Gregory wrote:
> > Ignore my previous email ;-) BUT the MAJOR name should be " MAJOR_11"
> since
> > Java has a new versioning scheme. Same for "MAJOR_10" and we should add
> MAJOR_9
> > and deprecate MAJOR_1_9 if is
On 18/04/18 16:21, Gary Gregory wrote:
> Ignore my previous email ;-) BUT the MAJOR name should be " MAJOR_11" since
> Java has a new versioning scheme. Same for "MAJOR_10" and we should add
> MAJOR_9
> and deprecate MAJOR_1_9 if is has been released.
I'll make those changes.
Mark
>
> Gary
>
GitHub user h0l0gram opened a pull request:
https://github.com/apache/commons-validator/pull/11
add Belarus (BY) valid example
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/h0l0gram/commons-validator belarus-test
Alternatively
GitHub user h0l0gram opened a pull request:
https://github.com/apache/commons-validator/pull/10
Add El Salvador (SV)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/h0l0gram/commons-validator trunk
Alternatively you can review a
Ignore my previous email ;-) BUT the MAJOR name should be " MAJOR_11" since
Java has a new versioning scheme. Same for "MAJOR_10" and we should add MAJOR_9
and deprecate MAJOR_1_9 if is has been released.
Gary
-- Forwarded message --
From:
Date: Wed, Apr 18, 2018 at 7:55 AM
Subj
How about for Java 11? Has the format changed in the EA?
Gary
-- Forwarded message --
From:
Date: Wed, Apr 18, 2018 at 7:54 AM
Subject: svn commit: r1829449 -
/commons/proper/bcel/trunk/src/main/java/org/apache/bcel/Const.java
To: comm...@commons.apache.org
Author: markt
Date:
VFS is open for a big update or rewrite. I and others have proposed a
rewrite using the NIO API from Java 7, though there haven't been any
committed efforts that I've seen.
As for it using Subversion, that's mainly because nobody has migrated it to
Git yet. We've been migrating repos one at a time
Is there committer’s guide for VFS ( or any svn based project ) and working
with github PR’s?
Who can review the PRs and +1 them to commit?
If some of these PR *did* actually land, who would do the release?
It seems that VFS is in a ‘maintenance’ state, is that true and official?
Thanks.
ottO
On 13/02/18 09:10, Mark Thomas wrote:
> The following votes were cast:
>
> Binding:
> +1: markt, bodewig, sebb, ebourg, ggregory, oheger, chtompki, ecki
>
> Non-binding:
> +1: rmannibucau
>
>
> Two of the +1 binding votes indicating a preference for Jira rather than
> GitHub issues.
>
> The vo
13 matches
Mail list logo
