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
As a developer on a support team I'd like to be aware of the release plans for dodal, as the centerpiece of the bluesky beamline state representation, and a base for running and testing plans.
Agile recommends a regular release set and if automated would be 0 effort.
It does not seem that we would frequently run into a problem of a new release not having 0 new commits in main.
Possible implementations
Continuous Deployment could have a cron job that every week on day (?) makes a new semver tag if the CI passes on main.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
As a developer on a support team I'd like to be aware of the release plans for dodal, as the centerpiece of the bluesky beamline state representation, and a base for running and testing plans.
Agile recommends a regular release set and if automated would be 0 effort.
It does not seem that we would frequently run into a problem of a new release not having 0 new commits in main.

Possible implementations
Continuous Deployment could have a cron job that every week on day (?) makes a new semver tag if the CI passes on
main
.Beta Was this translation helpful? Give feedback.
All reactions