Menu

Release Procedure

Paul Walker
  • Look at the Bugs and Feature Requests tagged as for the next release and decide next version number

  • Set new version number in the following:

    • utplsql\source\ut_plsql.pkb (variable name: g_version)
  • Update release notes and version number:

    • utplsql\documentation\src\release.html
  • Check the copyright years in:

    • utplsql\documentation\readme.txt
    • utplsql\documentation\src\copyright_years.txt
  • Tag the release in SVN

  • In the Bugs Tracker Admin:

    • 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]
    • 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 Requests Tracker Admin:

    • 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:

    • Modify the “Version” field to insert the new version number immediately after the asterisk at the start of the string
    • Hit Save
  • Run utplsql\documentation\src\build_docs.pl

  • 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 and from the Info box, select the checkboxes to make it the default download for all OS’s


Related

Feature Request Archive (Use GitHub now): #8

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.