[Framework-Team] post-3.0: tags? branches?

[Wichert Akkerman]

With 3.0-final coming up I have been wondering how to handle the 3.0
bundle. I would like to have this bundle be as stable as possible, which
suggests that it ca not keep using trunks everywhere. But most products
and packages will not have a seperate stable branch for their current or
upcoming release either. So what to do?

One option I've been pondering is to update the bundle to use tags or
revision pins for any package or product which does not have a seperate
maintenance branch. Possible that is a somewhat extreme thing to do
though.

I would like to hear some opinions on this before I make any decisions.
So... what do you think?

Wichert.



-- 
Wichert Akkerman <wichert at wiggy.net>    It is simple to make things.
http://www.wiggy.net/                   It is hard to make things simple.