https://issues.apache.org/jira/browse/LEGAL-256 is created and commented to
track this.
If we think this analysis makes sense, we will choose to go ECCN 5D002
self-classify category. Will wait for a few days for feedbacks.
Regards,
Haifeng
-Original Message-
From: Chen, Haifeng
+1 Congrats!
Sergio Fernández wrote:
congrats, Stian!
On May 25, 2016 6:11 PM, "Stian Soiland-Reyes" wrote:
Done - now live on
http://commons.apache.org/team-list.html
Do I need to do something special to get Jira admin access? (e.g. to
manage Versions)
On 24 May 2016
+1 wfm
Bernd Eckenfels wrote:
Hello,
I would like to be able to use Git with the Apache Commons VFS repo. As
we agreed upon I call out the intention to do this and ask you for your
oppinion.
Now that we have the 2.1 release out of the way the switch wont affect
any planned steps.
Anybody
On Wed, May 25, 2016 at 1:31 PM, Bernd Eckenfels
wrote:
> +1 (binding)
>
> i do have some remarks/discussion points:
>
> RELEASE-NOTES.txt contains the site link as http instead of https, I
> had the impression we wanted to switch the defaults?
>
> Is the site planned to
On Wed, May 25, 2016 at 4:20 PM, Bernd Eckenfels wrote:
> Hello,
>
> I would like to be able to use Git with the Apache Commons VFS repo. As
> we agreed upon I call out the intention to do this and ask you for your
> oppinion.
+1
Woonsan
>
> Now that we have the 2.1
On Wed, May 25, 2016 at 10:42 AM, Stian Soiland-Reyes
wrote:
> Thanks for preparing this release candidate, Gary!
>
> My vote: +1 (binding)
>
> Tested:
>
> +1 signatures, hashes
> +1 sources-jar vs src.zip
> +1 mvn clean install
> +1 mvn apache-rat:check
> +1 LICENSE, NOTICE
Hi All:
It would be nice if components would be consistent in their use
of Checkstyle with LICENSE-header.txt vs. RAT.
Should we just forgo the use of LICENSE-header.txt and rely on RAT 100%?
The following components contain a LICENSE-header.txt:
commons-beanutils
commons-chain
commons-codec
On Wed, May 25, 2016 at 1:20 PM, Bernd Eckenfels
wrote:
> Hello,
>
> I would like to be able to use Git with the Apache Commons VFS repo. As
> we agreed upon I call out the intention to do this and ask you for your
> oppinion.
>
+1
Gary
>
> Now that we have the 2.1
On Wed, May 25, 2016 at 9:37 AM, Stian Soiland-Reyes
wrote:
> On 25 May 2016 at 05:20, Gary Gregory wrote:
> > Apache Commons CSV 1.4 RC2 is available for review here:
> >
> > https://svn.apache.org/repos/asf/commons/proper/csv/tags/csv-1.4-RC2
> >
+1 (binding)
i do have some remarks/discussion points:
RELEASE-NOTES.txt contains the site link as http instead of https, I
had the impression we wanted to switch the defaults?
Is the site planned to be "rolled back" to 1.3.2 or will it stay
1.4-SNAPSHOT?
Gruss
Bernd
Am Mon, 23 May 2016
Hello,
I would like to be able to use Git with the Apache Commons VFS repo. As
we agreed upon I call out the intention to do this and ask you for your
oppinion.
Now that we have the 2.1 release out of the way the switch wont affect
any planned steps.
Anybody opposed to this move? I will
Hello Gary,
Build fine from sources with:
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T17:41:47+01:00)
Maven home: /usr/local/Cellar/maven/3.3.9/libexec
Java version: 1.8.0_65, vendor: Oracle Corporation
Java home:
Hi,
Stian Soiland-Reyes schrieb am Mi., 25. Mai 2016 um
18:11 Uhr:
> +1 for a general move to git, even if it is done one-by-one by lazy
> consensus.
>
> I guess on moving, INFRA do not need to remove the old mirrored
> repository in GitHub? (It should be mirrored form the
Benedikt Ritter schrieb am Mi., 25. Mai 2016 um
19:35 Uhr:
> I can grant you the necessary karma when I'm back to my machine.
>
I have added you to the commons-developers group.
>
>
> Benedikt
>
> Stian Soiland-Reyes schrieb am Mi., 25. Mai 2016 um
>
On May 25, 2016 9:13 AM, "Stian Soiland-Reyes" wrote:
>
> Agree, we should try to avoid including test-data that requires
> attribution - users of Commons CSV will then seemingly have to
> propagate the NOTICE when the data is not used at runtime.
>
> Is there a reason why we
On May 25, 2016 9:11 AM, "Stian Soiland-Reyes" wrote:
>
> +1 for a general move to git, even if it is done one-by-one by lazy
consensus.
>
> I guess on moving, INFRA do not need to remove the old mirrored
> repository in GitHub? (It should be mirrored form the same location).
>
Thanks for preparing this release candidate, Gary!
My vote: +1 (binding)
Tested:
+1 signatures, hashes
+1 sources-jar vs src.zip
+1 mvn clean install
+1 mvn apache-rat:check
+1 LICENSE, NOTICE (thanks!)
+1 RELEASE-NOTES
0 Confusing file LICENSE-header.txt should not be in the src dist
+1 mvn
I can grant you the necessary karma when I'm back to my machine.
Benedikt
Stian Soiland-Reyes schrieb am Mi., 25. Mai 2016 um
18:11:
> Done - now live on
>
> http://commons.apache.org/team-list.html
>
>
> Do I need to do something special to get Jira admin access? (e.g. to
>
On 25 May 2016 at 05:20, Gary Gregory wrote:
> Apache Commons CSV 1.4 RC2 is available for review here:
>
> https://svn.apache.org/repos/asf/commons/proper/csv/tags/csv-1.4-RC2
> (revision 1745420)
Did you mean:
My vote: +1 (binding)
FYI - dist sha1 checksums according to svn r13750
6650d1c878b1142a0c8e3be3534ad24d6f422fc2
binaries/commons-fileupload-1.3.2-bin.tar.gz
0d1004f3aab4ecc62b2fb14056b9c92489d79121
binaries/commons-fileupload-1.3.2-bin.zip
6f254ad51f5e2c9d9a039995bc1a2295cabc95f6
Agree, we should try to avoid including test-data that requires
attribution - users of Commons CSV will then seemingly have to
propagate the NOTICE when the data is not used at runtime.
Is there a reason why we can't create equivalent test-CSV files (use
the same syntax and escapes), or is the
Done - now live on
http://commons.apache.org/team-list.html
Do I need to do something special to get Jira admin access? (e.g. to
manage Versions)
On 24 May 2016 at 20:20, Gary Gregory wrote:
> Stian,
>
> You should add yourself as a PMC member here:
>
+1 for a general move to git, even if it is done one-by-one by lazy consensus.
I guess on moving, INFRA do not need to remove the old mirrored
repository in GitHub? (It should be mirrored form the same location).
Otherwise we need to be worried about open pull requests, link to
forks, etc.
We
The Apache CommonsRDF team is proud to announce the latest release of Apache
CommonsRDF 0.2.0.
Apache BroCommons RDF aims to provide a common library for RDF 1.1 that
could be implemented by systems on the Java Virtual Machine. More details
can be found at https://commonsrdf.incubator.apache.org/
On Wed, May 25, 2016 at 1:07 PM, Benedikt Ritter wrote:
> I think the tag got created when Jochen played around with the
> maven-release-plugin. I didn't notice when I created the RC we're currently
> voting for. The tag can probably be dropped, since it has never been used.
Gary Gregory schrieb am Di., 24. Mai 2016 um
23:03 Uhr:
> I think we have to do 1-by-1 with infra anyway but I'd prefer to do it all.
> My guess from recollections from previous email threads is that folks would
> rather do this 1-by-1. You could start a [POLL] thread.
>
Hello,
sebb schrieb am Mi., 25. Mai 2016 um 00:34 Uhr:
> On 24 May 2016 at 08:32, wrote:
> > Author: jochen
> > Date: Tue May 24 07:32:56 2016
> > New Revision: 1745314
> >
> > URL: http://svn.apache.org/viewvc?rev=1745314=rev
> > Log: (empty)
>
> What's
My +1 for this release.
Benedikt Ritter schrieb am Mo., 23. Mai 2016 um
17:23 Uhr:
> It has been a long time since the last release of Apache Commons
> FileUpload, so I'd like to release Apache Commons FileUpload 1.3.2 based on
> RC1.
>
> Apache Commons FileUpload 1.3.2 RC1
On 25 May 2016 at 00:13, Gary Gregory wrote:
> On Tue, May 24, 2016 at 3:29 PM, sebb wrote:
>
>> On 24 May 2016 at 23:14, Gary Gregory wrote:
>> > Ok, so maybe I just exclude these files from the release and add some
>> > Assume
29 matches
Mail list logo