+1. -- Ashish
On Sat, Nov 14, 2009 at 10:02 AM, David E Jones <d...@me.com> wrote: > > We had to make this decision before with 1.4 -> 1.5, and if I remember > right from 1.3 -> 1.4 too. > > Sooner or later we need to deprecate support for 1.5 in order to move on, > and to more easily be able to update various libraries and such. The 1.5 -> > 1.6 transition is a bit of a pain because they did a few changes that were > not backwards compatible. Because of that it would be particularly nice to > deprecate support for 1.5 and require 1.6 (or later, as possible/available). > > In any case, our criteria before was to deprecate support for the older > version of Java as soon as the newer version was widely available. At this > point I think 1.6 qualifies well for that... unless there are specific > systems people use that still can't run 1.6 then we should just update that > requirement. > > -David