I've just posted the formatted log of our meeting from Thursday on the IRC page. In this meeting we discuss what we should target for M3.

The M2 release is the first one with a release cycle as short as three months. As such it was an experiment, and I think it was quite a success. The milestone is released even though not all assigned bugs could be closed in time. I think for now it's more important to send out the signal that we are actually able to stick to such a release cycle. May be we should be more realistic about what bugs/tasks to assign for M3... Find the release at our releases page.

Long awaited, this release marks the end of the transition from the old 'berlin-consortium.org' to the new 'fresco.org' with all the implications: new website and infrastructure, reworked and much enhanced source code structure, and quite a lot more. Read the M1 Release Notes or get it from our releases page.

Fresco now has its own issue tracker. It is used to track bugs, as well as tasks, and milestones. The tool will be further enhanced as we learn how to make good use of it, but it's already doing a terriffic job. Have a look at issues.fresco.org !