--- taskjuggler-2.3.0/docs/en/ChangeLog.xml	2006-09-05 18:27:45.000000000 +0200
+++ taskjuggler-2.3.1/docs/en/ChangeLog.xml	2007-01-31 20:21:32.000000000 +0100
@@ -999,4 +999,105 @@
 </itemizedlist></para>
 
 </sect2>
+<sect2 id="Changelog_2_3_1"><title>Version 2.3.1 (2007-01-30)</title>
+<para>
+<itemizedlist mark='opencircle'>
+
+<listitem><para>Added support for automatic macros like
+<computeroutput>now</computeroutput>,
+<computeroutput>projectstart</computeroutput> and
+<computeroutput>projectend</computeroutput>.</para></listitem>
+
+<listitem><para>Added monthly calendar HTML report.</para></listitem>
+
+<listitem><para>Added <computeroutput>period</computeroutput> property
+as a shortcut for the combined use of
+<computeroutput>start</computeroutput> and
+<computeroutput>end</computeroutput>.</para></listitem>
+
+<listitem><para>Added more details to the pop-up info for tasks and
+resources in the UI.</para></listitem>
+
+<listitem><para>Added support for warnings and turned some
+non-critical errors into warnings.</para></listitem>
+
+<listitem><para>Improved scheduling performance for projects with
+long dependency chains.</para></listitem>
+
+<listitem><para>Added new attribute
+<computeroutput>purge</computeroutput> to clear inherited allocations 
+and flags from a task or resource.</para></listitem>
+
+<listitem><para>Fixed complexity explosion in loop detector and
+critical path analyzer. Larger projects that made heavy use of
+inherited dependencies had an exponentially growing run time of these
+components.</para></listitem>
+
+<listitem><para>The threshold for the critical path detection now
+defaults to 10%. All pathes that have less than 10% slack time will be
+marked as critical.</para></listitem>
+
+<listitem><para>Fixed problem where editor tools were doubled when
+"Open Recent" was used while editor was open. This also triggered a
+crash on program exit.</para></listitem>
+
+<listitem><para>Fixed double headline problem in most HTML
+reports.</para></listitem>
+
+<listitem><para>Fixed a bug in the coloring of tasks in HTML reports
+that had a 'complete' specification.</para></listitem>
+
+<listitem><para>Fixed documenation for usage of sorting modes for
+scenario specific columns in reports and make them work
+properly.</para></listitem>
+
+<listitem><para>Force <computeroutput>now</computeroutput> date to be
+aligned to the timing resolution.</para></listitem>
+
+<listitem><para>Fixed a major bug in the handling of multiple
+scenarios. Values were inherited from peer scenarios instead of their
+parents.</para></listitem>
+
+<listitem><para>More meaningful error messages for some impossible
+combinations of fixed start/end times and
+dependencies.</para></listitem>
+
+<listitem><para>For technical reasons we had to limit the
+timingresolution between 5 minutes and 1 hour. Larger resolutions
+caused too many hazards in corner case situations.</para></listitem>
+
+<listitem><para>Fixed <computeroutput>gaplength</computeroutput> for
+time units other than days.</para></listitem>
+
+<listitem><para>Really hide all inherited dependency arrows in Gantt
+chart.</para></listitem>
+
+<listitem><para>Fix several crashes when the user is viewing reports
+in the UI after an unsuccessfull scheduling run.</para></listitem>
+
+<listitem><para>Fix sorting of tasks in interactive resource reports
+and sorting of resources in interactive task
+reports.</para></listitem>
+
+<listitem><para>The resource reporting in htmlweeklycalendar reports
+has been fixed. The report can now be used in task or resource
+reporting mode. The default is the task reporting mode which is
+closest to the previous behaviour.</para></listitem>
+
+<listitem><para>Fixed values of the revenue and profit column in
+resource reports. Resources can never generate a revenue so the value
+must always be 0.</para></listitem>
+
+<listitem><para>Fixed crash when printing resource reports from the UI
+that had a <computeroutput>hierarchyindex</computeroutput>
+column.</para></listitem>
+
+<listitem><para>The completion degree of container tasks that have sub
+tasks with and without resource allocations was reported as 0. This
+has been replaced with "in progress" as the completion degree cannot be
+calculated.</para></listitem>
+
+</itemizedlist></para>
+
+</sect2>
 </sect1>