Re: [VOTE] Release Apache Commons JCS 2.2 based on RC1

[Rob Tompkins]

Signatures look good,

mvn clean site works java 1.7
mvn clean test works 1.6, 1.8 (javadoc blocks site on 1.8)

agreed on Oliver’s nit-picky bits, plus:
- commons-jcs-jcache-openjpa/derby.log shows up in RAT (granted it’s not in the 
build)

I’m a +1.

-Rob

> On Aug 2, 2017, at 9:32 AM, Thomas Vandahl  wrote:
> 
> I would like to release the [jcs] component to resolve some overdue bugs
> 
> Apache Commons JCS 2.2 RC1 is available for review at:
>  https://dist.apache.org/repos/dist/dev/commons/jcs/ (r20728).
> 
> Maven artifacts are at:
>  https://repository.apache.org/content/repositories/orgapachecommons-1256 .
> 
> The Subversion tag is:
> 
> https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2
> (r1803806).
> 
> The release notes are at:
> 
> https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2/RELEASE-NOTES.txt
> (r1803806).
> 
> The staged site is available as a tarball at
> 
> https://dist.apache.org/repos/dist/dev/commons/jcs/commons-jcs-site-2.2.tar.gz
> (r20723).
> 
> Please review the release candidate and vote.
> 
>  [ ] +1 Release these artifacts
>  [ ] +0 OK, but...
>  [ ] -0 OK, but really should fix...
>  [ ] -1 I oppose this release because...
> 
> Bye, Thomas
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: Empty repositories for some retired components on github

[Pascal Schumacher]

Am 14.08.2017 um 09:05 schrieb Benedikt Ritter:

Am 13.08.2017 um 20:24 schrieb Pascal Schumacher:

Hello everybody,

just a small detail.

For some retired components there are still github mirrors (with an empty 
repository):

https://github.com/apache/commons-primitives

https://github.com/apache/commons-betwixt

https://github.com/apache/commons-attributes

Should I create an infra ticket in order to let these mirrors be deactivated?

Yes, let’s do that.


done: https://issues.apache.org/jira/browse/INFRA-14867


We should add that step to our „how to move components to dormant“ 
documentation in the wiki.
https://commons.apache.org/releases/moving-to-dormant.html already 
contains "Ask Infra to deactivate the git mirror ."


Seems like the deletion is not strictly part of the disabling of the 
mirror. To quote from the infra ticket:


"We have to manually remove the repos on Github if a mirror disappears since Github 
won't delete it on it's own. But removed the 3 Github repos and verified we aren't 
mirroring anymore"

Cheers,
Pascal

Re: REMINDER: [VOTE] Release Apache Commons JCS 2.2 based on RC1

[Thomas Vandahl]

On 14.08.17 20:21, Rob Tompkins wrote:
> 
> 
>> On Aug 14, 2017, at 2:15 PM, Thomas Vandahl  wrote:
>>
>> We are one PMC vote short. Please consider voting.
> 
> I can get to validating it tonight 8p (UTC-4). That work?

Of course. Go ahead.

Bye Thomas.

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: REMINDER: [VOTE] Release Apache Commons JCS 2.2 based on RC1

[Rob Tompkins]

> On Aug 14, 2017, at 2:15 PM, Thomas Vandahl  wrote:
> 
> We are one PMC vote short. Please consider voting.

I can get to validating it tonight 8p (UTC-4). That work?

-Rob

> 
>> On 02.08.17 15:32, Thomas Vandahl wrote:
>> I would like to release the [jcs] component to resolve some overdue bugs
>> 
>> Apache Commons JCS 2.2 RC1 is available for review at:
>>  https://dist.apache.org/repos/dist/dev/commons/jcs/ (r20728).
>> 
>> Maven artifacts are at:
>>  https://repository.apache.org/content/repositories/orgapachecommons-1256 .
>> 
>> The Subversion tag is:
>> 
>> https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2
>> (r1803806).
>> 
>> The release notes are at:
>> 
>> https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2/RELEASE-NOTES.txt
>> (r1803806).
>> 
>> The staged site is available as a tarball at
>> 
>> https://dist.apache.org/repos/dist/dev/commons/jcs/commons-jcs-site-2.2.tar.gz
>> (r20723).
>> 
>> Please review the release candidate and vote.
>> 
>>  [ ] +1 Release these artifacts
>>  [ ] +0 OK, but...
>>  [ ] -0 OK, but really should fix...
>>  [ ] -1 I oppose this release because...
>> 
>> Bye, Thomas
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

