I intend to fix this by adjusting the rsync push location to match what nova.version.canonical_version() says. At release time, we can move symlinks around to make something like nova.openstack.org/trunk point to the new dev release, so that e.g. nova.openstack.org/bexar (and nova.openstack.org/2011.1) are frozen.
So, once Cactus is open for development, going to nova.openstack.org will redirect you to nova.openstack.org/trunk.
On the filesystem trunk/ and cactus /will be symlinks to 2011.2/ which is where the nova job will push documentation.
I intend to fix this by adjusting the rsync push location to match what nova.version. canonical_ version( ) says. At release time, we can move symlinks around to make something like nova.openstack. org/trunk point to the new dev release, so that e.g. nova.openstack. org/bexar (and nova.openstack. org/2011. 1) are frozen.
So, once Cactus is open for development, going to nova.openstack.org will redirect you to nova.openstack. org/trunk.
On the filesystem trunk/ and cactus /will be symlinks to 2011.2/ which is where the nova job will push documentation.