I should add that for us, the main problem would be if you introduce incompatible code changes, e.g. sdk dependencies which are unique to 7 or upwards. If the actual code remains compatible, we can always rebuild using IBM's java 6. On the side, I was also told that IBM's Java lifecycle is not aligned with Oracle's. I don't have the exact dates available though
Simon From: Simon Helsen/Toronto/IBM@IBMCA To: [email protected], Date: 01/17/2013 02:03 PM Subject: Re: Java6 end of life Hey Andy, I can understand the issue around bug fixes. Not sure how likely this is in practice though. I can't really comment on cost of development. It is also hard for me to make statements about 2/ and 3/. What where you thinking of when you think development may be less fun? Would it put developers/contributors off? No idea either. I don't have a personal relationship with Java 6, nor with 7 :-) I am not following your last paragraph "the "plan B" one-two of Java7-then-Java8 is a different style to java as a static unchanging thing it had slipped into." What exactly do you mean by this? thanks Simon From: Andy Seaborne <[email protected]> To: [email protected], Date: 01/17/2013 01:33 PM Subject: Re: Java6 end of life Hello Simon :-) On 17/01/13 16:18, Simon Helsen wrote: > end of public updates does not mean "won't be used anymore". I guess the > more compelling question is why Jena needs to be moved to Java 7. If there > is no specific reason, why move? I do think it is important to be > compatible with Java 7, but I am not aware of any issue there > > Simon "end of public updates" does mean little or no security updates, as well as no bug fixes. The bug issue is a risk because Jena is not a static maintenance-only codebase - new code may trigger different bugs. There are various community issues as well: 1/ Does it cause cost on development? 2/ Does it make development less fun? 3/ Does it put contributors/developers off by being a bit laggardly? The changes in Java over the next 2 releases are a special case. The "plan B" one-two of Java7-then-Java8 is a different style to java as a static unchanging thing it had slipped into. Andy > > > > > From: > Andy Seaborne <[email protected]> > To: > [email protected], > Date: > 01/17/2013 04:38 AM > Subject: > Java6 end of life > > > > FYI > > Java 6 end-of-life is approaching. > > End of public updates is next month (Feb 2013). > End of public updates for Java7 is currently July 2014. > Java8 is scheduled for Sept 2013 (and feature complete this month) > > Jena 2.10 is the next release. > > Thoughts on migration? > > Andy > > http://www.oracle.com/technetwork/java/eol-135779.html > > > >
