<?xml version="1.0" encoding="ISO-8859-1"?>

<sect1>
  <sect1info>

<!-- Please, do NOT edit the following revision history by hand. Use the
"make <module_name>.revision" target instead.  -->

<revhistory>
      <revision>
        <revnumber>1.en.lproof</revnumber>
        <date>YYYY-MM-DD</date>
        <authorinitials>tbn</authorinitials>
      </revision>
      <revision>
        <revnumber>1.en.ispell</revnumber>
        <date>YYYY-MM-DD</date>
        <authorinitials>tbn</authorinitials>
      </revision>
      <revision>
        <revnumber>1.en.pproof</revnumber>
        <date>YYYY-MM-DD</date>
        <authorinitials>tbn</authorinitials>
      </revision>
      <revision>
        <revnumber>1.en.tproof</revnumber>
        <date>2002-10-14</date>
        <authorinitials>fm</authorinitials>
      </revision>
      <revision>
        <revnumber>1.en.write</revnumber>
        <date>2002-10-11</date>
        <authorinitials>cb</authorinitials>
      </revision>
    </revhistory></sect1info>
  <title>Introduction</title>

  <para>This document will list all features that are planned to be
  implemented in future Borges releases. The information in here will
  be useful for developers because they should find here all the
  necessary information to provide a feature. The document will also
  be interesting for users wishing to know what to expect from
  Borges.</para>

  <para>Each feature is identified by a unique <acronym>ID</acronym>:
  if there's a Sourceforge <acronym>RFE</acronym> for that feature, we
  use its <acronym>ID</acronym> with the <acronym>sf</acronym> prefix,
  if not we use the <literal>fx</literal> (Feature # x) ID. For
  SourceForge <acronym>RFE</acronym>s you can check the developer in
  charge of a feature and its status in <ulink
  url="http://sourceforge.net/projects/borges-dms/">Borges'
  SourceForge web site</ulink>.</para>
  <!-- FABITOREM 20021014: maybe add something about non-SF RFEs or
  convert ALL non-SF RFEs to SF RFEs ? -->

  <para>As soon as a feature has been implemented and tested, and when
  a new Borges version including it comes out, the implementor must
  add a paragraph in this document at the end of the features section
  stating in which Borges version this feature has been implemented.</para>
  <note>
    <para>Needless to say programmers must:<orderedlist>
	<listitem>
	  <para>Comment the code;</para>
	</listitem>
	<listitem>
	  <para>Document, in the Borges user manual, all modifications
	  made;</para>
	</listitem>
	<listitem>
	  <para>Possibly document changes in the Borges programer's
	  reference manual.</para>
	</listitem>
      </orderedlist></para>
  </note>
</sect1>

<!-- Keep this comment at the end of the file
Local variables:
mode: xml
sgml-parent-document: ("../../manuals/Borges-Roadmap/master.xml" "sect1")
End:
-->