The Apache Velocity project had an exciting first quarter of 2007 with the long anticipated release of the Velocity engine.
We have no board-level issues at this time.
Our various releases since the beginning of 2007 sent a clear message out to the Java world that the Velocity project was never dormant and is picking up speed. The number of messages on the develpment and user lists reflect this nicely. The Velocity Engine 1.5 release was covered in depth on various Java related web sites (e.g. theserverside.com).
The Velocity project tried to organize a formal press release for the Velocity engine release and even postponed the official release date to get possible better coverage. Will Glass-Husain worked as our liaison with the PRC.
Unfortunately, this press release did not work out. While we tried to work in a timely manner (we started six weeks before the actual release date collecting quotes from Velocity users for the release and circulated drafts to the PRC), Will reported that the PRC did not respond at times and seemed to be dormant and he had to ping the chair directly. Various objections came up only hours before the intended release date even though we tried to give ample time for the PRC to review drafts. In the end, the Velocity PMC decided to withdraw the press release draft.
The experience working with the PRC was interesting, though not entirely good. We hope that the PRC and other PMCs can learn from our experience and we streamline the review/feedback process for the next time.
The Velocity project created three new sub projects in Q1:
The Velocity project has discussed to sponsor the incubation of the Click Framework, which is based on Velocity. The Click community has already reached consensus that they want to be incubated to become an Apache project; discussion is still open whether this will be a sub-project of Velocity or a TLP in its own right. We expect to see a formal incubation proposal in Q2.
Claude Brisson was voted to become a member of the Velocity PMC on April, 3rd. He accepted his nomination.
No new committers were added to the Velocity project in Q1.
The Velocity community is proud that a proposal to the Google Summer of Code 2007 was accepted:
Supun Madhushanka Kamburugamuva will work to improve the Velocity Macro capabilities (see: http://code.google.com/soc/asf/appinfo.html?csaid=75DF2BC1378C84A5 ), Will Glass-Husain, Velocity PMC member will mentor him.
The Velocity Engine team released Apache Velocity 1.5 on March 13th.
Work on Velocity 1.x continues at the usual pace.
Velocity Tools currently works towards a 2.0 release. No release have been made in Q1.
Since the inception of the Velocity TLP, the DVSL code base was not changed and there seems to be no interest in it from users and developers. We will discuss mothballing it in Q2.
Anakia is an old/new tool that used to be part of the Velocity engine. It was spun out of the engine after the 1.5 release to allow different release cycles.
Velocity Anakia 1.0, which is just a repackaged version, was released on April 28th.
Texen is an old/new tool that used to be part of the Velocity engine. It was spun out of the engine after the 1.5 release to allow different release cycles.
Velocity Texen 1.0, which is just a repackaged version, was released on April 28th.
The DocBook Framework is intended to help everyone that wants to write documentation in an industry-wide accepted format that is suitable for printing and on-line viewing.
For the time being (and because it is used to generate the Velocity documentation), this stays as part of the Velocity project. If it fits better into another TLP in the future, it is expected to leave Velocity).
Velocity DocBook Framework 1.0 was released on April 9th.