Upgrading Source code

As of OpenG 3.0, libraries will only be available for LabVIEW 8.2 (release date August 2006). The source code for all libraries should be upgraded from LabVIEW 6.1 to 8.2, the following document describes the steps for this action. This should be done prior to any edits that will lead to a new release.


 * 1) Create a task on Sourceforge (Upgrading XXXX to LabVIEW 8.2) Let the task start in one week and finish in 2 weeks, this gives other developers the opportunity to check in any changes Assign the task to yourself
 * 2) Wait one week
 * 3) Make sure you have the latest revision of the source code
 * 4) Create a LabVIEW Project file located at the library root folder named: OpenG Library {library name} Toolkit
 * 5) Make an export of the library (eg. removing all .svn folders)
 * 6) Add the whole library folder to the LabVIEW project
 * 7) Make an SVN update to get all the .svn folder back.
 * 8) Open up a VI-Tree VI in the source folder
 * 9) Save (and save all sub-VIs) the VI-Tree
 * 10) Go through the directory of the source folder and make sure everything has been updated. If any unchanged files are found recompile them manually, make a note in the Docs folder
 * 11) Make an SVN commit with the note 'Updated Source code to LabVIEW 8.2'
 * 12) Recompile any LabVIEW file inside the LabVIEW project not included with the source folder (tests, candidates and others)
 * 13) Make an SVN commit with the note 'Updated Helper files to LabVIEW 8.2'
 * 14) Add the LabVIEW project file to SVN, ignore the aliases file in SVN.
 * 15) Make an SVN commit with the note 'Added LabVIEW project file'
 * 16) Run any unit tests VIs found
 * 17) Update the status of the task in Sourceforge to 'closed'