Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add option to automatically create new release #1062

Open
1 task
KPostOffice opened this issue Jun 10, 2022 · 4 comments
Open
1 task

Add option to automatically create new release #1062

KPostOffice opened this issue Jun 10, 2022 · 4 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries.

Comments

@KPostOffice
Copy link
Member

Problem statement

With the new feature which creates tags after a release PR is merged, some users may also want to automatically generate a release as well.

High-level Goals

Give users a configuration option to automatically create a release when the new version tag is pushed.

Proposal description

Create new release using OGR/GitHub api right after a version tag is created. It should just contain change logs.

Acceptance Criteria

  • Add concrete acceptance criteria
@KPostOffice KPostOffice added the kind/feature Categorizes issue or PR as related to a new feature. label Jun 10, 2022
@harshad16
Copy link
Member

/triage accepted
/priority backlog
/sig user-experience

@sesheta sesheta added triage/accepted Indicates an issue or PR is ready to be actively worked on. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. labels Jun 15, 2022
@sesheta
Copy link
Member

sesheta commented Sep 13, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 13, 2022
@VannTen
Copy link
Member

VannTen commented Sep 21, 2022

/lifecycle frozen
/remove-triage accepted
(Since the acceptance critera are not yet concrete)

The docs says that kebechet does not create release, so maybe that would mean creating a "releases managers", separate from the version manager ?

@sesheta sesheta added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Sep 21, 2022
@harshad16
Copy link
Member

yeah corect, either we would extend version to create the github release or have a separate release manager, I think it would be left on convenience and easy of fitting in the structure of kebechet

@codificat codificat moved this to 📋 Backlog in Planning Board Sep 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries.
Projects
Status: 📋 Backlog
Development

No branches or pull requests

4 participants