2024_mar_epic #story_l: Archive MTL 3.0 releases and associated information

[ljmoody]

Reference: sim_ui_workflow meeting on January 10, 2024 *Need all the archives, TEST environments, and manuals/documentation discussed.

Definition of Done:

• [x] Archive SEE guides.
• [x] Archive SAY guides.
• [x] Include an underscore between mtl and the version number:
  • [x] mtl_1.7, mtl_2.0, mtl_3.0, mtl_3.7
• [x] Inventory and ensure there is an archive of each release:
  • [ ] mtl_1.0
  • [ ] mtl_1.7
  • [ ] mtl_2.0
  • [ ] mtl_3.0

  • [ ] mtl_3.7

    DECISIONS - Archives we need for each release: (from sim_ui mtg 1/10/24)

• [x] Archive all release version files at https://mtl.how
  • [x] ADD: release_3.0
• [x] Within the blue branch of https://mtl.how
  • [ ] ADD: mtl_3.7_models
• [x] Archive full guide branches for each release mtl_1.7 mtl_2.0, mtl_3.0, mtl_3.7 that were hosted at https://mtl.how
  • [x] e.g., release_1.7
• [x] Archive each MTL Manual https://mtl.how/manual
• [x] Archive each set of MTL Videos.
• [ ] Archive each set of Power BI Data UI files for each release.

Done: gh-pages_mtl_2.0_archive (archive of our MTL 2.0 manual)

Now: gh-pages_mtl_3.7_test (our MTL 3.7 TEST manual)

gh-pages_mtl_3.0_archive (archive of our MTL 3.0 manual)

gh-pages_mtl_3.7_test_archive (archive of our MTL 3.7 TEST manual)

February 2024: gh-pages_mtl_3.7 (our MTL 3.7 PROD manual)

gh-pages_mtl_3.7_archive (archive of our MTL 3.7 PROD manual)

Do not worry about walking back work to archive an MTL 3.0 version of the manual. Likely provisional conclusion - we will be only work in PROD with these 12 NIH sites wrapping up in Jan/Feb. Documentation:

• [x] Self-registration
• [x] MTL Reports And yes, we need all the archives, TEST environments and manuals/documentation we discussed.