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
The News page hasn't been update since November, currently it's a manual process so we need a way to remember to update it. I think we should include this as part of First Responder duties since we're aiming to reduce the amount of project work FR does, and increase time for FR + maintenance tasks.
Proposed process:
FR opens News pr every Monday for team to comment re new events and releases.
Slack bot reminder on Thursday to help team remember to post updates to pr
FR checks again with team on Friday re any changes and updates but doesn't ship (because of timezone differences people may ship releases after someones end of work day so makes more sense to ship on Monday)
Next FR reviews and ships News PR and opens a new one for the week. The cycle continues.
This is very manual, if we can automate all or parts of this please make suggestions!
cc @primer/ds-core
The text was updated successfully, but these errors were encountered:
One way that we could ensure this is kept up to date is to actually use the GitHub releases API to get the latest release of one or more repos server-side:
The News page hasn't been update since November, currently it's a manual process so we need a way to remember to update it. I think we should include this as part of First Responder duties since we're aiming to reduce the amount of project work FR does, and increase time for FR + maintenance tasks.
Proposed process:
News
pr every Monday for team to comment re new events and releases.News
PR and opens a new one for the week. The cycle continues.This is very manual, if we can automate all or parts of this please make suggestions!
cc @primer/ds-core
The text was updated successfully, but these errors were encountered: