IMHO we should move all of dev to 1.7 ASAP to suss out any early issues. This should include continuous integration. Thanks, L
On Jul 16, 2012, at 12:54 PM, Duffy Gillman <[email protected]> wrote: > I've been looking into compiling and running nakamura under the Oracle 1.7 > JDK and have met initial success [1]. After some additional testing we will > be able to use either 1.6 or 1.7. This raises the question what we want to > officially support, and when support should be shifted to 1.7. For some > period it may be possible to support either version of Java. Java 1.6 will > reach end of life (EOL) November of this year [2]. So this discussion may be > urgent for some in this community. What concerns does this community have > around the timing of this transition? It seems some deployers may be pushed > by support policies to move off of the soon-to-be-unsupported Java 1.6. Are > there likewise folks who will face obstacles moving *off* of 1.6? What is the > cost (particularly for QA) of supporting both versions? > > Just some points for discussion... > > [1] https://github.com/sakaiproject/nakamura/pull/915 > [2] http://www.oracle.com/technetwork/java/eol-135779.html > ------------------------------ > Duffy Gillman > Sr. Software Engineer > The rSmart Group, Inc. > > _______________________________________________ > oae-dev mailing list > [email protected] > http://collab.sakaiproject.org/mailman/listinfo/oae-dev _______________________________________________ oae-dev mailing list [email protected] http://collab.sakaiproject.org/mailman/listinfo/oae-dev
