[lang] Re: releasing maintenance 2.2.1

Although it may be on the wrong list it probably is a good question for the git discussion regarding commons lang. When Log4j 2 switched to git we didn’t have all the details for doing a release worked out. It turned out it wasn’t too much different than what we were doing with SVN, especially

Re: [lang] Re: releasing maintenance 2.2.1

Am Fri, 6 Mar 2015 16:03:53 -0700 schrieb Ralph Goers ralph.go...@dslextreme.com: Although it may be on the wrong list it probably is a good question for the git discussion regarding commons lang. When Log4j 2 switched to git we didn’t have all the details for doing a release worked out. It

Re: [VOTE] Release BCEL 6.0 based on RC3

On 06/03/2015 21:05, Sarah Murray wrote: - 187 https://issues.apache.org/jira/browse/BCEL-187 - has a test case. no committer review for 2 months Neither has anyone else reviewed it. It isn't just committers that can review patches. I've got the necessary commit karma and after looking at

Re: [VOTE] Release BCEL 6.0 based on RC3

Thanks for taking the time to review those patches Mark. I guarantee you that Mark and Jerome do not know that their patches are considered difficult to review in a timely manner. The last comment on all of their patches is from them and they're waiting for a response. If the issues are

Re: [io] support for additional character sets needed in ReversedLinesFileReader

Hi sebb and all, Here’s a revised proposed addition to ReversedLinesFileReader to support the CCJK Windows code pages: ... } else if(charset == Charset.forName(Shift_JIS) || // Same as for UTF-8 http://www.herongyang.com/Unicode/JIS-Shift-JIS-Encoding.html charset ==

Re: releasing maintenance 2.2.1

Yep, sorry! Gary On Fri, Mar 6, 2015 at 12:32 AM, Benedikt Ritter brit...@apache.org wrote: Was this supposed to go to log4j? 2015-03-06 0:45 GMT+01:00 Gary Gregory garydgreg...@gmail.com: Ralph, How much work is it to cut an RC and push out a release for you ATM? Are the

Re: [VOTE] Release BCEL 6.0 based on RC3

+100 to RERO. +1000 to release before we're all dead. It's been a decade people. Just cut a release already. You can always cut another one later. Stop with the excuses Whatever you want to call it - alpha, beta, RC, final, anything. Java 8 users are left in a lurch. Compiling libraries is not a

Re: [VOTE] Release BCEL 6.0 based on RC3

All, This is a community of volunteers. If you want to see something happen, demanding that other people do something is not the way to achieve your aims. At best your demands will have no impact. At worst, they will irritate folks that might have otherwise done the very thing you want to see

Re: [LANG] Handling LANG-1086 (Was: Re: svn commit: r1661762 - in /commons/proper/lang/trunk/src: changes/ main/java/org/apache/commons/lang3/concurrent/ test/java/org/apache/commons/lang3/concurrent/

Am 06.03.2015 um 08:51 schrieb Benedikt Ritter: 2015-03-05 22:00 GMT+01:00 Oliver Heger oliver.he...@oliver-heger.de: Am 03.03.2015 um 08:35 schrieb Benedikt Ritter: 2015-03-02 21:34 GMT+01:00 Oliver Heger oliver.he...@oliver-heger.de: Am 02.03.2015 um 07:23 schrieb Benedikt Ritter:

Re: [VOTE] Release BCEL 6.0 based on RC3

Sorry for the frustration I expressed. It was probably not the most constructive way to voice my opinion. A well described bug with a patch and a test case tends to get committed very quickly. I'm not sure you've looked at the issue tracker lately. This really isn't true as far as I can see,

Re: releasing maintenance 2.2.1

Was this supposed to go to log4j? 2015-03-06 0:45 GMT+01:00 Gary Gregory garydgreg...@gmail.com: Ralph, How much work is it to cut an RC and push out a release for you ATM? Are the instructions up to date? Just curious as to opinions as to when we should release a maintenance release.