[
http://jira.magnolia-cms.com/browse/MGNLSTK-1073?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samuel Schmitt updated MGNLSTK-1073:
------------------------------------
Attachment: Migration status and STK.zip
Description:
This ticket is the result of the following discussion
#####
Hi all,
we just discussed with Philip about the migration and about the side effect
produced by the changes done on the different version of the migration module.
To make it short, each version of the migration generates a different
configuration of STK.
And a fresh installation comes with the configuration generated by the
migration v1.1.2.
So we want to align everything.
The next migration module 1.2.1 must generate the same config than in the next
STK 2.0.9.
And a update from stk 2.0.8 to STK 2.0.9 must handle the delta of the config.
i created a ticket for that http://jira.magnolia-cms.com/browse/MGNLSTK-1073
The service team could do the 2 sub task.
The issue described with STK is also true for form, pur, ect... Tickets are not
yet created.
A second point, we would like to finalize the migration v1.2.1.
We found major issues. We already fixed some of them but here it would be great
if the maintenance team can jump in the topic.
http://jira.magnolia-cms.com/browse/MGNLMIGRATION/fixforversion/12456
We can have a call if things are not clear and to define who do what.
Cheers,
Sam
####
Attached more discussion
> The configuration of STK between a new instance and a migrated instance must
> be the same
> ----------------------------------------------------------------------------------------
>
> Key: MGNLSTK-1073
> URL: http://jira.magnolia-cms.com/browse/MGNLSTK-1073
> Project: Magnolia Standard Templating Kit
> Issue Type: Task
> Reporter: Samuel Schmitt
> Priority: Major
> Fix For: 2.0.9
>
> Attachments: Migration status and STK.zip
>
>
> This ticket is the result of the following discussion
> #####
> Hi all,
> we just discussed with Philip about the migration and about the side effect
> produced by the changes done on the different version of the migration module.
> To make it short, each version of the migration generates a different
> configuration of STK.
> And a fresh installation comes with the configuration generated by the
> migration v1.1.2.
> So we want to align everything.
> The next migration module 1.2.1 must generate the same config than in the
> next STK 2.0.9.
> And a update from stk 2.0.8 to STK 2.0.9 must handle the delta of the config.
> i created a ticket for that http://jira.magnolia-cms.com/browse/MGNLSTK-1073
> The service team could do the 2 sub task.
> The issue described with STK is also true for form, pur, ect... Tickets are
> not yet created.
> A second point, we would like to finalize the migration v1.2.1.
> We found major issues. We already fixed some of them but here it would be
> great if the maintenance team can jump in the topic.
> http://jira.magnolia-cms.com/browse/MGNLMIGRATION/fixforversion/12456
> We can have a call if things are not clear and to define who do what.
> Cheers,
> Sam
> ####
> Attached more discussion
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
