Release types and activities

Release types are used to reflect on the level of completion for a component.

Alpha release

In an alpha release the component/site may not contain all the planned features and likely contains known and unknown defects.

With the exception of release notes, there are no formal expectations to review work product in an alpha release.

This type of release can be used to validate the merge request process and ensure core functionality is not compromised once work has been deployed to the eServices Platform environment.

Beta release

Beta releases follow alpha releases. In this release the component is feature complete but likely to contain some known or unknown defects.

In an initial beta release a more formal review of your work product is expected.

Development partners are expected to:

  • Provide release notes.
  • Participate in a joint code review session. During code review the development partner can walk through custom features to discuss approach and highlight any technical issues. Code reviews are estimated to be 30 minutes.
  • Demonstrate relevant testing practices and or steps taken to provide assurances for code quality and/or test coverage, this may include reporting of:
    • Unit tests.
    • Functional tests.
    • Compliance with WCAG 2.0 (AA) guidelines.
    • Compliance with Government of Yukon security and privacy guidelines.
    • Demonstrated compatibility across the following approved desktop browsers and devices:
      • Desktop browsers for: Chrome, Firefox, Safari and IE 8+.
      • Devices running the latest versions of Apple iOS and Android.
      • Visual inspections of the site in popular mobile viewport sizes.
  • Confirm that any custom components can be translated within Drupal.
  • Setup and configuration of external services are also provided by the development partner (e.g.. Beanstream).

Release candidate (RC)

A development release candidate follows a development beta release. A release candidate is code complete when the development partner agrees no new source code will be added to this release.

For a release candidate, development partners are to:

  • Provide release notes.
  • Demonstrate issues during beta testing have been resolved.
  • Approval from you project sponsor to promote release candidate to the UAT environment.

 

Next: Release notes →

Last update:
May 23, 2017