Magnolia Enterprise Edition 3.5 has just been released. This version sports a more targeted focus on I18N, streamlined maintenance and integration for enterprises with an international focus.
To begin with, it is much easier to customize the offering. v3.5 includes a new configuration mechanism that enables you to build custom modules that, if you like, can replace certain Magnolia functionalities.
The offering's complete modularization -- another new feature -- makes it possible to do this without affecting Magnolia's default distribution.

Magnolia, an enterprise CMS purveyor, as transitioned Magnolia Community Edition to GPLv3.
This is the most current iteration of the open source license released just last June by the Free Software Foundation.
This move makes Magnolia the first JSR 170-based CMS to go public under GPLv3.
Adopting the open source license -- thereby enabling developers to improve it as they wish -- makes Magnolia more resilient in the face of change, thereby protecting the investment of clients. For this reason Magnolia's namesake makes an apt metaphor.
Despite its elegant appearance, the magnolia flower dates back over 20 million years. Having weathered its fair share of Darwinist storms, even its fragrant petals are extra-tough, because it is pollinated by beetles.
Not a bad lot to cast your fortunes with.
Download Magnolia Community Edition at no cost on the Magnolia website. Or to find out what others think, clicky-clicky for comments.
Today Magnolia released Magnolia Enterprise Edition, a major update to their Enterprise Web CMS + Java Content Repository (JSR-170) offering, targeting simplification and ease of deployment. This is to commemorate their third anniversary.
If only all vendors celebrated product birthdays by making life easier for developers, yeah?
Magnolia 3.0 is out the door. A "commercial open-source" project, Magnolia integrates web content management (CMS) and document management (DMS) through a single, web-based, AJAX-powered user interface.
Version 3.0 brings together 3+ years of research and development and is one of the few CMS products to support the JSR-170 content repository standard.