9 Feb
2014
9 Feb
'14
9:51 a.m.
Result of the VOTE:
- 8 binding +1 and 3 non-binding +1
- no veto
The VOTE is passed!
So what do we need to do now:
- change the top level pom to reflect this (compiler setting + release plugin config)
- modify agents on CI to use Java7. However we probably need to leave some agents on Java6
to build 5.x branches.
Anything else?
Thanks
-Vincent
On 31 Jan 2014 at 10:06:34, vincent(a)massol.net
(vincent@massol.net(mailto:vincent@massol.net)) wrote:
Java 6 has been end of life for more than a year now.
I think it’s reasonable for us to require java7 in 6.x.
XWiki users who are in production will have about 1 year before upgrading so that should
leave them enough time to prepare.
@Thomas: I think you should send a Poll mail to the users list to ask our users how much
pain they’d have if we switched to 7 for 6.x
Thanks
-Vincent
PS: I couldn’t find any recent stat usage of Java 6 vs 7 in production.
On 31 Jan 2014 at 09:54:41, Thomas Mortagne
(thomas.mortagne@xwiki.com(mailto:thomas.mortagne@xwiki.com)) wrote:
> Hi devs,
>
> I would like to propose that we move to Java 7 as minimum version in XWiki 6.0.
>
> You can look at http://jira.xwiki.org/browse/XCOMMONS-432 for details
> on why and why not.
>
> The only cons basically is that Java 6 may still be used in production
> but we are talking about a version that won't be used in production
> before at least 3 months.
>
> WDYT ?
>
> Here is my +1
>
> --
> Thomas Mortagne