Santoso Wijaya actually answered this quite well back in February; you need to use a version control system. I would suggest either git (http://git-scm.com/) or mercurial (http://mercurial.selenic.com/). Git may be better for your needs primarily because of its cherry- picking abilities (see http://schacon.github.com/git/git-cherry-pick.html), which would let you pull changes from one branch into another fairly easily. Note that git is probably one of the most powerful version control systems out there today, and will take some work on your part to learn how to use well.
Whatever system you choose to use, make sure you can script it; that way, you can easily make your changes, and then when you push your changes into the repository, all your documentation gets updated immediately. Does that all make sense? Thanks, Cem Karan Mateusz Łoskot wrote: > 2011/10/17 Mateusz Łoskot <[email protected]>: > > Hi, > > > > I'd like to follow-up the old thread: How to manage many versions? > > > > http://groups.google.com/group/sphinx-dev/browse_thread/thread/fb8ba5cfa890b587/ > > > > I maintain a small library project written in C++. > > I'd like to use Sphinx to maintain the library website + user > > documentation per release version. > > I have found similar thread > > > > How to manage many versions? > > Forgive me if I'm being annoying bumping this thread, but I really > would appreciate > any help, any suggestion of good practice regarding the handling multi-release > documentation. > > Anyone anything? > > Best regards, > -- > Mateusz Loskot, http://mateusz.loskot.net > Charter Member of OSGeo, http://osgeo.org > Member of ACCU, http://accu.org -- You received this message because you are subscribed to the Google Groups "sphinx-dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sphinx-dev?hl=en.
