In message 42B8385F.2070202@fsforth.de you wrote:

is it possible to give an estimation when the next release will be done?

I'm still trying to figure out which way to go regarding tooling - version control system, patch database, patch submission, etc. At the moment it looks very much as if we'll use git - it seems to work fine for the purposes needed, it is much faster than other alternatives, and it's developing at high speed.

Once I figures out how to use this in a n efficient way for U-Boot, I will focus on merging the long (and growing) backlog of patches (approx 220 atm).

It is not clear yet where on this way it makes sense to call the current state a new release.

If you need something you can use as reference: chose any of the CVS tags in the tree and call this your "release" version.

Best regards,

Wolfgang Denk