Skip to content
This repository has been archived by the owner on Oct 10, 2023. It is now read-only.

Define a release process #151

Closed
Tracked by #166
thepetk opened this issue Mar 22, 2023 · 0 comments · Fixed by #158
Closed
Tracked by #166

Define a release process #151

thepetk opened this issue Mar 22, 2023 · 0 comments · Fixed by #158
Assignees
@thepetk
Labels
area/documentation All issues related to documentation updates, corrections or bugs

Comments

@thepetk
Copy link
Collaborator

thepetk commented Mar 22, 2023 •
edited
Loading

Which area this feature is related to?

/area documentation

Issue details

As a serviceability enhancement we should define a new release process for the Alizer component.
A good example to follow for this issue would be the Devfile Release Process

Target date: 3 Apr 2023
@openshift-ci openshift-ci bot added the area/documentation All issues related to documentation updates, corrections or bugs label Mar 22, 2023
@thepetk thepetk self-assigned this Mar 22, 2023
@thepetk thepetk moved this to Under Consideration in Sprint 234 Mar 22, 2023
@thepetk thepetk moved this from Backlog to Todo in Sprint 234 Mar 24, 2023
@thepetk thepetk moved this from Todo to In Progress in Sprint 234 Mar 27, 2023
@thepetk thepetk mentioned this issue Mar 29, 2023
Merged
@thepetk thepetk moved this from In Progress to Review in Progress in Sprint 234 Mar 29, 2023
@thepetk thepetk moved this from Review in Progress to Done in Sprint 234 Mar 31, 2023
@jasperchui jasperchui mentioned this issue Mar 31, 2023
Closed
14 tasks
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@thepetk thepetk

Labels
area/documentation All issues related to documentation updates, corrections or bugs
Projects
No open projects
Sprint 234
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Define a Release process thepetk/alizer
1 participant
@thepetk