The Motivation

Until M5 Magnolia stored MetaData on a separate subnode - among others this

...

• mgnl:lastModified (DATE)
• mgnl:lastModifiedBy (STRING)

[mgnl:activatable]
  MIXIN

• mgnl:lastActivated (DATE)
• mgnl:lastActivatedBy (STRING)
• mgnl:activationStatus (STRING)

...

It hosts a proper inner class for each node type together with the constants for all it's properties and some convenience methods. 

Backwards Compatibility

• info.magnolia.cms.core.MetaData has been adapted to be fully backwards compatible
  • If you have code still using the MetaData type and the old property names, we'll internally map these to the new property names on the workingNode. 

Migration

Bootstrap files

• We still support Bootstrap files containing MetaData subsides
  
  • info.magnolia.importexport.postprocessors.MetaDataImportPostProcessor will take care of moving the contained properties to the workingNode and rename to the new structure

Repositories

• <to be described>in next Sprint (s011) we'll add an InstallationTask migrating existing content to the new repository layout