>What's the best way to deal with this sort of change in the docs, now >that we have a release?
Easy: put the 0.90 docs in their own folder, let the "Documentation" point to the trunk documentation, but put a "release documentation" link at the top (or the other way around, make the release documentation the default and put a "trunk documentation" link on top) and provide both documentations. Make changes to the documentation in trunk as you do with the source, but with every release, just have a release-numbered directory with the documentation from that tag/branch. People _will_ need both versions of docs online, depending on what release they use. And since we most definitely will need it with later releases, why not start now? bye, Georg
