Re: [VOTE] Bump Jenkins to Java 6
On 09/06/2012 12:12 AM, Stephen Connolly wrote: On 5 September 2012 23:16, Kohsuke Kawaguchi kkawagu...@cloudbees.com mailto:kkawagu...@cloudbees.com wrote: On 09/05/2012 01:18 PM, Brian Smith wrote: Hi I don't think EOL alone is a good reason to upgrade the runtime dependency, anybody concerned about it can run on a newer JVM anyway. It might help if someone were to outline the benefit of upgrading the language version. The benefits to developers are: - We get to use a few APIs that we currently can't rely on. (Note that we already do use a number of Java6 APIs in ways that gracefully degrades when running on Java5, but this is separate.) - Some IDE integrations (apparently) work better when what we tell as the compiler language level (1.5) matches with the runtime requirement (1.6) - Some language level stuff (like @Override on interface methods) causes IDE and javac to disagree, which gets fixed with 1.6. The benefits are admittedly marginal, but the argument is that the cost is marginal, too --- just 2% of users on Java5, and I suspect those people aren't updating frequently. And at some point we need to move on, so I suppose it could well be now. I guess what I'm particularly keen on is if there are any minority platforms where Java6 isn't available easily, and/or desperate cries from users begging us not to require Java6, if any. This is really where the issue is. If you have Jenkins slaves that are on older OSes which are stuck with Java 1.5 as the best JVM they can run, please shout out now. Yes, slaves are important. When the Jenkins core bumps up to require Java6, all the slaves will need to run Java6. You can still launch builds that builds with Java5 (just like you can today launch a build that builds with Java 1.4), but the slave JVM will have to be Java6. So folks, think about all the exotic slaves you may have (BSD, SunOS, IRIX, HP-UX, AIX, ...) and think if Java6 is available readily on them. Do you keep any ancient versions of those platforms for testing purpose? Do your ancient versions have Java6? So far we are seeing wide support from developers to bump up to 1.6. So you better raise your voice if you have a problem... -Stephen (Personally, I'm neutral on this.) What's the upside for jenkins dev? Is there something in java 6 people are hankering to use? Personally the only things in java 6 I've found useful were the new concurrent collections and the ResourceBundle hooks. Cheers Brian On 5 September 2012 20:18, domi d...@fortysix.ch mailto:d...@fortysix.ch mailto:d...@fortysix.ch mailto:d...@fortysix.ch wrote: Hi all, just after todays meeting on the IRC chat, we startet a discussion about upgrading Jenkins to Java 6. As Java 5 has reached EOL since quite a while, some core developers have asked whether it would be OK to bump Jenkins' runtime dependency from Java5 to Java6. The core is already build on Java6, but until now still backward compatible with Java5. Therefore we would like to know from you (Users) whether you have an issue with this upgrade. This would mean, that in the future you will have to have Java6 installed to run Jenkins (for Master and Slave). Here are the current usage numbers (installations we know of): Java 1.5: 655 Java 1.6: 29164 Java 1.7: 2919 So please give us some feedback/votes on this. Domi -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Nectar, our professional version of Jenkins -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Nectar, our professional version of Jenkins
Re: [VOTE] Bump Jenkins to Java 6
On Fri, Sep 7, 2012 at 1:42 PM, Kohsuke Kawaguchi kkawagu...@cloudbees.com wrote: Yes, slaves are important. When the Jenkins core bumps up to require Java6, all the slaves will need to run Java6. You can still launch builds that builds with Java5 (just like you can today launch a build that builds with Java 1.4), but the slave JVM will have to be Java6. So folks, think about all the exotic slaves you may have (BSD, SunOS, IRIX, HP-UX, AIX, ...) and think if Java6 is available readily on them. Do you keep any ancient versions of those platforms for testing purpose? Do your ancient versions have Java6? So far we are seeing wide support from developers to bump up to 1.6. So you better raise your voice if you have a problem... +1 for Java6 -- Mehul N. Sanghvi email: mehul.sang...@gmail.com
Re: [VOTE] Bump Jenkins to Java 6
On 5 September 2012 23:16, Kohsuke Kawaguchi kkawagu...@cloudbees.comwrote: On 09/05/2012 01:18 PM, Brian Smith wrote: Hi I don't think EOL alone is a good reason to upgrade the runtime dependency, anybody concerned about it can run on a newer JVM anyway. It might help if someone were to outline the benefit of upgrading the language version. The benefits to developers are: - We get to use a few APIs that we currently can't rely on. (Note that we already do use a number of Java6 APIs in ways that gracefully degrades when running on Java5, but this is separate.) - Some IDE integrations (apparently) work better when what we tell as the compiler language level (1.5) matches with the runtime requirement (1.6) - Some language level stuff (like @Override on interface methods) causes IDE and javac to disagree, which gets fixed with 1.6. The benefits are admittedly marginal, but the argument is that the cost is marginal, too --- just 2% of users on Java5, and I suspect those people aren't updating frequently. And at some point we need to move on, so I suppose it could well be now. I guess what I'm particularly keen on is if there are any minority platforms where Java6 isn't available easily, and/or desperate cries from users begging us not to require Java6, if any. This is really where the issue is. If you have Jenkins slaves that are on older OSes which are stuck with Java 1.5 as the best JVM they can run, please shout out now. -Stephen (Personally, I'm neutral on this.) What's the upside for jenkins dev? Is there something in java 6 people are hankering to use? Personally the only things in java 6 I've found useful were the new concurrent collections and the ResourceBundle hooks. Cheers Brian On 5 September 2012 20:18, domi d...@fortysix.ch mailto:d...@fortysix.ch wrote: Hi all, just after todays meeting on the IRC chat, we startet a discussion about upgrading Jenkins to Java 6. As Java 5 has reached EOL since quite a while, some core developers have asked whether it would be OK to bump Jenkins' runtime dependency from Java5 to Java6. The core is already build on Java6, but until now still backward compatible with Java5. Therefore we would like to know from you (Users) whether you have an issue with this upgrade. This would mean, that in the future you will have to have Java6 installed to run Jenkins (for Master and Slave). Here are the current usage numbers (installations we know of): Java 1.5: 655 Java 1.6: 29164 Java 1.7: 2919 So please give us some feedback/votes on this. Domi -- Kohsuke Kawaguchi | CloudBees, Inc. | http://cloudbees.com/ Try Nectar, our professional version of Jenkins
Re: [VOTE] Bump Jenkins to Java 6
Am Mittwoch, 5. September 2012 21:18:41 UTC+2 schrieb domi: Hi all, just after todays meeting on the IRC chat, we startet a discussion about upgrading Jenkins to Java 6. As Java 5 has reached EOL since quite a while, some core developers have asked whether it would be OK to bump Jenkins' runtime dependency from Java5 to Java6. The core is already build on Java6, but until now still backward compatible with Java5. Therefore we would like to know from you (Users) whether you have an issue with this upgrade. This would mean, that in the future you will have to have Java6 installed to run Jenkins (for Master and Slave). Here are the current usage numbers (installations we know of): Java 1.5: 655 Java 1.6: 29164 Java 1.7: 2919 So please give us some feedback/votes on this. Domi
Re: [VOTE] Bump Jenkins to Java 6
+1 I know thats not easy to update all kinds of nodes to Java 1.6+. But the jenkins core should be cleaned up to depend on Java 1.6. Conny Am Mittwoch, 5. September 2012 21:18:41 UTC+2 schrieb domi: Hi all, just after todays meeting on the IRC chat, we startet a discussion about upgrading Jenkins to Java 6. As Java 5 has reached EOL since quite a while, some core developers have asked whether it would be OK to bump Jenkins' runtime dependency from Java5 to Java6. The core is already build on Java6, but until now still backward compatible with Java5. Therefore we would like to know from you (Users) whether you have an issue with this upgrade. This would mean, that in the future you will have to have Java6 installed to run Jenkins (for Master and Slave). Here are the current usage numbers (installations we know of): Java 1.5: 655 Java 1.6: 29164 Java 1.7: 2919 So please give us some feedback/votes on this. Domi
[VOTE] Bump Jenkins to Java 6
Hi all, just after todays meeting on the IRC chat, we startet a discussion about upgrading Jenkins to Java 6. As Java 5 has reached EOL since quite a while, some core developers have asked whether it would be OK to bump Jenkins' runtime dependency from Java5 to Java6. The core is already build on Java6, but until now still backward compatible with Java5. Therefore we would like to know from you (Users) whether you have an issue with this upgrade. This would mean, that in the future you will have to have Java6 installed to run Jenkins (for Master and Slave). Here are the current usage numbers (installations we know of): Java 1.5: 655 Java 1.6: 29164 Java 1.7: 2919 So please give us some feedback/votes on this. Domi
Re: [VOTE] Bump Jenkins to Java 6
Bump Jenkins version to 1.500 (or something), put branch 1.4xx into maintenance and switch to Java 7. Java 7 is already at update 7. My $.02. On Wed, Sep 5, 2012 at 1:18 PM, domi d...@fortysix.ch wrote: Hi all, just after todays meeting on the IRC chat, we startet a discussion about upgrading Jenkins to Java 6. As Java 5 has reached EOL since quite a while, some core developers have asked whether it would be OK to bump Jenkins' runtime dependency from Java5 to Java6. The core is already build on Java6, but until now still backward compatible with Java5. Therefore we would like to know from you (Users) whether you have an issue with this upgrade. This would mean, that in the future you will have to have Java6 installed to run Jenkins (for Master and Slave). Here are the current usage numbers (installations we know of): Java 1.5: 655 Java 1.6: 29164 Java 1.7: 2919 So please give us some feedback/votes on this. Domi -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !!
Re: [VOTE] Bump Jenkins to Java 6
Switching to Java 7 would be a mistake in my view based on the number of users listed in the current usage summary. If current development switches to Java 7, the Java 5 and Java 6 users will be stranded by a development choice, rather than making their own choice of JDK. I don't see enough benefit for Jenkins developers or Jenkins users in the switch from Java6 to Java7, and I see a large potential to alienate a very large portion of the user community if development switched to a Java7 runtime dependency. I'm in favor of switching from Java5 as the runtime dependency to Java6 as the runtime dependency. I assume it is one less thing to trouble the developers so they don't have to continually check that they have not inadvertently introduced a Java6 runtime dependency. Mark Waite From: Jeff predato...@gmail.com To: jenkinsci-users@googlegroups.com Sent: Wednesday, September 5, 2012 1:38 PM Subject: Re: [VOTE] Bump Jenkins to Java 6 Bump Jenkins version to 1.500 (or something), put branch 1.4xx into maintenance and switch to Java 7. Java 7 is already at update 7. My $.02. On Wed, Sep 5, 2012 at 1:18 PM, domi d...@fortysix.ch wrote: Hi all, just after todays meeting on the IRC chat, we startet a discussion about upgrading Jenkins to Java 6. As Java 5 has reached EOL since quite a while, some core developers have asked whether it would be OK to bump Jenkins' runtime dependency from Java5 to Java6. The core is already build on Java6, but until now still backward compatible with Java5. Therefore we would like to know from you (Users) whether you have an issue with this upgrade. This would mean, that in the future you will have to have Java6 installed to run Jenkins (for Master and Slave). Here are the current usage numbers (installations we know of): Java 1.5: 655 Java 1.6: 29164 Java 1.7: 2919 So please give us some feedback/votes on this. Domi -- Jeff Vincent predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox !!
Re: [VOTE] Bump Jenkins to Java 6
On 5 September 2012 21:38, Jeff predato...@gmail.com wrote: Bump Jenkins version to 1.500 (or something), put branch 1.4xx into maintenance and switch to Java 7. Java 7 is already at update 7. +1 Java 6 is end of life by Feb 2013 [1], If I understand it correctly, we are discussing a dependency to a Java 7 run time for running Jenkins. The compiler used by any project is still the choice of each project. /Thomas [1] http://www.oracle.com/technetwork/java/eol-135779.html -- Thomas Sundberg M. Sc. in Computer Science Mobile: +46 70 767 33 15 Blog: http://thomassundberg.wordpress.com/ Twitter: @thomassundberg Better software through faster feedback
Re: [VOTE] Bump Jenkins to Java 6
On 09/05/2012 05:12 PM, Thomas Sundberg wrote: On 5 September 2012 21:38, Jeff predato...@gmail.com wrote: Bump Jenkins version to 1.500 (or something), put branch 1.4xx into maintenance and switch to Java 7. Java 7 is already at update 7. +1 Java 6 is end of life by Feb 2013 [1], If I understand it correctly, we are discussing a dependency to a Java 7 run time for running Jenkins. The compiler used by any project is still the choice of each project. /Thomas [1] http://www.oracle.com/technetwork/java/eol-135779.html My understanding is we are talking about dropping support for Java 5. Keeping Java 6 runtime support. Now if the developers are developing against 6 or 7 I don't really car as long as we are keeping Java 6 runtime support. -- Thanks Robert Middleswarth @rmiddle (twitter/Freenode IRC) @RobertM (OFTC IRC)
Re: [VOTE] Bump Jenkins to Java 6
We aren't talking about requiring Java7. So let's not confuse this request for feedback with a different issue. On 09/05/2012 12:38 PM, Jeff wrote: Bump Jenkins version to 1.500 (or something), put branch 1.4xx into maintenance and switch to Java 7. Java 7 is already at update 7. My $.02. On Wed, Sep 5, 2012 at 1:18 PM, domi d...@fortysix.ch mailto:d...@fortysix.ch wrote: Hi all, just after todays meeting on the IRC chat, we startet a discussion about upgrading Jenkins to Java 6. As Java 5 has reached EOL since quite a while, some core developers have asked whether it would be OK to bump Jenkins' runtime dependency from Java5 to Java6. The core is already build on Java6, but until now still backward compatible with Java5. Therefore we would like to know from you (Users) whether you have an issue with this upgrade. This would mean, that in the future you will have to have Java6 installed to run Jenkins (for Master and Slave). Here are the current usage numbers (installations we know of): Java 1.5: 655 Java 1.6: 29164 Java 1.7: 2919 So please give us some feedback/votes on this. Domi -- Jeff Vincent predato...@gmail.com mailto:predato...@gmail.com See my LinkedIn profile at: http://www.linkedin.com/in/rjeffreyvincent I ♥ DropBox http://db.tt/9O6LfBX !! -- Kohsuke Kawaguchi http://kohsuke.org/
Antwort: [VOTE] Bump Jenkins to Java 6
hi together, is there any site for the feedback? or do you really want to get the statistics from all the replies? :-) anyway, we're fine with java 6. kind regards, Andreas Schilling CAE Processes Data Management --- Dipl. Inf. Andreas Schilling Senior Software Architect TWT GmbH Science Innovation Bernhäuser Str. 40 - 42 73765 Neuhausen Tel: +49 - 7158 - 17 15 - 673 E-Mail: andreas.schill...@twt-gmbh.de www.twt-gmbh.de Geschäftsführung: Dimitrios Vartziotis, Joachim Laicher (stv.) Registergericht: Amtsgericht Stuttgart, HRB Nr. 212778 Umsatzsteuer: ID-Nr.: DE147841145 Von:domi d...@fortysix.ch An: Jenkins Developers jenkinsci-...@googlegroups.com, jenkinsci-users@googlegroups.com jenkinsci-users@googlegroups.com Datum: 05.09.2012 21:24 Betreff:[VOTE] Bump Jenkins to Java 6 Gesendet von: jenkinsci-users@googlegroups.com Hi all, just after todays meeting on the IRC chat, we startet a discussion about upgrading Jenkins to Java 6. As Java 5 has reached EOL since quite a while, some core developers have asked whether it would be OK to bump Jenkins' runtime dependency from Java5 to Java6. The core is already build on Java6, but until now still backward compatible with Java5. Therefore we would like to know from you (Users) whether you have an issue with this upgrade. This would mean, that in the future you will have to have Java6 installed to run Jenkins (for Master and Slave). Here are the current usage numbers (installations we know of): Java 1.5: 655 Java 1.6: 29164 Java 1.7: 2919 So please give us some feedback/votes on this. Domi
