Administrator



what would help is if you could try the milestones and release

candidates out.



If you find issues that require changes to your code we can document

them in the release notes. We of course will document as many of the

known upgrade requirements as possible, but feedback really helps



Cheers



On Mon, Jun 27, 2011 at 5:06 PM, James Zhang <

> It is glad to hear that and looking forward to the release. Great job!

> Since I have couple of production sites running on Grails 1.3.7 and I am

> eager to upgrade to this new release so I can take advantage of Hibernate

> 3.6. Is there any note or wrap up how to safely upgrade/merge to the new

> release from older one?

> Thanks and Regards,

> James

>

>> From:

>> Date: Mon, 27 Jun 2011 17:01:23 +0200

>> To:

>> Subject: [grails-user] Grails 1.4 is now Grails 2.0

>>

>> Hi all,

>>

>> After some consideration we have decided to change Grails 1.4 to be

>> Grails 2.0. This should not significantly impact timelines of the

>> release, but we do feel there are too many great things in the github

>> master branch for it to be a mere 1.4 release.

>>

>> Some of these things coming in the next milestone include:

>>

>> * New console UI and interactive mode

>> * Enhanced error reporting and stack trace printing

>> * Improved development time reloading with a JVM agent

>> * Performance enhancements

>> * AST transformation API for plugin devs

>> * HTML5 scaffolding

>> * Static resource handling

>> * A formalized GORM API

>> * Abstract inheritance support

>> * Multiple data sources support with 2 phase commit

>> * Database migrations and reverse engineering

>> * Upgrades to libraries from Groovy 1.8, Spring 3.1, Hibernate 3.6 and

>> Servlet 3.0

>> * Completely new Testing API with Spock support

>> * Unit test scaffolding and enhanced unit test output in the console

>>

>> There is just too much there that it no longer feels like a 1.x

>> release, so the next release of Grails with 2.0.0.M1 at the end of

>> July

>>

>> Followed closely the the release candidates running through August

>> until we're final

>>

>> The roadmap at

>> change

>>

>> Cheers,

>>

>> --

>> Graeme Rocher

>> Grails Project Lead

>> SpringSource - A Division of VMware

>>

>>

>> ---------------------------------------------------------------------

>> To unsubscribe from this list, please visit:

>>

>>

>>

>>

> > It is glad to hear that and looking forward to the release. Great job!> Since I have couple of production sites running on Grails 1.3.7 and I am> eager to upgrade to this new release so I can take advantage of Hibernate> 3.6. Is there any note or wrap up how to safely upgrade/merge to the new> release from older one?> Thanks and Regards,> James>> From: [hidden email] >> Date: Mon, 27 Jun 2011 17:01:23 +0200>> To: [hidden email] >> Subject: [grails-user] Grails 1.4 is now Grails 2.0>>>> Hi all,>>>> After some consideration we have decided to change Grails 1.4 to be>> Grails 2.0. This should not significantly impact timelines of the>> release, but we do feel there are too many great things in the github>> master branch for it to be a mere 1.4 release.>>>> Some of these things coming in the next milestone include:>>>> * New console UI and interactive mode>> * Enhanced error reporting and stack trace printing>> * Improved development time reloading with a JVM agent>> * Performance enhancements>> * AST transformation API for plugin devs>> * HTML5 scaffolding>> * Static resource handling>> * A formalized GORM API>> * Abstract inheritance support>> * Multiple data sources support with 2 phase commit>> * Database migrations and reverse engineering>> * Upgrades to libraries from Groovy 1.8, Spring 3.1, Hibernate 3.6 and>> Servlet 3.0>> * Completely new Testing API with Spock support>> * Unit test scaffolding and enhanced unit test output in the console>>>> There is just too much there that it no longer feels like a 1.x>> release, so the next release of Grails with 2.0.0.M1 at the end of>> July>>>> Followed closely the the release candidates running through August>> until we're final>>>> The roadmap at http://grails.org/Roadmap has been updated to reflect the>> change>>>> Cheers,>>>> -->> Graeme Rocher>> Grails Project Lead>> SpringSource - A Division of VMware>> http://www.springsource.com >>>> --------------------------------------------------------------------->> To unsubscribe from this list, please visit:>>>> http://xircles.codehaus.org/manage_email >>>>





--

Graeme Rocher

Grails Project Lead

SpringSource - A Division of VMware

http://www.springsource.com



---------------------------------------------------------------------

To unsubscribe from this list, please visit:



http://xircles.codehaus.org/manage_email





We will evolve the upgrade notes closer to the time of release, butwhat would help is if you could try the milestones and releasecandidates out.If you find issues that require changes to your code we can documentthem in the release notes. We of course will document as many of theknown upgrade requirements as possible, but feedback really helpsCheersOn Mon, Jun 27, 2011 at 5:06 PM, James Zhang < [hidden email] > wrote:--Graeme RocherGrails Project LeadSpringSource - A Division of VMware---------------------------------------------------------------------To unsubscribe from this list, please visit: