2020 Q1 Fameflower PO Bugfix and Hotfix Release Process:

Owned by Anton Emelianov (Deactivated)
Last updated: Jun 21, 2021 by Ann-Marie Breaux (Deactivated)

Bugfix = a fix release that happens after the module release deadline, but before the actual release

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

This describes the Q1-2020/Fameflower 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 April 2020, we are releasing hotfixes for Q1-2020 (Fameflower) and Q4-2019 (Edelweiss)
  2. According to the soon-to-be-approved release process we won't create maintenance releases (i.e. hotfix) for anything but a P1.
  3. For Q1-2020 hotfixes, add the Jira label q1-2020-hotfix 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. 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.  
  6. If approved (can be considered approved if you get the thumbs up from at least two technical approvers (Mike, Mark or Jakub), ask the module maintainer to create a hotfix release. You can get the module maintainer’s name from the most recent release spreadsheet that lists all the MOD and UI modules. The release needs to go to the appropriate Release branch and the Main branch, and populate the community Flower release. UI releases show up automatically in the flower release. MODs don’t. They have to be manually pushed
  7. When the release is made, the module maintainer will announce it on the Slack #releases channel. 
  8. When release is announced, ask an EBSCO PO (Harry Kaplanian, Ann-Marie Breaux, Cate Boerema, Dennis Bridges, Khalilah Gambrell, Magda Zacharska, Patty Wanninger, Stephanie Buck) or Anton Emelianov to make a request for it to be deployed to BugFest.
  9. PO tests the hotfix on the BugFest environment
  10. Add information about the hotfix to the Q1/Fameflower Release Notes page on the wiki, in the Post-release Hotfixes table: Q1 2020 (Fameflower) 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 Q1-2020/Fameflower Bugfix release process (fixes being released after the initial release, but before the final Fameflower deadline). This will be adjusted for future quarterly releases

  1. Bugfix = fix that happens after the module release deadline, but before the actual release. Fameflower release schedule
  2. Label Jira issue with q1-2020-bugfix and let the developers doing the fix know that it is needed ASAP for a bugfix
  3. 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 be tested on the Bug Fest environment)
  4. Once the fix has passed testing in snapshot, post the Jira and seek approval for a bugfix release on the Slack #release_bug_triage channel. Approvers are Cate Boerema, Jakub Skoczen, Holly Mistlebauer, Mark Veksler, Mike Gorrell, Harry Kaplanian.  This time  around the #release_bug_triage group decided not to try to approve every release.  We are leaving it to the discretion of the tech leads. 
  5. If approved, ask the module maintainer to create a bugfix release. You can get the module maintainer’s name from the most recent release spreadsheet that lists all the MOD and UI modules. The release needs to go to the appropriate Release branch and the Main branch.  Note: some module maintainers will be monitoring this filter to see what is ready to release:  Getting issues...
  6. When the release is made, the module maintainer will announce it on the Slack #releases channel. 
  7. When release is announced, ask an EBSCO PO (Harry Kaplanian, Ann-Marie Breaux, Cate Boerema, Dennis Bridges, Khalilah Gambrell, Magda Zacharska, Patty Wanninger, Stephanie Buck) or Anton Emelianov to make a request for it to be deployed to BugFest.  Bugfix releases will automatically be picked up and applied to the Bug Fest environment (nightly).  No need to request that the fix be applied.
  8. PO tests the bugfix on the BugFest environment,