Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Hotfix = a fix release that happens after the final flower release, and heads straight to production

This describes the Q2-2020/Goldenrod Hotfix release process. This will be adjusted for future quarterly releases. See below for prior quarters' Bugfix/Hotfix procedures.

  1. Hotfix release = one that must be added to a release after the final release has been made. As of July 20 2020, we are releasing hotfixes for Q1-2020 (Fameflower) and Q2-2020 (Goldenrod)
  2. According to the soon-to-be-approved release process, we won't create a hotfix release except for P1 functional and P2 security issues.  Once a hotfix release has been scheduled, lower priority issues (e.g. P2 and P3 functional issues) may also be included with permission.
  3. For Q2-2020 hotfixes, set Release field of the bug Jira issues to Q2 2020 Hot Fix and make sure the developers doing the fix know that it is needed for a hotfix
  4. Get the issue fixed and test on https://folio-snapshot.aws.indexdata.com/
  5. As of July 27, 2020, the 54 issues have been approved for the Goldenrod hotfix release(s) (see dashboard).  Any additional issues should be approved:
    1. Once the fix has passed testing in snapshot, post the Jira and seek approval for a hotfix release on the Slack #release_bug_triage channel. Approvers are Cate Boerema, Jakub Skoczen, Holly Mistlebauer, Mark Veksler, Mike Gorrell, Harry Kaplanian.  Please tag the approvers with your request (can be considered approved if you get the thumbs up from at least two technical approvers (Mike, Mark or Jakub))
  6. If approved, ask the module maintainer to create a hotfix release and set the JIRA status to Awaiting Release.
    1. You can get the module maintainer’s name from the Team Module Responsibility Matrix.
    2. The release needs to go to the appropriate Release branch and the Main branch. 
    3. When the release is made, the module maintainer will announce it on the Slack #releases channel. 
  7. When the release is made, the module maintainer will announce it on the Slack #releases channel and change the JIRA status to Awaiting Deployment which will trigger Anton Emelianov to get the release deployed to BugFest (there is no need for the PO or module maintainer to request that the release be deployed).
  8. Once the release has been deployed to Bug Fest, Anton Emelianov will change the bug issue's status to In Bugfix Review which is the PO's trigger to do the final round of testing in the Bug Fest environment
  9. Finally, when the issue has passed test in the Bug Fest environment, the PO should change the status to Closed
  10. Add information about the hotfix to the Q2/Goldenrod Release Notes page on the wiki, in the Post-release Hotfixes table: Q2 2020 (Goldenrod) Release Notes
  11. Once the hotfix has passed testing on BugFest, it needs to be deployed to libraries using the current release in production or in sandbox.
    1. For EBSCO-hosted libraries, ask an EBSCO PO or Anton to deploy the fix.
    2. For Index Data-hosted libraries, Wayne Schneider is managing the deployments. 
    3. Self-hosted libraries will need to decide whether to implement the hotfix or not, based on the announcement on the Slack releases channel or the Fameflower release notes.
  12. If hotfixes are deployed by hosting providers, they should notify the libraries using the current release in production or sandbox that a hotfix has been deployed

This describes the Q2-2020/Goldenrod Bugfix release process (fixes being released after the initial release, but before the final Goldenrod deadline). This will be adjusted for future quarterly releases

  1. Bugfix = fix that happens after the module release deadline, but before the actual release. Goldenrod Release Schedule Most of these issues will be identified during BugFest Q2 2020 Goldenrod BugFest
  2. Set Release field of the bug Jira issues to Q2 2020 and let the developers doing the fix know that it is needed ASAP for a bugfix, definitely before the Goldenrod 17 July 2020 release. Do not confuse with the Fix version field, which should reflect the release version the fix will be included in.
  3. Label the bug Jira issues with bugfest_q2.2020 if the bug is found by a community tester during BugFest (this allows us to keep statistics on the bugs produced during that process. Don't forget to link Jira issue to TestRail test case.
  4. Use label regression when applicable
  5. Get the issue fixed and test on https://folio-snapshot.aws.indexdata.com/ (if possible - some performance issues that don't repro on snapshot will have to skip snapshot testing and be tested on the Bug Fest environment, instead)
  6. No permission is required for bugfixes before the release deadline. Once the fix has passed testing in snapshot, change the status to the new "Awaiting bugfix release" and ask the module maintainer to create a bugfix release.
    1. You can get the module maintainer’s name from the Team Module Responsibility Matrix.
    2. The release needs to go to the appropriate Release branch and the Main branch. 
    3. When the release is made, the module maintainer will announce it on the Slack #releases channel. 
  7. Create a release ticket for the module and assign Epic 
    Jira
    serverFOLIO Issue Tracker
    serverId6ccf3fe4-3301-368a-983e-20c466b11a49
    keyFOLREL-350
    . Be sure that each bug in the release has the correct release version assigned to it.
  8. When the release has been created
    1. Change the status of the release ticket to Closed
    2. The module maintainer will change the bug issue's status to "Awaiting bugfix deployment" which will trigger Anton Emelianov to get the release deployed to BugFest (there is no need for the PO or module maintainer to request that the release be deployed).
  9. Once the release has been deployed to Bug Fest, Anton Emelianov will change the bug issue's status to "In bugfix review" which is the PO's trigger to do the final round of testing in the Bug Fest environment
  10. Finally, when the issue has passed test in the Bug Fest environment, the PO should change the status to "Closed"

...