[mitreid-connect] Release Candidate: 1.2.0-RC1

[Justin Richer]

Unfortunately we haven’t been very good at keeping changelogs between releases, so apart from looking at the code change sets there’s not a very good way to see what’s there. 

You should at the very least upgrade to 1.1.15 (and 1.1.16 when it comes out) as there are data upgrade API and security updates and other bug fixes in there.

I would recommend at least testing 1.2.0-RC1 to make sure that it doesn’t regress something that you count on for your environment.

 — Justin

> On Jul 14, 2015, at 11:02 AM, Luiz Omori <luiz.omori at duke.edu> wrote:
> 
> 
> Is there a succinct list of changes between MitreId versions? We are using
> 1.1.12 and wonder about upgrading it.
> 
> Regards,
> Luiz
> 
> 
> On Jul/9/15, 6:38 PM, "mitreid-connect-bounces at mit.edu on behalf of Justin
> Richer" <mitreid-connect-bounces at mit.edu on behalf of jricher at mit.edu>
> wrote:
> 
>> We¹ve just published the first Release Candidate version of MITREid
>> Connect 1.2. This new release has many improvements over the 1.1 series
>> and includes brand new functionality such as UMA support. Upgrades are
>> possible from recent 1.0 and 1.1 releases using the server¹s data
>> import/export API (available from the server root at /api/data).
>> 
>> The files are on their way to Maven Central now and should be available
>> as version ³1.2.0-RC1² under the existing group and artifact IDs.
>> 
>> Please test this version, including upgrades from previous releases
>> wherever possible, and file bugs in the GitHub issue tracker. Since this
>> is a Release Candidate, there may be several more big incompatible
>> changes before the release of 1.2.0. We don¹t have an exact date for
>> 1.2.0, but if testing proceeds smoothly with the Release Candidates, it
>> could happen imminently.
>> 
>> ‹ Justin
>> _______________________________________________
>> mitreid-connect mailing list
>> mitreid-connect at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/mitreid-connect
>