You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Current »

Since our last report in August, the Roller project has been making progress on two fronts: Roller 4.1 development and Roller 4.0 release candidate testing. And there are two areas where progress is needed: the Roller 3.1.1 release is stalled at RC6 and there is still some post graduation work to be done.

Roller 4.1 development

Roller 4.1 development has been proceeding in the roller_4.1_dev branch. The proposal to externalize user management has been implemented, as has the proposal to add a Tag Data API so other apps can get Roller's tag cloud data.

Apache Roller 4.0 RC9 available for testing

Roller 4.0 is a major new release that upgrades Roller to Jave SE 5, Struts 2, Velocity 1.5 and OpenJPA. This is will be the first release that does not require Hibernate or any other LGPL code to run. We released the first RC on August 11, 2007 (announcement here: http://tinyurl.com/22wq7y) and we've been testing RCs ever since. We're now up to RC9 and are hopeful that RC9 or RC10 will be the final.

Apache Roller 3.1 completed, 3.1.1 RC6 ready for testing

We shipped 3.1 on April 23, 2007. A number of significant problems (including an XSS bug) were found and fixed. We are now testing a fix release known as 3.1.1 RC6, made available October 4, 2007 (announcement here: http://tinyurl.com/ynmrtj).

Some post graduation work still TBD

Apache Roller graduated back in March and announced graduation and the Apache Roller 3.1 release on April 23, 2007. However, we've still got some work to do. We're still waiting for our JIRA instance to be setup (see https://issues.apache.org/jira/browse/INFRA-813).

Thanks to Vadim Gritsenko we now have a statistics page for Roller

Community health

Community health is good. Developers and users are active on the mailing lists, reporting bugs, submitting patches and seeking support. We've been having some difficulties getting 4.0 out the door because committers don't always have time to test each new RC, but on the other hand we are going though the process, fixing bug and the end result will be more solid release.

Other community related news...

  • No labels