<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
+1 for the idea of relegating old content to a history museum to
reduce maintenance. <br>
<br>
There can be other transitions in a package's life which change it
so dramatically that it's not worth maintaining the previous
content. However, the previous version is still there - in the
version history. Perhaps there could be a macro that let's an
author refer to a history tag and display a message something like
"The version of this page prior to <XYZ> his <here>,
where <XYZ> could be "catkin" or "groovy" or "API version 2.0"
or "new-sensor-version" etc. etc. This could work for tutorial pages
too.<br>
<br>
Paul Bouchier<br>
<br>
<div class="moz-cite-prefix">On 11/22/2014 08:24 PM, Rud Merriam
wrote:<br>
</div>
<blockquote cite="mid:5471536E.9020208@arrl.net" type="cite">
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
<div class="moz-cite-prefix">As someone new to ROS I find it very
frustrating to have the pre-catkin documentation in the Wiki. <br>
<br>
I would suggest you quickly move the pre-catkin material to a
separate Wiki for those still using those versions. Then begin a
rolling update system for new releases. You might keep three
release in the main Wiki while rolling previous releases into a
historical Wiki separate from the pre-catkin Wiki. That might
entail too much work, I realize. Maybe a diff/merge through a
version control system would work? I suggest that anyone working
with versions 3 years out of date probably can figure out the
documentation even if it is not perfect. <br>
<br>
<div class="moz-signature"><font color="#000080" face="Comic
Sans MS"><br>
- 73 - <br>
<b> Rud Merriam K5RUD<br>
</b> <i> <a moz-do-not-send="true"
href="http://mysticlakesoftware.com/">Mystic Lake
Software</a><br>
</i> <br>
<br>
</font></div>
<br>
</div>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
ros-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ros-users@lists.ros.org">ros-users@lists.ros.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ros.org/mailman/listinfo/ros-users">http://lists.ros.org/mailman/listinfo/ros-users</a>
</pre>
</blockquote>
<br>
</body>
</html>