Development Roadmap

Upcoming Releases of Jahia Portal Server

Jahia 5.x Releases

Jahia 5.0 SP (Service Packs)

Please note that the Jahia SVN already includes a Service Pack (SP) branch with all the bugs already fixed being available. You can found daily nightly builds on http://nightly.jahia.com in order to test and verify if your bug was already fixed. From time to time, as soon as a number of fixes is significant enough and all the QA tests have been successfully passed, Jahia will release some new offical service packs. 

• SP1 - Christmas 2006
• SP2 - June 2007 - Migration from 4.x and functional stability
• Sp3 - Fall 2007 - Performance fine-tunings

Jahia 5.1 (End 2007 - Q1 2008) 

New major features will include:

• New Document Management System based on Apache Jacrabbit (currently based on Apache Slide)
• New Portal Interface (à la Netvibes.com and Web 2.0 oriented)
• Web 2.0 AJAX oriented GUI in preview, compare and edit modes
  

Jahia 6 Releases (2009) 

New major features will include:

• Full Jahia Content Management System refactoring in order to support JSR 170 Level 1 and 2 + JSR283 (certainly based on Apache Jackrabbit)
• Refactoring of all Jahia GUI with JSF components
• Better scalability, better performance, better GUI and better integration between our different sub-systems (DMS, WCMS, Portal, BPM, Search and Collaborative servers)
  
• Various connectors on existing legacy systems
  

Technical Overview of Jahia 5.0

Click here to see the Jahia architecture.

So when is the next release coming out?

Here is the truth regarding Jahia releases:

Jahia products are mainly released on the basis of quality, and ~not~ according to a strict timetable (even if we have plans).

The developers in the Jahia community devote whatever time they can to work on the product according to 1) the new development projects (sponsorised by Jahia Ltd or directly by some customers) or 2) based on their free time.

But all jahia developers, even if most of them are working full time on the Jahia platform, also have other customer based professional services to provide that do take precedence. Then we simply cannot make date-oriented commitments for the product releases as they also depends on several other customers projects (and sponsors) which can be late for one reason or another.

Moreover all Jahia products will go through a public beta process before any final release. If a beta is not in circulation, then it's a good bet that a release is not forthcoming any time soon. Products sometimes go through several betas before final release. So if this is beta 1, then it still may not released any time soon.

The bottom line is that Jahia takes releases very seriously. We do not compromise the quality of our software by watching the calendar (and then ship something ready or not for marketing reasons). A release is ready when it is ready.

That may sound flip, but it ~is~ the truth. The delivery of production-quality, leading-edge software is not something anyone can prognosticate. If anyone tries, they are lying to you. That, we won't do ;-)

What we ~will~ do is release all of our development software as soon as it is developed in the public CVS and in prepackaged alpha/beta editions ("Release early, Release often" principle). This way you can judge for yourself how quickly the development is proceeding, and whether what is currently being developed will meet your future needs. If you need a feature right now, you can use the last nightly build available at your own risk, or roll your own patch by only extracting the key new features you want. We will do the maximum so that Beta or RC releases are as stable as possible. In order to help you upgrade as frequently as possible we also manage a distinct stable branch (the SP branch for "Service Pack" branch) which only contains fixes and no new major ongoing developments which could break the overall stability of the platform for several months.

IT project management is already quite difficult with a dedicated internal team of developers with a dedicated budget. Please understand that it is then even more difficult in a virtual, multi-companies and collaborative based environement.

Thanks for your patience and understanding!