Re: [all] Rethinking dev@

On Fri, Jun 24, 2016 at 9:13 PM, Benedikt Ritter wrote: > we should stick to having one mailing list. If a component becomes so > specialized that the PMC fails to follow what is going on (like what > happend with CM), it is time to move that component out of commons. Having

Re: [all] Rethinking dev@

On Jun 24, 2016 12:13 PM, "Benedikt Ritter" wrote: > > Hello, > > we should stick to having one mailing list. If a component becomes so > specialized that the PMC fails to follow what is going on (like what > happend with CM), it is time to move that component out of commons.

Re: [all] Rethinking dev@

Hello, we should stick to having one mailing list. If a component becomes so specialized that the PMC fails to follow what is going on (like what happend with CM), it is time to move that component out of commons. Having separat mailing lists will only make things worse, IMHO. Benedikt Jochen

Is JIRA down?

I am getting a HTTP 500 when trying to access issues.apache.org -- *Raviteja Lokineni* | Business Intelligence Developer TD Ameritrade E: raviteja.lokin...@gmail.com [image: View Raviteja Lokineni's profile on LinkedIn]

Re: [all] Rethinking dev@

On Fri, Jun 24, 2016 at 3:58 PM, Ralph Goers wrote: > Well, it sort of works for the incubator. They are constantly having > discussions about how to do it better. And yes, it could work for us if all > the subprojects have to follow the incubator rules, such as

Re: svn commit: r1750073 - in /commons/proper/bcel/trunk: RELEASE-NOTES.txt src/changes/changes.xml

sebb wrote: > I'm not sure why the svnmailer does not default to UTF-8, but it > clearly doesn't. ??? It seems it does: %< === Content-Type: text/plain; charset=UTF-8 %< === and when I look at %< === >>> >

Re: [all] Rethinking dev@

On Jun 24, 2016 7:41 AM, "Gary Gregory" wrote: > > > On Jun 24, 2016 4:19 AM, "sebb" wrote: > > > > On 24 June 2016 at 12:02, Jochen Wiedmann wrote: > > > On Fri, Jun 24, 2016 at 12:22 PM, Emmanuel Bourg

Re: [all] Rethinking dev@

On Jun 24, 2016 4:19 AM, "sebb" wrote: > > On 24 June 2016 at 12:02, Jochen Wiedmann wrote: > > On Fri, Jun 24, 2016 at 12:22 PM, Emmanuel Bourg wrote: > > > >> I'm -1, because indeed "It didn't work for Jakarta". You can't really

Re: [all] Rethinking dev@

> On Jun 24, 2016, at 2:35 AM, Jochen Wiedmann > wrote: > > Hi, > > given the last weeks, I'd like us to rethink how we work together. > Right now, there is basically only a single place for discussions, and > decisions, which is dev@commons. Okay, we are a common

Re: [compress] Update to Java 7?

I don't think we should need that strong arguments to go to Java 7. Remember being "stuck in the past" with older syntax also puts off potential new contributors and eventually causes code rot. E.g. Commons Compress is very InputStream-centric, and so a try-with-resources could be quite good to

Re: svn commit: r1750073 - in /commons/proper/bcel/trunk: RELEASE-NOTES.txt src/changes/changes.xml

I'm not sure why the svnmailer does not default to UTF-8, but it clearly doesn't. On 24 June 2016 at 13:10, Benedikt Ritter wrote: > Nice, thank you! > > sebb AT ASF schrieb am Fr., 24. Juni 2016 um 12:46 Uhr: > >> Looks like the fix for the encoding was

Re: [compress] Update to Java 7?

On 24 June 2016 at 14:14, Stefan Bodewig wrote: > On 2016-06-24, Gary Gregory wrote: > >> Hi, > >> I was looking at some compress code that I wanted to update to >> switch-on-string but realized the code is still on Java 6. > > "still" means 1.12 has been the first release to

Re: [compress] Update to Java 7?

On 2016-06-24, Gary Gregory wrote: > Hi, > I was looking at some compress code that I wanted to update to > switch-on-string but realized the code is still on Java 6. "still" means 1.12 has been the first release to require Java 6 - 1.11 was at Java 5 :-) > OK to bump to Java 7? If it is

Re: [compress] Update to Java 7?

Le 24/06/2016 à 05:31, Gary Gregory a écrit : > OK to bump to Java 7? I'd rather bump to Java 7 if you intend to leverage the Java 7 APIs, and no just benefiting from the minor syntax changes. Emmanuel Bourg - To unsubscribe,

Re: [compress] Update to Java 7?

+1! On 24 June 2016 at 04:31, Gary Gregory wrote: > Hi, > > I was looking at some compress code that I wanted to update to > switch-on-string but realized the code is still on Java 6. > > OK to bump to Java 7? > > Gary > > -- > E-Mail: garydgreg...@gmail.com |

Re: svn commit: r1750073 - in /commons/proper/bcel/trunk: RELEASE-NOTES.txt src/changes/changes.xml

Nice, thank you! sebb AT ASF schrieb am Fr., 24. Juni 2016 um 12:46 Uhr: > Looks like the fix for the encoding was successful. > > [I was looking for somewhere to apply a dummy change to test the UTF8 > fix when I found the duplicate ...] > > On 24 June 2016 at 11:42,

