Hi, we had some attempts for automatic migration, but the PR was closed based on a ML thread, where it was advised to not run auto migration. Now I think the next questions are: * Do we support a migration from 1.0.0.final to any new release of the 1.0.x series? * If yes, how do we do that, and where is the documentation for that? Does we need a new ticket (e.g. for documentation) to be included in the 1.0.3 release? -Matthias -- Matthias Wessendorf blog: http://matthiaswessendorf.wordpress.com/ sessions: http://www.slideshare.net/mwessendorf twitter: http://twitter.com/mwessendorf

On 09/12/2014 10:51, Matthias Wessendorf wrote: > > Now I think the next questions are: > * Do we support a migration from 1.0.0.final to any new release of the > 1.0.x series? What would be the alternative? > * If yes, how do we do that, and where is the documentation for that? So yes, we have to have a migration path and of course it needs to be documented how to use it.

_______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev

Answers in line On Tue, Dec 9, 2014 at 7:51 AM, Matthias Wessendorf <matzew(a)apache.org&gt; wrote: > Hi, > > we had some attempts for automatic migration, but the PR was closed based > on a ML thread, where it was advised to not run auto migration. > > Now I think the next questions are: > * Do we support a migration from 1.0.0.final to any new release of the > 1.0.x series? > Yes! > * If yes, how do we do that, and where is the documentation for that? > * Release notes and link to migrate script.

* ag.org page "How to migrate" > Does we need a new ticket (e.g. for documentation) to be included in the > 1.0.3 release? > > -Matthias > _______________________________________________ aerogear-dev mailing list aerogear-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/aerogear-dev