Merged over changes relating to trac paths and so on. Updated generat…

…ed docs.
qgis · Jun 5, 2011 · de66c87 · de66c87
1 parent 1b19b79
commit de66c87
Show file tree

Hide file tree

Showing 8 changed files with 702 additions and 2,357 deletions.
diff --git a/CODING b/CODING
@@ -596,10 +596,10 @@ easily, and help us deal with the patches that are sent to use easily.
 
 If the patch is a fix for a specific bug, please name the file with the bug
 number in it e.g.  bug777fix.patch, and attach it to the original bug report
-in trac (https://trac.osgeo.org/qgis/).
+in trac (http://hub.qgis.org/projects/quantum-gis).
 
 If the bug is an enhancement or new feature, its usually a good idea to create
-a ticket in trac (https://trac.osgeo.org/qgis/) first and then attach you 
+a ticket in trac (http://hub.qgis.org/projects/quantum-gis) first and then attach you 
 
 
     2.7.2. Create your patch in the top level QGIS source dir
@@ -868,7 +868,7 @@ test before fixing the bug will let you automate the testing for bug
 resolution in an efficient manner.
 
 To implement your regression test, you should follow the naming convention of
-regression<TicketID> for your test functions. If no trac ticket exists for the
+regression<TicketID> for your test functions. If no redmine ticket exists for the
 regression, you should create one first.  Using this approach allows the person
 running a failed regression test easily go and find out more information.
 

diff --git a/CODING.pdf b/CODING.pdf
diff --git a/INSTALL b/INSTALL
@@ -1,10 +1,10 @@
 Quantum GIS (QGIS)
 Building QGIS from source - step by step
-Sunday May 29, 2011
+Sunday June 05, 2011
 
 
-Last Updated: Sunday May 29, 2011
-Last Change : Friday May 20, 2011
+Last Updated: Sunday June 05, 2011
+Last Change : Thursday June 02, 2011
 
 
   1. Introduction

diff --git a/INSTALL.pdf b/INSTALL.pdf
diff --git a/doc/CODING.t2t b/doc/CODING.t2t
@@ -575,10 +575,10 @@ easily, and help us deal with the patches that are sent to use easily.
 
 If the patch is a fix for a specific bug, please name the file with the bug
 number in it e.g.  **bug777fix.patch**, and attach it to the original bug report
-in trac (https://trac.osgeo.org/qgis/).
+in trac (http://hub.qgis.org/projects/quantum-gis).
 
 If the bug is an enhancement or new feature, its usually a good idea to create
-a ticket in trac (https://trac.osgeo.org/qgis/) first and then attach you 
+a ticket in trac (http://hub.qgis.org/projects/quantum-gis) first and then attach you 
 
 === Create your patch in the top level QGIS source dir ===
 
@@ -854,7 +854,7 @@ test **before** fixing the bug will let you automate the testing for bug
 resolution in an efficient manner.
 
 To implement your regression test, you should follow the naming convention of
-regression<TicketID> for your test functions. If no trac ticket exists for the
+regression<TicketID> for your test functions. If no redmine ticket exists for the
 regression, you should create one first.  Using this approach allows the person
 running a failed regression test easily go and find out more information.
 

diff --git a/doc/INSTALL.html b/doc/INSTALL.html
@@ -45,13 +45,13 @@
 <DIV CLASS="header" ID="header">
 <H1>Quantum GIS (QGIS)</H1>
 <H2>Building QGIS from source - step by step</H2>
-<H3>Sunday May 29, 2011</H3>
+<H3>Sunday June 05, 2011</H3>
 </DIV>
 
 <DIV CLASS="body" ID="body">
 <P>
-Last Updated: Sunday May 29, 2011
-Last Change : Friday May 20, 2011
+Last Updated: Sunday June 05, 2011
+Last Change : Thursday June 02, 2011
 </P>
 <DIV CLASS="toc">
 
@@ -2275,5 +2275,5 @@ <H1>6. Authors and Acknowledgments</H1>
 
 </DIV>
 <!-- html code generated by txt2tags 2.6 (http://txt2tags.org) -->
-<!-- cmdline: txt2tags -t html -o INSTALL.html INSTALL.t2t -->
+<!-- cmdline: txt2tags -o INSTALL.html -t html INSTALL.t2t -->
 </BODY></HTML>
diff --git a/doc/index.dox b/doc/index.dox
@@ -36,7 +36,7 @@ developers.</li> </ul>
 
 \section index_bugs Bug Reporting
 If you think you have found a bug, please report it using our <a
-href="https://trac.osgeo.org/qgis/">bug tracker</a>. When reporting bugs,
+href="http://hub.qgis.org/projects/quantum-gis">bug tracker</a>. When reporting bugs,
 please include some contact information in case we need help with replicating
 your issue.