If you are generally ok with some APIs still evolving and changing between milestones, then go 3.2. You will have fewer generics warnings, etc. 3.1 is stable of course.

On Sep 20, 2013, at 5:52 PM, Mike Kienenberger wrote:

Never mind. After reading the news posting on the 3.2 release, I see
that it builds on 3.1, so I'm better off upgrading to 3.1 first and
getting that working before dealing with the 3.2 api changes.
On Fri, Sep 20, 2013 at 10:47 AM, Mike Kienenberger wrote:
So I'm looking at upgrading from 3.0.2 to 3.1 or 3.2.

I can already see that there's a lot of Configuration-related changes
I am going to have to make.

Is it easier to upgrade to 3.1 then 3.2, or from 3.0.2 to 3.2 directly?

The 3.2M1 package does not contain upgrade notes for 3.2, but only up
through 3.1.

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 3 of 4 | next ›
Discussion Overview
groupuser @
postedSep 20, '13 at 2:48p
activeSep 21, '13 at 8:50a



site design / logo © 2022 Grokbase