From 03525ea0378c9f28d6cc298ca8a9ac0f6c020190 Mon Sep 17 00:00:00 2001 From: Tim Sutton Date: Sun, 5 Jun 2011 13:44:05 +0200 Subject: [PATCH] Updated references to bug tracker to point to hub website --- CODING | 6 +++--- INSTALL | 20 +++++++++++++------- doc/CODING.t2t | 6 +++--- doc/INSTALL.html | 8 ++++---- doc/index.dox | 2 +- doc/index.html | 23 ++++++++++++++--------- 6 files changed, 38 insertions(+), 27 deletions(-) diff --git a/CODING b/CODING index 2151d59c07c..972e9ea17a2 100644 --- 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 for your test functions. If no trac ticket exists for the +regression 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/INSTALL b/INSTALL index 558a91ca444..6164df3f060 100644 --- 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 @@ -27,7 +27,7 @@ Last Change : Friday May 20, 2011 5.1. Install Qt4 from disk image 5.2. Install development frameworks for QGIS dependencies 5.3. Install CMake for OSX - 5.4. Download QGIS source from github + 5.4. QGIS source 5.5. Configure the build 5.6. Building 6. Authors and Acknowledgments @@ -1496,10 +1496,16 @@ tarball, then cd to the source folder and: sudo make install - 5.4. Download QGIS source from github - ===================================== + 5.4. QGIS source + ================ -Go to the github QGIS project page: +Unzip the QGIS source tarball to a working folder of your choice +(/usr/somewhere is not a good choice as it's hidden and requires root +privileges). If you are reading this from the source, you've already done +this. + +If you want to experiment with the latest development sources, go to the github +QGIS project page: http://github.com/qgis/Quantum-GIS diff --git a/doc/CODING.t2t b/doc/CODING.t2t index 62697ef4e03..48c1dc2f4ab 100644 --- 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 for your test functions. If no trac ticket exists for the +regression 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 index 9b81956e11c..3aac281bca8 100644 --- a/doc/INSTALL.html +++ b/doc/INSTALL.html @@ -45,13 +45,13 @@ pre, code { font-family: monospace }

-Last Updated: Sunday May 29, 2011 -Last Change : Friday May 20, 2011 +Last Updated: Sunday June 05, 2011 +Last Change : Thursday June 02, 2011

@@ -2291,5 +2291,5 @@ The following people have contributed to this document:
- + diff --git a/doc/index.dox b/doc/index.dox index c8dda52b140..493eb93782d 100644 --- a/doc/index.dox +++ b/doc/index.dox @@ -36,7 +36,7 @@ developers. \section index_bugs Bug Reporting If you think you have found a bug, please report it using our bug tracker. When reporting bugs, +href="http://hub.qgis.org/projects/quantum-gis">bug tracker. When reporting bugs, please include some contact information in case we need help with replicating your issue. diff --git a/doc/index.html b/doc/index.html index 91f112671d8..c1ab1c77ded 100644 --- a/doc/index.html +++ b/doc/index.html @@ -10,7 +10,7 @@ Quantum GIS Documentation
- Version 1.7.0 Wroclaw
+ Version 1.7.0 Wrocław
Please read this entire document for important information about this release.
You find a PDF manual of the current version on the QGIS website. @@ -25,7 +25,7 @@ information on QGIS is available on the web page at http://qgis.org. -->

Whats new in Version 1.7.0 'Wrocław'?

This release is named after the town of Wrocław in Poland. The Department of Climatology and Atmosphere Protection, University of Wrocław kindly hosted our -last developer meeting in November 2010. Please note that this is a release in +developer meeting in November 2010. Please note that this is a release in our 'cutting edge' release series. As such it contains new features and extends the programmatic interface over QGIS 1.0.x and QGIS 1.6.0. As with any software, there may be bugs and issues that we were not able to fix in time for @@ -430,7 +430,7 @@ markers. Keyboard shortcuts: New feature: configure shortcuts for actions within main window of qgis! -See menu Setting->Configure shortcuts +See menu Setting->Configure shortcuts Map Composer: @@ -471,7 +471,7 @@ Projects Management: QGIS now includes support for project relative position of file data sources and svgs. The saving of relative paths of file data sources is optional. -PostGIS & the PostgreSQL Provider: +PostGIS & the PostgreSQL Provider: You can now select the SSL mode when adding a new DB connection. Turning off SSL encryption can greatly improve performance of PostGIS data loading where @@ -655,7 +655,9 @@ the following new features:

OS X Specific
    -
  • Due to a limitation in the Quicktime graphics engine, there is a limit on the number points allowed per feature. See the Readme that comes with the OS X dmg +
  • Due to a limitation in the Quicktime graphics engine, there is a + limit on the number points allowed per feature. See the Readme that comes + with the OS X dmg
@@ -670,10 +672,13 @@ the following new features:
If think you have found a bug, please consider reporting it to the development team. The steps to report a bug are:
    -
  1. Go to the Bug Tracker at https://svn.qgis.org/trac -
  2. Read Using Trac With QGIS to learn about the submission process -
  3. Review the list of current issues to make sure your bug has not already been submitted. If it has, review the submission and see if there is anything you can add to the bug report to aid the developers -
  4. If your bug has not been reported, create a new ticket, making sure to either login to trac or provide your email address. Tickets lacking contact information are subject to deletion. +
  5. Ensure you have an OSGEO login (available to anyone by filling out the form on this page: http://www.osgeo.org/osgeo_userid +
  6. Go to the Bug Tracker at http://hub.qgis.org/projects/quantum-gis +
  7. Review the list of current issues to make sure your bug has not + already been submitted. If it has, review the submission and see if + there is anything you can add to the bug report to aid the developers +
  8. If your bug has not been reported, create a new ticket. Tickets + lacking contact information are subject to deletion.