Difference between revisions of "Migration Of Escidoc Data"
Jump to navigation
Jump to search
(New page: The goal of the Migration procedure is to transform the Escidoc data created and modified with a certain stable Escidoc-core release to the next stable Escidoc-core release. Migration pro...) |
|||
| Line 1: | Line 1: | ||
The goal of the Migration procedure is to transform the Escidoc data created and modified with a certain stable Escidoc-core release to the next stable Escidoc-core release. | The goal of the Migration procedure is to transform the Escidoc data created and modified with a certain stable Escidoc-core release to the next stable Escidoc-core release. | ||
Migration procedure also tries to make a transformation of the objects created or modified with one of the developer builds delivered between these two stable Escidoc-core releases, but doesn't warrant the correctness and consistence of the result. Therefore the migration procedure will make a logg entry for every object, created or modified with one of the developer builds delivered between these two stable Escidoc-core releases. The application should | Migration procedure also tries to make a transformation of the objects created or modified with one of the developer builds delivered between these two stable Escidoc-core releases, but doesn't warrant the correctness and consistence of the result. Therefore the migration procedure will make a logg entry for every object, created or modified with one of the developer builds delivered between these two stable Escidoc-core releases. The application should care about such objects. | ||
Revision as of 13:21, 9 October 2008
The goal of the Migration procedure is to transform the Escidoc data created and modified with a certain stable Escidoc-core release to the next stable Escidoc-core release. Migration procedure also tries to make a transformation of the objects created or modified with one of the developer builds delivered between these two stable Escidoc-core releases, but doesn't warrant the correctness and consistence of the result. Therefore the migration procedure will make a logg entry for every object, created or modified with one of the developer builds delivered between these two stable Escidoc-core releases. The application should care about such objects.