You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once we know what comms are approved, create commits and merge in those changes
Deploy comms changes to Dev via CLI, and ask BAs to approve
Wait till we're absolutely ready to release, test while waiting
I believe we won't need to enter maintenance mode for deployment, but confirm
Add 2024 to mlarReleaseYear and dataPublicationYears.mlar to prod-config.json (and possibly the other configs as well for completeness) then merge to github
Create a github release
Wait till the late afternoon on off-peak hours (confirm with BAs)
Deploy mLAR changes to Prod via CLI (based on how I understand things currently are working with the caching workaround, these changes won't be visible until a manual deploy is done) - use the same image that's on dev
Deploy updated 2024 mLAR e2e tests to prod
Test things out with the team, confirm e2e tests pass (wait till they run automatically or trigger manually)
🥳
Open questions:
What types of comms will be included with the release of the 2024 mLAR data?
Announcement banner (from last mLAR release):
We're preparing to publish the 2024 modified LAR data next month. Here are the frontend tasks as I see them at the moment:
TODOs:
2024
tomlarReleaseYear
anddataPublicationYears.mlar
todev-config.json
and merge to github2024
tomlarReleaseYear
anddataPublicationYears.mlar
toprod-config.json
(and possibly the other configs as well for completeness) then merge to githubOpen questions:
Announcement banner (from last mLAR release):
Changelog update (from last mLAR release):
Press release (link to last mLAR press release):
Notes:
In the config...
dataPublicationYears.mlar
- allows this page to display2024
mLAR data by institution and combined mLAR datamlarReleaseYear
- makes the link from the home page direct to2024
mLAR dataThe text was updated successfully, but these errors were encountered: