Hey there,
You probably realized in the past few weeks that a 4.5 release of Magnolia was
coming up. It's a fairly recent decision, and until a couple days ago, it
wasn't entirely clear what would go in or not just yet. We first announced it
about 2 weeks ago already (time flies!), but there's more we can say by now.
http://www.magnolia-cms.com/magnolia-cms/roadmap/roadmap-magnolia-4-5.html is
only the tip of the iceberg ;)
By pushing out another 4.x release of Magnolia, we want to ensure we ship a 5.0
that delivers on its promises... and more ! The 4.5 release will be a stepping
stone towards 5.0, which we think will allow projects to be progressively
migrated as well as new projects to start on a stable basis with minimal risks.
So what will be in 4.5 ? Well, here's the current stack of tasks we're taking
on. We're hoping for a release in November, so it's tight ! Keep in mind any
roadmap is *tentative*, meaning that if something can't be done in time, well,
priorities might change.
We're upgrading our base technology stack:
Java 6 and JCR 2.0 are long overdue updates. We'll back this by Jackrabbit
2.2 in the default bundles.
Templating gets a major revision:
The revised templating mechanism, as proposed and discussed at
http://wiki.magnolia-cms.com/display/MAGNOLIA5/Templating+-+Proposal -
including a compatibility layer, so you can migrate your templates gradually.
Repository and content access and APIs:
Magnolia will now expose and use the JCR APIs directly (as opposed to our
similar-but-not-quite APIs of times past) and provide wrappers/utils for
interoperability. See
http://wiki.magnolia-cms.com/display/MAGNOLIA5/Content+Model for Philipp's
presentation of the topic.
Security will now be handled at JCR level. -
http://wiki.magnolia-cms.com/display/MAGNOLIA5/JCR+-+Security
Security and activation:
A more secure mechanism will be used to transmit activation data between
author and public instances.
REST and CMIS:
Magnolia will provide a CMIS layer, allowing applications to access
Magnolia's repository via the CMIS standard APIs.
Inversion of Control:
A mechanism we hope will help Magnolia's own codebase, but also make module
development simpler, nicer, more elegant - see
http://wiki.magnolia-cms.com/display/DEV/Concept+IOC+in+Magnolia for some
background.
Finally, a major revision of the templating kit, STK 2.0:
This is a long topic which might deserve a discussion thread in its own
right, but here a couple of topics we'll tackle with STK 2.0:
* Mobile
* HTML 5
* Simplified configuration - we introduced the super useful "extends"
feature just a little too late for STK 1.0 to use it. Now we're going to
migrate all of STK's configuration to make use of it !
So... how does this sound ? We'd like to hear your comments and feedback, and
if you'd like to hear/read more information about certain topics, please ask.
We're pretty excited about the release, and hope you are too !
Cheers,
Grégory Joseph
Magnolia International Ltd.
----------------------------------------------------------------------
[email protected] http://www.magnolia-cms.com
Magnolia® CMS - Simple Open-Source Content Management
----------------------------------------------------------------------
----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------
