STK must be in sync with static prototype changes for every minor release
-------------------------------------------------------------------------
Key: MGNLSTK-965
URL: http://jira.magnolia-cms.com/browse/MGNLSTK-965
Project: Magnolia Standard Templating Kit
Issue Type: Bug
Components: concept, paragraphs, templates
Affects Versions: 2.0.3, 2.0.2
Reporter: Christian Ringele
Priority: Blocker
Fix For: 2.0.4
In between every minor release there could be changes within the html static
prototype.
The static prototype get released together with the STK. There for the STK must
always be aligned/in sync with the static prototype.
This is a repeating task for every minor&major version.
I'll link a issue, which just postponed to a later version. This should never
happen:
STK 2.0.3 is not in sync with prototype 2.0.3
The process to do:
- See if there were any check ins into the prototype
- If so a divv whill show it that were css or html changes
-- css changes -> can just be copy & pasted into the theme module
-- html changes -> accordinf ftl must be found and change implemented
Be careful, right now all changes till prototype 2.0.1 must be taking in
account.
--
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]>
----------------------------------------------------------------
