Changeset 8083 for branches/anuga_1_2_1/anuga_core/documentation/user_manual/anuga_whats_new.tex

Timestamp:

Nov 24, 2010, 4:55:55 PM (13 years ago)

Author:

habili

Message:

Bug fixes, including correct use of starttime and duration.

File:

• branches/anuga_1_2_1/anuga_core/documentation/user_manual/anuga_whats_new.tex (modified) (6 diffs)

branches/anuga_1_2_1/anuga_core/documentation/user_manual/anuga_whats_new.tex

@@ -1 +1 @@
 \documentclass{manual}
-
+\usepackage{hyperref}
 
 \title{ANUGA What's New}
 
-\author{Ole Nielsen}
+\author{Nariman Habili}
 
 % Please at least include a long-lived email address;
 % the rest is at your discretion.
 \authoraddress{Geoscience Australia \\
-  Email: \email{ole.nielsen@ga.gov.au}
+  Email: \email{anuga@ga.gov.au}
 }
 
@@ -48 +48 @@
 These lists are not comprehensive and we refer to the TRAC system for a complete audit trail of changes made to ANUGA.
 \begin{itemize} 
-    \item Timeline of all changes to the code base: \url{https://datamining.anu.edu.au/anuga/timeline}
-    \item List of completed tasks ordered by last modification time\footnote{Last time a closed ticket was modified will normally correspond to the time it was resolved. However, it is possible that it could be modified after being closed. Refer to the ticket change history if in doubt.}: \url{https://datamining.anu.edu.au/anuga/report/17}
-    \item Changesets between two releases: To see all changes between version 4669 and 4733, for example, visit:
+    \item Timeline of all changes to the code base: https://datamining.anu.edu.au/anuga/timeline
+    \item Changesets between two releases: To see all changes between subversion versions 4669 and 4733, for example, visit:
     \begin{itemize} 
       \item \url{https://datamining.anu.edu.au/anuga/changeset/4669} through to
@@ -59 +58 @@
 The release names take the form
 \begin{verbatim}
-  XX-YY_ZZ.EXT
+  AA-BB.CC.DD.EXT
 \end{verbatim}
 where
 \begin{itemize}
-  \item \code{XX} is the name of the anuga component, e.g. 
+  \item \code{AA} is the name of the anuga component, e.g. 
   \code{anuga}, \code{anuga\_viewer}, \code{anuga\_installation\_guide} or \code{anuga\_user\_manual}
-  \item \code{YY} is the name of the major revision, e.g. 1.0beta, which is unlikely to change very often unless the code has undergone a major change.
-  \item \code{ZZ} is the Subversion revision number of this release. Every change to ANUGA causes the revision number to increment so this number uniquely identifies the version of ANUA. This is also known as the changeset number. 
+  \item \code{BB} is the major revision number. The major revision number is unlikely to change very often unless the code has undergone a major change.
+  \item \code{CC} is the minor revision number. This number will increase when the code undergoes major bug fixes, changes to the interface, optimisation and the addition of minor features.
+  \item \code{DD} is the minor revision number. This number will increase when the code undergoes minor bug fixes.
   \item \code{EXT} is the file name extension \code{tgz}\footnote{Internet explorer has the habit of renaming the .tgz files to .gz - the remedy is to rename them back or use another browser such as Firefox.} used for source code or \code{pdf} used for documentation.
 \end{itemize}
@@ -79 +79 @@
 here. Refer to the Subversion 
 log (https://datamining.anu.edu.au/anuga/timeline) and closed tickets
-https://datamining.anu.edu.au/anuga/report/17) for all changes in ANUGA.
+https://datamining.anu.edu.au/anuga/report/10) for all changes in ANUGA.
 
 \section{Bleeding Edge}
@@ -86 +86 @@
 forcing terms. There is also activity in the area of viewers and installers.
 
-\section{Release Name: anuga-1.2beta, Date: June 2010}
+\section{Release Name: anuga-1.2.0, Date: July 2010}
 Breaks code compatibility with older ANUGA versions. Please see the ANUGA wiki for migration instructions.
 Simplified API, with more logical module locations and names. 
@@ -92 +92 @@
 Support for user-specified breaklines.
 Speed optimisations - fitting is around 25 percent faster.
-Various bug fixes - see trac.
+Various bug fixes - see trac. Note the new versioning system.