RE: [CRYPTO] Git repository requested

2016-04-12 Thread Chen, Haifeng
The git repository for Apache Commons Crypto has been created. It is locked so commits won't be accepted for now, will inform Daniel when we want the lock lifted. https://git-wip-us.apache.org/repos/asf?p=commons-crypto.git Next we may need to setup a JIRA project and the initial committers. Tha

Re: Git not suitable for dist repo (was: Whatever happened to commons-io 2.5?)

2016-04-12 Thread Torsten Curdt
Not completely true http://stackoverflow.com/questions/600079/is-there-any-way-to-clone-a-git-repositorys-sub-directory-only

Re: [VOTE] Release commons-io 2.5 based on RC4

2016-04-12 Thread Benson Margulies
I built this wrong. Please consider this vote [CANCELLED]; I'll try again and post another vote. I misunderstood the web page the first time about how you deal with RC status and the maven-release-plugin. On Tue, Apr 12, 2016 at 9:12 AM, Benson Margulies wrote: > I'm working on moving the stuff

Re: [VOTE] Release commons-io 2.5 based on RC4

2016-04-12 Thread Benson Margulies
I'm working on moving the stuff to dist. I'm working on 'home'. On Tue, Apr 12, 2016 at 8:16 AM, sebb wrote: > On 12 April 2016 at 12:42, Benson Margulies wrote: >> We have fixed quite a few bugs and added some significant enhancements >> since Commons IO 2.4 was released, >> so I would lik

a problem with staging the site

2016-04-12 Thread Benson Margulies
I posted the vote, and then realized that I don't understand how to stage the site with the changes to people.apache.org. I'm also puzzled that this isn't all being done via the CMS. I used lftp and pushed the tree, but it isn't showing up when visited from a browser. ---

Re: Whatever happened to commons-io 2.5?

2016-04-12 Thread sebb
On 12 April 2016 at 13:14, Stian Soiland-Reyes wrote: > Right, dist is just using SVN as a convenient way to manage the > distribution tree for the download mirrors, that it is version controlled > is a nice side effect, it would not work well with Git (except possibly > with LFS) as every binary

Re: [VOTE] Release commons-io 2.5 based on RC4

2016-04-12 Thread sebb
On 12 April 2016 at 12:42, Benson Margulies wrote: > We have fixed quite a few bugs and added some significant enhancements > since Commons IO 2.4 was released, > so I would like to release Commons IO 2.5. > > NOTE: because this is just an RC, and because I'm not a PMC member, > I'm pointing to

Re: Whatever happened to commons-io 2.5?

2016-04-12 Thread Stian Soiland-Reyes
Right, dist is just using SVN as a convenient way to manage the distribution tree for the download mirrors, that it is version controlled is a nice side effect, it would not work well with Git (except possibly with LFS) as every binary and source release of ASF since the dist repos inception is in

Re: [VOTE] Release commons-io 2.5 based on RC4

2016-04-12 Thread sebb
On 12 April 2016 at 12:47, Mark Thomas wrote: > On 12/04/2016 12:42, Benson Margulies wrote: >> We have fixed quite a few bugs and added some significant enhancements >> since Commons IO 2.4 was released, >> so I would like to release Commons IO 2.5. >> >> NOTE: because this is just an RC, and b

Re: [VOTE] Release commons-io 2.5 based on RC4

2016-04-12 Thread Mark Thomas
On 12/04/2016 12:42, Benson Margulies wrote: > We have fixed quite a few bugs and added some significant enhancements > since Commons IO 2.4 was released, > so I would like to release Commons IO 2.5. > > NOTE: because this is just an RC, and because I'm not a PMC member, > I'm pointing to the re

[VOTE] Release commons-io 2.5 based on RC4

2016-04-12 Thread Benson Margulies
We have fixed quite a few bugs and added some significant enhancements since Commons IO 2.4 was released, so I would like to release Commons IO 2.5. NOTE: because this is just an RC, and because I'm not a PMC member, I'm pointing to the release on Nexus rather than copying it to dist. If this is

Re: Whatever happened to commons-io 2.5?

2016-04-12 Thread Mark Thomas
On 11/04/2016 22:52, Benson Margulies wrote: > First Karma issue: > > SendingKEYS > Transmitting file data .svn: E195023: Commit failed (details follow): > svn: E195023: Changing file '/Users/benson/asf/commons/KEYS' is > forbidden by the server > svn: E175013: Access to > '/repos/dist/!sv