Re: [all] Rethinking dev@

On 24 June 2016 at 12:02, Jochen Wiedmann wrote: > On Fri, Jun 24, 2016 at 12:22 PM, Emmanuel Bourg wrote: > >> I'm -1, because indeed "It didn't work for Jakarta". You can't really >> compare Commons to the Incubator, because the ultimate goal of an

Re: [all] Rethinking dev@

On Fri, Jun 24, 2016 at 12:22 PM, Emmanuel Bourg wrote: > I'm -1, because indeed "It didn't work for Jakarta". You can't really > compare Commons to the Incubator, because the ultimate goal of an > incubated project is to become a TLP with its own community, so a > dedicated

Re: [all] Rethinking dev@

On Fri, Jun 24, 2016 at 12:11 PM, Bertrand Delacretaz wrote: > Another issue is voting on releases which must be an act of the PMC as > a whole, so if you split I would recommend that release votes still > happen on this list. There could be a rule, that release votes

Re: svn commit: r1750073 - in /commons/proper/bcel/trunk: RELEASE-NOTES.txt src/changes/changes.xml

Looks like the fix for the encoding was successful. [I was looking for somewhere to apply a dummy change to test the UTF8 fix when I found the duplicate ...] On 24 June 2016 at 11:42, wrote: > Author: sebb > Date: Fri Jun 24 10:42:46 2016 > New Revision: 1750073 > > URL:

Re: svn commit: r1750027 - in /commons/proper/bcel/trunk: RELEASE-NOTES.txt pom.xml src/changes/changes.xml src/changes/release-notes.vm src/conf/clirr-ignored-diffs.xml

On 24 June 2016 at 07:57, Benedikt Ritter wrote: > schrieb am Do., 23. Juni 2016 um 23:56 Uhr: > >> Author: sebb >> Date: Thu Jun 23 21:56:18 2016 >> New Revision: 1750027 >> >> URL: http://svn.apache.org/viewvc?rev=1750027=rev >> Log: >> Fix up changes.xml

Re: [all] Rethinking dev@

I'm -1, because indeed "It didn't work for Jakarta". You can't really compare Commons to the Incubator, because the ultimate goal of an incubated project is to become a TLP with its own community, so a dedicated mailing list makes sense. Splitting the Commons mailing list will just split the

Re: [CRYPTO]1.0.0 Release Plan

On 24 June 2016 at 10:08, Sun, Dapeng wrote: > Hi all, > > Thank all for helping review CRYPTO from different angles. > > According the number of jira remaining issues, I prefer to start the thread > for rolling a RC at June 29th(Next Wednesday). Please feel free to let me

Re: [all] Rethinking dev@

On Fri, Jun 24, 2016 at 12:11 PM, Stian Soiland-Reyes wrote: > ...there's the danger > of developing the "Crypto PMC", "Math PMC" etc - effectively making an > Apache within Apache RED LIGHT ALARMS ALL OVER MY BOARD MEMBER BRAIN NOW Just sayin' ;-) -Bertrand

Re: [all] Rethinking dev@

Agreed, I think multiple lists would be great for everyone else who is not on the Commons PMC; in fact that was a major reason why Commons RDF went to the Incubator first, to have its own mailing lists in the constructive phase. However it could be very fragmenting for the PMC as there's the

Re: [all] Rethinking dev@

On Fri, Jun 24, 2016 at 11:35 AM, Jochen Wiedmann > > ...Why shouldn't [math], or [crypto], have an additional mailing list... The general rule of mailing lists is that they should be split by audience, not by topic. If the math audience for example is really

Re: [all] Rethinking dev@

The 'problem of Jakarta' was a problem of supervision. The board could not trust that anyone was minding the entire store. Multiple mailing lists could be seen as an indication that commons is large and diverse enough to risk suffering from the same problem. Some would think that this desire to

Aw: [all] Rethinking dev@

+1000. I joined the commons list only because I wanted to listen to BCEL project. Kind regards, Andrey Loskutov http://google.com/+AndreyLoskutov > Gesendet: Freitag, 24. Juni 2016 um 11:35 Uhr > Von: "Jochen Wiedmann" > An: "Apache Commons Developers List"

[all] Rethinking dev@

Hi, given the last weeks, I'd like us to rethink how we work together. Right now, there is basically only a single place for discussions, and decisions, which is dev@commons. Okay, we are a common ASF project (no pun intended), and we need a place to meet, but aren't we overempasizing things a

RE: [CRYPTO]1.0.0 Release Plan

Hi all, Thank all for helping review CRYPTO from different angles. According the number of jira remaining issues, I prefer to start the thread for rolling a RC at June 29th(Next Wednesday). Please feel free to let me know if you have any concern about it. Regards Dapeng -Original

Re: svn commit: r1750027 - in /commons/proper/bcel/trunk: RELEASE-NOTES.txt pom.xml src/changes/changes.xml src/changes/release-notes.vm src/conf/clirr-ignored-diffs.xml

schrieb am Do., 23. Juni 2016 um 23:56 Uhr: > Author: sebb > Date: Thu Jun 23 21:56:18 2016 > New Revision: 1750027 > > URL: http://svn.apache.org/viewvc?rev=1750027=rev > Log: > Fix up changes.xml so it regenerates RELEASE-NOTES OK > > Modified: >