Cookies help us deliver our services. By using our services, you agree to our use of cookies.
Views

Difference between revisions of "Software Release Procedure"

From IHRIS Wiki

Jump to: navigation, search
Line 17: Line 17:
 
== Bug Reports (responsibility of Carl/Luke)==
 
== Bug Reports (responsibility of Carl/Luke)==
  
Review all bugs reported in [https://bugs.launchpad.net/ihris-suite Launchpad.] Mark bugs that have been fixed or are in progress. List fixed bugs in [[Development Timeline]] on wiki.
+
Review all bugs reported in [https://bugs.launchpad.net/ihris-suite Launchpad.] Mark bugs that have been fixed or are in progress. List fixed bugs in Development Timeline on wiki.
 
 
  
 
== Use Cases ==
 
== Use Cases ==

Revision as of 12:23, 15 September 2011

Below is the ideal iHRIS release procedure. It includes updating User's Manuals (we have not done this in several releases, but should every release) and updating Use Cases (we have not updated these in years, but they need to be updated). It also includes all pages and links that must be updated, as well as announcements that need to be posted whenever a new version of any of the iHRIS software products is released.

NOTE: All electronic Toolkit updates will also need to include an additional update to the Toolkit ZIP file, which is used for burning on software and flash drives. The latest ZIP is always located here: http://www.capacityproject.org/hris/hris-toolkit/hris-toolkit.zip NEED TO UPDATE ZIP FILE!


User's Manuals (Help)

During testing, update the Help File Originals with any procedures that have changed and new features. Update screenshots of changed screens as well. NOTE:

Create a book for each user's manual on the wiki. The iHRIS Manage User's Manual and iHRIS Qualify User's Manual has already been created, but will need to be updated if any pages are removed or added. NOTE: A book for iHRIS Plan will need to be generated.

Generate a new HTML version of the user's manual to include with the software (Luke). Generate a PDF to include in the electronic Toolkit. Upload the PDFs to this location: http://www.capacityproject.org/hris/hris-toolkit/tools/pdf/. See the Software Documentation page for individual filenames (all website links point here). Also add copies to the electronic Toolkit ZIP file.

NOTE: If there have been any changes to the Data Dictionary, you will also need to generate that file as a PDF and upload to the electronic Toolkit in the same locations as the user's manuals.

Bug Reports (responsibility of Carl/Luke)

Review all bugs reported in Launchpad. Mark bugs that have been fixed or are in progress. List fixed bugs in Development Timeline on wiki.

Use Cases

Update all use cases with changes, resolved issues or new issues. Write new use cases or requirements, if needed to document new features. The original use case files are located on SharePoint in the iHRIS Software Suite Document Library. You will need CaseComplete to update the files.

NOTE: There are 4 use case files: one for each of the software programs, and one for use cases that are common to all of the programs in the suite. If you open multiple use case files in CaseComplete, you can print them to the same report.

If there have been changes, generate a new HTML report for each software program: Manage, Qualify and Plan. Be sure to include the shared (Common) use cases in each of these reports. Upload these to the website at this location: http://www.capacityproject.org/hris/suite/. See each software page for individual filenames.

Also generate a new Word report separately for each software program: Common, Manage, Qualify and Plan. I generally edit the Word reports to remove use cases that have not yet been implemented and open issues, so as to prevent confusion. Upload the DOCs to this location: http://www.capacityproject.org/hris/hris-toolkit/tools/doc/. See the Software Documentation page for individual filenames. Also add copies to the electronic Toolkit ZIP file.


Release Notes

Update the README files with the latest version number, release date, new features/bug fixes in the release and known issues with the release.

Save each new release file as a README file in TXT format. Upload the README file to the download pages on Launchpad for each release.

Responsibility of Brooke

Features Lists and Roadmaps

For each software release, update the features lists and roadmaps on the website. The features list should be updated with the latest version number, all features available in the latest version, all planned features scheduled for development and all requested features not yet scheduled. The roadmaps should be updated with the date and location of the latest release and the timeline for planned releases.

The Development Team should also update the Development Timelines on the wiki.


Download Links

Once the software is posted to Launchpad, update the download links and version numbers on the Software Downloads page on the website. Luke will provide the links.

If there is a new Windows version, it will need to be added to the electronic Toolkit. Upload the EXE file here: http://www.capacityproject.org/hris/hris-toolkit/tools/exe/ and add it to the Toolkit ZIP. Be sure to change the link on the Toolkit iHRIS Software Suite page to reflect the change in version number.


Announcements

An announcement of the new release version including the location of the download and demo, and a summary of any new features should be posted in all of the following places:

Be sure to link to the release notes in the announcement.