All right. Since there is circular dependency between cocoon and
forrest, I would suggest we release cocoon 2.1 first, allow forrest to
release a new version based on 2.1 and at that point forrestize our docs.
how does that sound?
But this circular dependency will always be there, so why not just get on with it. Anyway, Forrest uses a recent stable version of cocoon-2.1-dev, i.e. just off the bleeding-edge.
I agree we should get on with it too, as long as we don't break existing doc build capability. I think we should rely on the cvs version only for this transition stage. In the future, I don't want the docs build dependent on a cvs which from time to time will break. While the responsiveness of Forrest committers is incredible, I think Stefano's principle stated above is a best practice we should follow, especially for something like doc building (given the fact users just want docs, not necessarily the latest-greatest code which produces such docs).
All right, I think we need a vote on this. Please see next email.
Stefano.
