mike's web log

 

Blog Search


(Supports AND)

 

Google Ads

 

Feed

Subscribe to the RSS feed for this blog.

See this post for info on full versus truncated feeds.

 

Quote

The predisposition for languages is as mysterious as the inclination of certain people for mathmatics or music and has nothing to do with intelligence or knowledge. It is something separate, a gift that some possess and others don't.

Mario Vargas Llosa



 

Navigation






<May 2013>
SMTWTFS
2829301234
567891011
12131415161718
19202122232425
2627282930311
2345678


 

25 Most-Visited Entries

 

Categories

  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
  RSS
 

Blogs I Read

 

Contact

Email me
 

Blog Statistics

Dates
First entry - 6/27/2003
Most recent entry - 4/9/2013

Totals
Posts - 2293
Comments - 2463
Hits - 1,527,900

Averages
Entries/day - 0.63
Comments/entry - 1.07
Hits/day - 423

Update every 30 minutes. Last: 8:35 AM Pacific

 
   |  Handling version changes in documentation

posted at 06:12 PM | | |

Just wondering what sorts of examples people might have of documentation sets that cover multiple versions of the same product. In our doc set in MSDN, we basically republish each complete doc set, but updated for the new version with corrections and new features:


The advantage is you can go right to your version and be assured that what you're reading applies to you. The disadvantage is that the versions pile up (4 versions and counting), with a lot of overlap, which is inefficient in various dimensions.

Are you familiar with a doc set that handles versioning differently than this? (Conceptual or API reference or both.) If so, leave a comment with a link.

Thanks!

[categories] , ,