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
Open meeting of September 30 - set up by September 29
On September 30:
reset NOA banner to return at 9/30 (after meeting expires) and expire 10/1 at 5:30 pm
EFiling has requested a maintenance banner this weekend for patching - we need to set it to come up 5:30 on 10/1 and come down at 10 am 10/2 (Maintenance will still happen even if there is a shutdown)
- [ ] On October 1: If needed: shutdown banner (this may need to be coordinated with @patphongs since no one on content is on essential list)
On October 2 (assuming no shutdown):Reset NOA banner to return at 10 am 10/2 and expire at 11:59pm on 10/4
On October 5 as early as possible (assuming no shutdown): Revert pending rulemakings page to read "There are no current rulemaking matters pending for comment."
If needed: any change in status doc that may happen
Double-check for any other banners that might be needed
Create banner ticket for 16.2 before refinement and add it to the content doc for PI16
The text was updated successfully, but these errors were encountered:
Confirming that the rulemaking banner is down since the comment period expired, and that the pending rulemaking page has been updated to say "There are no current rulemaking matters pending for comment."
No other banners at the moment. Will move this ticket back to Assigned and move it again if any more banner work is required this sprint.
Summary
What we are after:
Content team is going to have routine sprint ticket for banner work each sprint to make sure we're on top of it.
Related
Banner spreadsheet
Banner How to
Completion criteria
Banners set up for:
On September 30:
- [ ] On October 1: If needed: shutdown banner (this may need to be coordinated with @patphongs since no one on content is on essential list)The text was updated successfully, but these errors were encountered: