Bootstrap 4 end of life is the start of 2023; future Arizona Bootstrap development should use Bootstrap 5

[mmunro-ltrr]

What is the problem that we want to solve?

Arizona Bootstrap is a collection of overrides and small extensions to Twitter Bootstrap, and includes a complete copy of this upstream version as one of its dependencies. In the last two years, the developers of Twitter Bootstrap have had Version 5 as their primary focus, and have been maintaining but not enhancing Version 4, but Arizona Bootstrap is currently based on v4. Twitter Bootstrap will drop support for v4 at the start of 2023: https://github.com/twbs/release

Conditions of satisfaction

• Switch development of Arizona Bootstrap to use Twitter Bootstrap v5.
• Offer a long-term support option for the version of Arizona Bootstrap based on v4, despite its end-of-life status.
• Investigate whether there can be a common sub-set of the two versions giving identical appearance & behavior on web sites using them.

[trackleft]

Notes:
Arizona bootstrap version 2 will be available via CDN URL indefinitely
Arizona bootstrap version 2 docs should have dedicated URL indefinitely
Arizona bootstrap version 5 should contain a shim file for version 2 styles so sites can upgrade quickly
Arizona bootstrap version 5 should use the new https://github.com/az-digital/arizona-bootstrap/blob/main/RELEASES.md policy

[trackleft]

Update build tools to sync docs to version 5 folder
Change version number of arizona bootstrap to version 5
Determine what our new CDN folder structure will be. Examples

https://cdn.digital.arizona.edu/lib/arizona-bootstrap/main/js/arizona-bootstrap.js
https://cdn.digital.arizona.edu/lib/arizona-bootstrap/latest/js/arizona-bootstrap.js
https://cdn.digital.arizona.edu/lib/arizona-bootstrap/v2.1.0/js/arizona-bootstrap.js

[trackleft]

1. Create 2.x branch and treat main as 5.x
2. Allow simultaneously maintaining releases for 5.x and 2.x versions of Arizona Bootstrap docs via CI infrastructure. digital.arizona.edu#40
3. Add 2.x as a target branch for dependabot #636
4. Update navigation on Arizona Bootstrap docs to account for version 5 #610
5. Create a release
6. Update cdn-deploy-main.yml to be triggered on both main and 2.x #605
7. Ensure that latest CDN folder is only updated by 2.x branch #606
8. Modify release.yml on 2.x branch so that it checks out the 2.x branch, and passes the branch name to the repository dispatch action. #643
9. Bring Arizona Bootstrap version 2 up to speed with upstream
   • Update Arizona Bootstrap with upstream changes #607
10. In parallel with Step 1 alter build tools to push docs into versioned buckets
    • Update workflow to push docs to version buckets instead of syncing 2.0 folder digital.arizona.edu#38
11. Audit Arizona Bootstrap version 2 to determine what we would like to support
    • Audit differences between Bootstrap 4 and Bootstrap 5 #608
12. Create a release candidate for Arizona Bootstrap 5
13. Update packagist meta package Update composer version alias for arizona bootstrap from 2.x-dev to 5.x-dev arizona-bootstrap-packagist#19
14. Allow switching between versions of arizona-bootstrap version 2.x now that we are changing the path for those assets. az_quickstart#2120

[joeparsons]

Resources shared by @mmunro-ltrr in our 2023-08-09 workshop:

• https://drafts.csswg.org/css-variables/
• https://getbootstrap.com/docs/5.3/migration/
• https://getbootstrap.com/docs/5.2/migration/