[VOTE] Require Java 1.6 for Cocoon3

2011-09-19 Thread Nathaniel, Alfred
Hi all,

A few weeks ago we had a discussion [1] whether to increase for Cocoon3 the 
minimum Java version from 1.5 to 1.6.
There were a number of advantages identified to be gained by using Java6, which 
I don't want to repeat here,

The only downside is the exclusion of potential C3 users locked in to Java5.
A survey on the user list [2] asking users to step forward if that really 
applied to anybody did not yield any response.

Therefore I' call the vote on Code Modification [3]:

+1 = Yes, Cocoon3 shall require Java 1.6
-1 = No, Cocoon3 must remain usable with Java 1.5 (with justification for the 
veto)

This change is targeted only at Cocoon3.  Cocoon2.1 and Cocoon2.2 are not 
affected.

Please cast your votes before Mon 3 Oct 06:00 UTC.

Here is mine:
+1

Cheers, Alfred.

[1] http://www.mail-archive.com/dev@cocoon.apache.org/msg59791.html
[2] http://www.mail-archive.com/users@cocoon.apache.org/msg46231.html
[3] http://www.apache.org/foundation/voting.html


The content of this e-mail is intended only for the confidential use of the 
person addressed. 
If you are not the intended recipient, please notify the sender and delete this 
e-mail immediately.
Thank you.


Re: [VOTE] Require Java 1.6 for Cocoon3

2011-09-19 Thread Peter Hunsberger
On Mon, Sep 19, 2011 at 4:03 PM, Nathaniel, Alfred
alfred.nathan...@six-group.com wrote:


 Therefore I’ call the vote on Code Modification [3]:



 +1 = Yes, Cocoon3 shall require Java 1.6

 -1 = No, Cocoon3 must remain usable with Java 1.5 (with justification for the 
 veto)


+1


Re: [VOTE] Require Java 1.6 for Cocoon3

2011-09-19 Thread Joerg Heinicke

+1

Joerg

On 19.09.2011 23:03, Nathaniel, Alfred wrote:

Hi all,

A few weeks ago we had a discussion [1] whether to increase for Cocoon3 the 
minimum Java version from 1.5 to 1.6.
There were a number of advantages identified to be gained by using Java6, which 
I don't want to repeat here,

The only downside is the exclusion of potential C3 users locked in to Java5.
A survey on the user list [2] asking users to step forward if that really 
applied to anybody did not yield any response.

Therefore I' call the vote on Code Modification [3]:

+1 = Yes, Cocoon3 shall require Java 1.6
-1 = No, Cocoon3 must remain usable with Java 1.5 (with justification for the 
veto)

This change is targeted only at Cocoon3.  Cocoon2.1 and Cocoon2.2 are not 
affected.

Please cast your votes before Mon 3 Oct 06:00 UTC.

Here is mine:
+1

Cheers, Alfred.

[1] http://www.mail-archive.com/dev@cocoon.apache.org/msg59791.html
[2] http://www.mail-archive.com/users@cocoon.apache.org/msg46231.html
[3] http://www.apache.org/foundation/voting.html


The content of this e-mail is intended only for the confidential use of the 
person addressed.
If you are not the intended recipient, please notify the sender and delete this 
e-mail immediately.
Thank you.



RE: Failing build

2011-09-19 Thread Nathaniel, Alfred
+1

Is there an option to delay the dev@ mail to give the committer a head start 
for fixing his own mess?

Cheers, Alfred. 

-Original Message-
From: simone.trip...@gmail.com [mailto:simone.trip...@gmail.com] On Behalf Of 
Simone Tripodi
Sent: Freitag, 16. September 2011 17:13
To: dev@cocoon.apache.org
Subject: Re: Failing build

I received the Jenkins notification that build came normal, I guess it
is configured to send email only to last committer that commits, not
the dev ML :S
I think we should ping INFRA to change that setting and receive the
failures on dev ML, WDYT?

thanks for the fix!! :)

All the best,
Simo


The content of this e-mail is intended only for the confidential use of the 
person addressed. 
If you are not the intended recipient, please notify the sender and delete this 
e-mail immediately.
Thank you.