Sunflower (R1 2025) PO Bugfix Release Process:

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

NOTE: We are in the Sunflower R1 2025 Bugfix period, which precedes the CSP period. Bugfix instructions are here

(Prior Bugfix procedures are saved with the appropriate release.)

This describes the Sunflower R1 2025 Bugfix release process (fixes being released after the initial release, but before the final Sunflower deadline). This may be adjusted for future releases

1. Bugfix = fix that happens after the module release deadline, but before the actual release. Please refer to the Sunflower Release Schedule Most of these issues will be identified during Sunflower R1 2025 BugFest Prep

2. Update several fields in the Jira bug issue

   1. Make sure the priority is aligned with the definitions here: Defect Priority Definition for Functional Issues

   2. Release field = Sunflower R1 2025 Bug Fix

   3. Assign label bugfest_r1.2025 if the bug is found by a community tester during BugFest. This allows us to keep statistics on the bugs produced during that process. 

   4. Fill in the RCA (root cause analysis) field of the Jira, or else be sure that the Developer fills it in. 

   5. Link the Jira issue to the appropriate TestRail case(s). If there is no TestRail, create one, and then link to the bug.

3. Let the developers doing the fix know that it is needed ASAP for a bugfix, definitely before the Sunflower official release. Do not confuse with the Fix version field, which should reflect the release version the fix will be included in.

4. Get the issue fixed and test on https://folio-etesting-snapshot-diku.ci.folio.org/ (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)

5. No permission is required for bugfixes before the release deadline. Once the fix has passed testing in snapshot, change the status to Awaiting release and the Resolution to Done, 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. 

6. Create a release ticket for the module and assign FOLREL-760: Sunflower 2025 R1 - Bugfix Release - 18 Apr 2025In Progress . Be sure that each bug in the release has the correct release version assigned to it.

7. When the release has been made, the module maintainer will change the bug issue's status to Awaiting deployment. There is no need for the PO or module maintainer to request that the release be deployed

8. Jenkins robot automatically generate pull request for the "R1 2025" branch of Platform Complete repository in Github for every released module if version incremented by "patch" number. (For example from 1.1.1 to 1.1.2)

9. Manual intervention required if release version requires change of major (1.1.1 to  2.0.0) or minor (1.1.1 to 1.2.0) number. In this case PO or Dev lead  have to notify DevOps and @Oleksii Petrenko about this change.

10. FOLIO hosting team checks for updates of Platform Complete one time per day and updates Sunflower Bug Fest with modules that have been released since yesterday's update.

11. FOLIO hosting team will post notification in #bug-fest Slack channel when update starts and ends. 

12. Once daily update has been deployed to Bug Fest, DevOps will change the bug issue's status to In bugfix review 

13. When an issue is moved to In Bugfix Review, the PO and/or community should do a final round of testing in the Bug Fest environment

14. Finally, when the issue has passed test in the Bug Fest environment, the PO should

    1. add a new test result to the TestRail case, which will hopefully move the test from Blocked or Failed to Passed.

    2. change the Jira Status to Closed

       Open