The plan this weekend is to make some iteration plans for AudioMan2 and Durham. An iteration plan will probably have:

- a list of things to do in this iteration
- a list of things to do in the short term
- a list of things to do in the long term

User feedback of iteration x determines which things from the short and long term buckets go into iteration x+1.

To make things easy it's probably best if AudioMan2, Durham and jid3v2 all have synchronized release schedules with the same version numbers. It will be just like how the Rich Client Platform (RCP) is released with Eclipse and they have the same version numbers.

AudioMan2 has dependencies on Durham so either Durham will hold up implementation of features in AudioMan2 or AudioMan will drive Durham development and iteration priorities. It might even be better for a Durham feature to be implemented one iteration before it is needed, so it has a chance to stabilize.

How long is an iteration? Open source projects are less predictable here because you never know how much free time people will have to contribute. The early iterations will definitely be "when it's done" but later we could release more often and on a regular schedule. We don't want iterations to get too long or too big.

The other thing I want to do is make a nice diagram of how all of the AudioMan projects and components will work together. Hopefully that will help to answer questions like: where does the database (data persistence) fit in?