REMINDER: [VOTE] Release Apache Commons JCS 2.2 based on RC1

[Thomas Vandahl]

We are one PMC vote short. Please consider voting.

On 02.08.17 15:32, Thomas Vandahl wrote:
> I would like to release the [jcs] component to resolve some overdue bugs
> 
> Apache Commons JCS 2.2 RC1 is available for review at:
>   https://dist.apache.org/repos/dist/dev/commons/jcs/ (r20728).
> 
> Maven artifacts are at:
>   https://repository.apache.org/content/repositories/orgapachecommons-1256 .
> 
> The Subversion tag is:
> 
> https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2
> (r1803806).
> 
> The release notes are at:
> 
> https://svn.apache.org/repos/asf/commons/proper/jcs/tags/commons-jcs-2.2/RELEASE-NOTES.txt
> (r1803806).
> 
> The staged site is available as a tarball at
> 
> https://dist.apache.org/repos/dist/dev/commons/jcs/commons-jcs-site-2.2.tar.gz
> (r20723).
> 
> Please review the release candidate and vote.
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
> Bye, Thomas
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [all/travis-ci] Regarding potential Travis-CI solutions

[Amey Jadiye]

Closed PR.

On Mon, Aug 7, 2017 at 2:12 AM, Amey Jadiye  wrote:

> looking at inclination of community I will be closing the PR without
> expecting merge after a week by 14th August 2017 unless someone see it's
> useful.
>
> Reference will be there in closed PR list on github so if someone need it
> in future it will be there.
>
> Regards,
> Amey
>
>
> On Fri, Aug 4, 2017, 3:02 AM Rob Tompkins  wrote:
>
>> Hello all,
>>
>> We have an open pull request from Amey (https://github.com/apache/
>> commons-text/pull/61 )
>> proposing a fairly complicated but quite nice travis-ci build solution
>> (taken from the jacoco project) that accommodates building on JDK7, JDK8,
>> JDK8-ea, EclipseJava, JDK9-ea, as well as IBMJava-8. To accommodate
>> building on all of these different versions of Java, we do however need to
>> make the travis-ci build a good deal more complex.
>>
>> As the two reviewers on the pull request, Pascal and myself, have mildly
>> differing opinions on the complexity-value trade off here, with Pascal’s
>> opinion being: "…[T]his is overkill. I don't think commons-text needs to be
>> tested against the eclipse java compiler and early access versions of java
>> 8 and 9. The script looks difficult to debug and maintain.” And my
>> perspective is that this could be a test piece for using this elsewhere in
>> commons.
>>
>> To me, the argument for simplicity is always quite compelling, to the
>> point that I’m mostly willing to let go of using the jacoco travis-ci
>> pattern. But I figured I would, before making any decisions, see what the
>> community thinks generally about this possible travis-ci build script.
>>
>> Cheers,
>> -Rob
>
>


-- 

-

To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org

For additional commands, e-mail: dev-h...@commons.apache.org

[GitHub] commons-text pull request #61: Added flexible Travis-ci build script.

[ameyjadiye]

Github user ameyjadiye closed the pull request at:

https://github.com/apache/commons-text/pull/61


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[GitHub] commons-text issue #61: Added flexible Travis-ci build script.

[ameyjadiye]

Github user ameyjadiye commented on the issue:

https://github.com/apache/commons-text/pull/61
  
Because of low interest of community adapting this change i'm closing this 
pull request.

http://markmail.org/message/mn2or73hqsz6oxo2


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: Empty repositories for some retired components on github

[Benedikt Ritter]

> Am 13.08.2017 um 20:24 schrieb Pascal Schumacher :
> 
> Hello everybody,
> 
> just a small detail.
> 
> For some retired components there are still github mirrors (with an empty 
> repository):
> 
> https://github.com/apache/commons-primitives
> 
> https://github.com/apache/commons-betwixt
> 
> https://github.com/apache/commons-attributes
> 
> Should I create an infra ticket in order to let these mirrors be deactivated?

Yes, let’s do that. We should add that step to our „how to move components to 
dormant“ documentation in the wiki.

Benedikt

> 
> Cheers,
> 
> Pascal
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [discovery] Move to dormant?

[Benedikt Ritter]

> Am 13.08.2017 um 21:05 schrieb Pascal Schumacher :
> 
> Hello everybody,
> 
> what about moving commons-discovery to dormant?
> 
> Version 0.5 was released in 2011. The last bugfix and feature commits are 
> from 2011. Not a single jira issue has been created since 2011.

+1

> 
> Cheers,
> 
> Pascal
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org