[Openvas-commits] r1535 - trunk/doc/website

[scm-commit@wald.intevation.org]

Author: mwiegand
Date: 2008-10-13 16:16:11 +0200 (Mon, 13 Oct 2008)
New Revision: 1535

Modified:
   trunk/doc/website/roadmap.htm4
Log:
Updated road map, removed features from road map that are already implemented.


Modified: trunk/doc/website/roadmap.htm4
===================================================================
--- trunk/doc/website/roadmap.htm4	2008-10-13 14:04:43 UTC (rev 1534)
+++ trunk/doc/website/roadmap.htm4	2008-10-13 14:16:11 UTC (rev 1535)
@@ -29,17 +29,9 @@
 <h2>Roadmap of OpenVAS project</h2>
 
 <p>
-This is the current (September 2008) status of the roadmap for OpenVAS.
+This is the current (October 2008) status of the roadmap for OpenVAS.
 <p>
 
-<h3>September 2008: Release of the comprehensive documentation "OpenVAS Compendium"</h3>
-
-<p>
-Work has already begun on providing a comprehensive documentation for all
-OpenVAS components. This will replace inaccurate and outdated documentation
-inherited from Nessus and documentation not available under a Free license.
-</p>
-
 <h3>October 2008: German translation of OpenVAS Compendium</h3>
 
 <p>
@@ -51,7 +43,7 @@
 
 <p>
 Depending on the problems found with OpenVAS 2.0-beta1, a second beta
-release is planned for 4-8 weeks after this beta1 release.
+release is planned for 4-8 weeks after the beta1 release.
 </p>
 
 <h2>Ideas for future OpenVAS functionalities</h2>
@@ -98,13 +90,6 @@
      as well.
      </p>
 
-<li> New Client-Server protocol:
-     <p>
-     Replace the old Nessus Protocol by something
-     based on standard protocol technologies and
-     iron out current weaknesses like the character encoding.
-     </p>
-
 <li> Trace function:
      <p>
      Show sets of queries. Each query is composed of the rule
@@ -130,11 +115,5 @@
 <li> Consider popular issue-tracker or helpdesk systems to pull issues from
      scan reports, sort them, prioritize and assign them.
 
-<li> Besides hole, warning, hint add two further classes: info and debug.
-     These could help to better understand what was going on during the scan.
-     The simple thesis that anything went well if no report is given ignores
-     the potential occurrence of various technical problems that might have
-     suppressed messages or prevented execution of tests.
-
 </ul>