GSA / data.gov

Main repository for the data.gov service
https://data.gov
Other
666 stars 103 forks source link

Brainstorm Formal/Informal Release Ideas #4243

Open nickumia-reisys opened 1 year ago

nickumia-reisys commented 1 year ago

User Story

In order to solidify the Data.gov Brand, the Data.gov Release Team wants to implement a process to audit work at a specified time interval (monthly or quarterly) to have better insight into what's changing at Data.gov and provide users a way to parse through the changes.

Acceptance Criteria

Background

This came out of the retro on 3/17. The sentiments were about working more on the big picture roadmap to the future and how to plan for 1-2 years out. As part of this thought, the best way to gain traction into the future is knowing where you've been which can be used to highlight possible paths and trajectories (in the absence of an external vision or goal). Right now, after we close issues, we forget about them and only look for them if there's an issue we feel like we've seen before. Often times, we forget 95%+ of the work that's already been done.

The release strategy from this work could be used in multiple folds:

Not all of these points need to be addressed. They are just different aspects we can explore in the scope of this work.

Security Considerations (required)

None.

Sketch

TBD

nickumia-reisys commented 1 year ago

A good place to start: https://sre.google/sre-book/release-engineering/

hkdctol commented 1 year ago

Moving to Icebox for now given competing priorities.