Flock development status:

• Automated builds are happening again
• MacOS builds will be fixed very soon
• Spec is mostly done
• Early adoptors release functionality complete mid-December
• Early adoptors release functionality complete mid-January

As Software’s whipping boy reports on his significant accomplishment:

Well the first phase of getting tinderbox back is there. Automated builds are occurring, but because of the lack of tools to manipulate mercurial by date they don’t build from quite the right source code.
Software’s whipping boy

We are getting there. It is functional, but we, particularly Robin and I won’t be satisfied with some of the loss of functionality that we had with CVS and Bonsai, so Robin is still hacking away at it. We will have some loss, but distributed SCM is a huge gain for the developers.

With Mercurial up and running, Erwan and others have checked in fixes to quite a few issues that could not be fixed while the build system migration was taking place.

Termie did an excellent job describing Flock Progess: Specs and Roadmap. Progess does rule! Before skipping town Termie and Factoryjoe completed most of their work on the specification.

As described in my email to flock-dev discussion list today, within the couple of days, the specification will be accessibly by the community (bug Daryl who was just given this task). Here are the other details in that email:

Manish ownsthe MacOS builds working again, and any other significant regressionsso that we can estable a baseline for the new work. That does not meanhe necessarily has to fix the breakages. He fixes the them or uses bugsto drive them to resolution — from a bug, I know who to harass on anissue. I can’t verify the recently fixed bugs until this is done.
The milestone for that work is still ms04 paperbag.
Anthony, this includes getting Flickr uploader working on Linux

Feature complete is targeted for December 15th. As Anthony described all of the spec’d work has been assigned, and the bugs all have milestone ms05 feature complete.

There are a large number of bugs currently with a milestone of Early Adopters
Each developer should to go through their bugs in this milestone then either:
a) If part of the Early Adopter release, move the bugs to milestone ms05 feature complete, and as appropriate add the details from the bug to the specification
b) If you think it will be in the release after Early Adopters, move the bug to milestone beyond
c) For minor bugs that will not make it into ms05 feature complete, ensure that their state is ASSIGNED, and leave them in ms06 early adopters.I will sit down and review this list with you, because too many bugs inthis category raises the risk of not being able to release on time.
d) if you don’t think the bug fits the medium term goals then assign the bug to “[email protected]” and the milestone to –.

Technorati Tags: flock, flock.com, flock browser, social browser, web browser, browser, blogging, beta, firefox