Are you using any VCS? If you do, one way to manage this is to have separate "branches" (however a "branch" is managed in a given VCS) per release, and have the documentation's sources tracked by the same repository. This way, you can always "checkout" a branch and have the documentation's sources easily switched around.
~/santa On Wed, Jan 26, 2011 at 3:35 PM, Alexandre M <alexandre.mcl...@gmail.com>wrote: > Hi, > I'm new to Sphinx and I'd like to know what is the best practice to > manage many versions of a project? > > For instance, Django has documentation for the development version and > 1.2, 1.0 and older. How can I do that? > > Do I need to simply "cp -r" my folder and change the conf.py file and > output to a specific directory that will contain all versions built? > Or is there some way to add many versions in the same config file? > > Thanks. > > -- > You received this message because you are subscribed to the Google Groups > "sphinx-dev" group. > To post to this group, send email to sphinx-dev@googlegroups.com. > To unsubscribe from this group, send email to > sphinx-dev+unsubscr...@googlegroups.com<sphinx-dev%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/sphinx-dev?hl=en. > > -- You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to sphinx-dev@googlegroups.com. To unsubscribe from this group, send email to sphinx-dev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en.
