TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
My opinion is that you should definitely drop the date in a filename.
Not only are the reasons mentioned here valid, but what
file_10_01_08.doc really means?
It may be 10th of Jan or 1st of Oct in some places, heck it might even
Standard date functions both in SCMs and filesystem take that into
Furthermore if you want to release a document/docset to be used
outside of SCM repository, you create a point in time snaphot, in SVN
called a tag. Not obligatory but a very good practice - it usually
tagged with a date, to give it a unique name.
Finally, since you haven't decided on SCM yet, I suggest you go to
distributed system such as Mercurial or GIT instead of centralized
like CVS or SVN. The main advantage is that when you're not connected
to central repository, you can happily create new version in your
local repo and sync them later. Merges are usually automatic. Briefly
CVS < SVN < GIT.
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-