Magnolia 4.4 m1 EE bundle not yet deployed -> check the logs, redeploy (G) video, done, to be exported (B) blog post (Ph), in progress, short review by Antti Contributions
author tag, include the company name Nexus the team was not able to delete/re-deploy an artifact permissions are not easy to maintain solution: grant the admin role to Jan short training by Gregory staging uses an unique url, but normally we use different urls (CE, EE, projects, ...) should use staging profiile easiest is to use different group ids we don't differentiate between CE and EE should start with that, but this is not a short term solution one can implement complex rules (repository targets) Gregory will try to do so creates a separate staging repo per IP kind of chaining is possible will most likely not be ready for 4.4 Maintenance imaging MGNLIMG-72 -> fixed released as 2.0.6 update files.magnolia-cms.com Magnolia 4.3.8 normalization/virtual uri as little changes as possible start releasing this Tuesday Magnolia 4.4 Sprint I quick progress reached the goal Philipp has not written one line of code deletion de-activation concept discuss it after the meeting Sprint II created a new mindmap new features deletion/de-activation references STK ask Aperto for updates for the libraries, jquery, .. clear space, should we do that? daisy diff dep in progress is in the internal repo for time being ---------------------------------------------------------------- For list details see http://www.magnolia-cms.com/home/community/mailing-lists.html To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
