There are lots of threads on the difficulty of upgrading a TWiki install. It is even harder if you have made extensive local customisations. So I'm wondering, why not have all the TWiki files, including everything under bin and lib, ship with their RCS files from the development area. That would allow the user to upgrade by issuing an RCS sync command.

In addition, if I have made local changes, I could do them using RCS too rather than just hacking the file in place. Then when a new version is released at twiki.org I could use RCS to merge the two and have it show conflicting changes. I'm not too familiar with RCS, but I'm guessing there is a way to make parallel changes to a file by creating a branch, and then having RCS do the merge between the two files?

-- MartinWatt - 09 Nov 2002

I just came across this page (while looking for some help in learning to setup RCS or CVS at home for some plain text files), and I have no idea whether this would work or not, but the idea sure sounds intriguing. So, I'm trying to bring attention to this page again (get it in recent changes) in hopes that somebody with more knowledge than I can express an opinion — could this be as simple as it sounds?

-- RandyKramer - 09 Nov 2003

Both TWiki and Owiki.org already allow you to do code upgrades using CVS. RCS would not be useful as it does not do multiple directories. Additionally, OWiki facilitates ReadOnlyOfflineWiki - i.e. replication of content onto (e.g.) your laptop. Very handy.

-- MartinCleaver - 09 Nov 2003

Great! Thanks for the response!

-- RandyKramer - 10 Nov 2003

---

CategoryUpgradeStrategy