A huge release like 1.2 always has some issues that come along. Those have now been addressed in ImpressCMS 1.2.1, which is now has reached Release Candidate status, after a beta cycle which saw very few bugs!

ImpressCMS has had a short, but notable history - founded in 2007, an initial release in January 2008, 3rd place in Packt Publishing's Most Promising Open Source CMS in 2008 and 1st place in 2009, a 2008 finalist in SourceForge's Community Choice Awards, 32 separate releases and almost 10,000 commits in its code repository.

This release is a Release Candidate release, meaning it is not yet ready for use on a live site!

Due to some recurrent reliability issues with our current SVN provider, we decided to migrate the development architecture servers (Subversion and Trac) to SourceForge. In order to do that, subversion access will have to be suspended for all users while the move is done. This migration will start Monday March 1st, 6 AM EST at which point people with SVN write access will see their access change to read only.

All the developers accounts will be transfered to SourceForge and your write access will be restored as quickly as possible. We plan the migration to last a few days. We will notify you when it is completed.

A huge release like 1.2 always has some issues that come along. Those have now been resolved in ImpressCMS 1.2.1, which is now ready as a Beta release! ImpressCMS 1.1 was released at the end of October 2008 and the scope of changes in this release has kept the developers, testers and translators busy.

ImpressCMS has had a short, but notable history - founded in 2007, an initial release in January 2008, 3rd place in Packt Publishing's Most Promising Open Source CMS in 2008 and 1st place in 2009, a 2008 finalist in SourceForge's Community Choice Awards, 32 separate releases and almost 10,000 commits in its code repository.

This release is a Beta release, meaning it is not for use on a live site!

 

All projects need to have a plan for where they want to go and ImpressCMS is no different. In the past, we have had several versions of roadmaps that quickly got out of synch as we adapted to current needs and conditions. We also tried to detail several releases in the future. In order to allow for more flexibility, we are simplifying our roadmap(s) - we will have 1 overview, published on our project site, providing the goals and objectives of the current release and future releases. There will be a technical roadmap maintained in Trac with all the how-to's and tasks needed to implement the features of the release and meet the goals and objectives.