Recent changes to Release Procedure

Release Procedure modified by Paul Walker

Paul Walker — Sun, 08 Feb 2015 23:08:57 -0000

--- v6
+++ v7
@@ -6,7 +6,9 @@
 * Update release notes and version number:
     * `utplsql\documentation\src\release.html`

-* Check the copyright years in `utplsql\documentation\readme.txt`
+* Check the copyright years in:
+    * `utplsql\documentation\readme.txt`
+    * `utplsql\documentation\src\copyright_years.txt`

 * Tag the release in SVN

Release Procedure modified by Paul Walker

Paul Walker — Sat, 30 Aug 2014 20:59:13 -0000

--- v5
+++ v6
@@ -1,8 +1,7 @@
 * Look at the [Bugs](https://sourceforge.net/p/utplsql/bugs/fixed_in_version/[next]/) and [Feature Requests](https://sourceforge.net/p/utplsql/feature-requests/fixed_in_version/[next]/) tagged as for the next release and decide next version number
-    * **Old version: 2.2.1 New version: 2.2.2**

 * Set new version number in the following:
-    * `utplsql\source\ut_plsql.pkb`
+    * `utplsql\source\ut_plsql.pkb` (variable name: `g_version`)

 * Update release notes and version number:
     * `utplsql\documentation\src\release.html`

Release Procedure modified by Paul Walker

Paul Walker — Sun, 04 May 2014 11:46:38 -0000

--- v4
+++ v5
@@ -1,5 +1,5 @@
 * Look at the [Bugs](https://sourceforge.net/p/utplsql/bugs/fixed_in_version/[next]/) and [Feature Requests](https://sourceforge.net/p/utplsql/feature-requests/fixed_in_version/[next]/) tagged as for the next release and decide next version number
-    * **Old version: \_\_\_\_\_\_\_\_ New version: \_\_\_\_\_\_\_\_**
+    * **Old version: 2.2.1 New version: 2.2.2**

 * Set new version number in the following:
     * `utplsql\source\ut_plsql.pkb`
@@ -11,28 +11,28 @@

 * Tag the release in SVN

-* In the Bugs Tracker Admin ([https://sourceforge.net/p/utplsql/admin/bugs/fields]): 
-    * Change the `[next]` milestone to the new version number
+* In the [Bugs Tracker Admin](https://sourceforge.net/p/utplsql/admin/bugs/fields): 
+    * Rename the `[next]` milestone to the new version number
     * Set the due date to today(format is mm/dd/yyyy)
     * Tick the Complete box
-    * Add a new milestone called `[next] just below `[none]
+    * Add a new milestone called `[next]` just below `[none]`
     * Hit `Save`
     * Modify the “Seen in version” field to insert the new version number immediately after the asterisk at the start of the string
     * Hit `Save`

-* In the Feature Tracker Admin ([https://sourceforge.net/p/utplsql/admin/feature-requests/fields]):
+* In the [Feature Requests Tracker Admin](https://sourceforge.net/p/utplsql/admin/feature-requests/fields):
     * Change the `[next]` milestone to the new version number
     * Set the due date to today(format is mm/dd/yyyy)
     * Tick the Complete box
     * Add a new milestone called `[next]` just below `[none]`
     * Hit `Save`

-* In the Support Tracker Admin ([https://sourceforge.net/p/utplsql/admin/support-tickets/fields]):
+* In the [Support Tracker Admin](https://sourceforge.net/p/utplsql/admin/support-tickets/fields):
     * Modify the “Version” field to insert the new version number immediately after the asterisk at the start of the string
     * Hit `Save`

-* Build docs
+* Run `utplsql\documentation\src\build_docs.pl`

-* Run `build.pl` and choose option 2 to create and upload the release
+* Run `utplsql\build\build.pl` and choose option 2 to create and upload the release

-* Find the new zip file on the the Files page ([https://sourceforge.net/projects/utplsql/files]) and from the Info box, select the checkboxes to make it the default download for all OS’s
+* Find the new zip file on the the [Files page](https://sourceforge.net/projects/utplsql/files) and from the Info box, select the checkboxes to make it the default download for all OS’s

Release Procedure modified by Paul Walker

Paul Walker — Sat, 03 May 2014 22:14:59 -0000

--- v3
+++ v4
@@ -1,4 +1,4 @@
-* Look at the [Bugs](https://sourceforge.net/p/utplsql/bugs/fixed_in_version/[next]/) and [Feature Requests](https://sourceforge.net/p/utplsql/feature-requests/fixed_in_version/[next]/]) tagged as for the next release and decide next version number
+* Look at the [Bugs](https://sourceforge.net/p/utplsql/bugs/fixed_in_version/[next]/) and [Feature Requests](https://sourceforge.net/p/utplsql/feature-requests/fixed_in_version/[next]/) tagged as for the next release and decide next version number
     * **Old version: \_\_\_\_\_\_\_\_ New version: \_\_\_\_\_\_\_\_**

 * Set new version number in the following:

Release Procedure modified by Paul Walker

Paul Walker — Sat, 03 May 2014 22:14:24 -0000

--- v2
+++ v3
@@ -1,4 +1,4 @@
-* Look at Bugs and Feature requests tagged as for the next release ([https://sourceforge.net/p/utplsql/bugs/fixed_in_version/%5Bnext%5D/]) and ([https://sourceforge.net/p/utplsql/feature-requests/fixed_in_version/%5Bnext%5D/]) and decide next version number
+* Look at the [Bugs](https://sourceforge.net/p/utplsql/bugs/fixed_in_version/[next]/) and [Feature Requests](https://sourceforge.net/p/utplsql/feature-requests/fixed_in_version/[next]/]) tagged as for the next release and decide next version number
     * **Old version: \_\_\_\_\_\_\_\_ New version: \_\_\_\_\_\_\_\_**

 * Set new version number in the following:

Release Procedure modified by Paul Walker

Paul Walker — Sat, 03 May 2014 22:08:29 -0000

--- v1
+++ v2
@@ -33,23 +33,6 @@

 * Build docs

-* In a new directory, create folders: `Code`, `Doc` and `Examples`
-    * In the `Code` directory, copy in all files from `utplsql\source`
-    * In the `Examples` directory, copy in all files from `utplsql\examples`
-    * In the `Doc` directory, copy in all files from `utplsql\documentation` (not the `\source` directory though).
-    * From the new `Doc` directory move `readme.txt` to the top level
+* Run `build.pl` and choose option 2 to create and upload the release

-* Zip up this directory called `utplsql-version.zip`, eg `utplsql-2-2-1.zip`
-
-* Release web:
-    * Using FileZilla, go to:
-        * Host: `web.sourceforge.net`
-        * Protocol: `SFTP – SSH File Transfer Protocol`
-        * Directory: `/home/project-web/utplsql/htdocs`
-    * Upload files from `\utplsql\website`
-
-* Release files
-    * Go to [https://sourceforge.net/projects/utplsql/files/utPLSQL/]
-    * Add a new folder for the new version number
-    * Go into the new folder and upload the release zip
-    * Select all the checkboxes to make it the default download for all OS’s
+* Find the new zip file on the the Files page ([https://sourceforge.net/projects/utplsql/files]) and from the Info box, select the checkboxes to make it the default download for all OS’s

Release Procedure modified by Paul Walker

Paul Walker — Sun, 06 Apr 2014 10:18:44 -0000

Look at Bugs and Feature requests tagged as for the next release ([https://sourceforge.net/p/utplsql/bugs/fixed_in_version/%5Bnext%5D/]) and ([https://sourceforge.net/p/utplsql/feature-requests/fixed_in_version/%5Bnext%5D/]) and decide next version number
- Old version: ________ New version: ________
Set new version number in the following:
- utplsql\source\ut_plsql.pkb
Update release notes and version number:
- utplsql\documentation\src\release.html
Check the copyright years in utplsql\documentation\readme.txt
Tag the release in SVN
In the Bugs Tracker Admin ([https://sourceforge.net/p/utplsql/admin/bugs/fields]):
- Change the [next] milestone to the new version number
- Set the due date to today(format is mm/dd/yyyy)
- Tick the Complete box
- Add a new milestone called [next] just below[none]
- Hit Save
- Modify the “Seen in version” field to insert the new version number immediately after the asterisk at the start of the string
- Hit Save
In the Feature Tracker Admin ([https://sourceforge.net/p/utplsql/admin/feature-requests/fields]):
- Change the [next] milestone to the new version number
- Set the due date to today(format is mm/dd/yyyy)
- Tick the Complete box
- Add a new milestone called [next] just below [none]
- Hit Save
In the Support Tracker Admin ([https://sourceforge.net/p/utplsql/admin/support-tickets/fields]):
- Modify the “Version” field to insert the new version number immediately after the asterisk at the start of the string
- Hit Save
Build docs
In a new directory, create folders: Code, Doc and Examples
- In the Code directory, copy in all files from utplsql\source
- In the Examples directory, copy in all files from utplsql\examples
- In the Doc directory, copy in all files from utplsql\documentation (not the \source directory though).
- From the new Doc directory move readme.txt to the top level
Zip up this directory called utplsql-version.zip, eg utplsql-2-2-1.zip
Release web:
- Using FileZilla, go to:
  - Host: web.sourceforge.net
  - Protocol: SFTP – SSH File Transfer Protocol
  - Directory: /home/project-web/utplsql/htdocs
- Upload files from \utplsql\website
Release files
- Go to [https://sourceforge.net/projects/utplsql/files/utPLSQL/]
- Add a new folder for the new version number
- Go into the new folder and upload the release zip
- Select all the checkboxes to make it the default download for all OS’s