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

Upstream changelog for Bohdi updates #2282

Open
1 task
LecrisUT opened this issue Apr 15, 2024 · 1 comment
Open
1 task

Upstream changelog for Bohdi updates #2282

LecrisUT opened this issue Apr 15, 2024 · 1 comment
Assignees
Labels
area/fedora Related to Fedora ecosystem complexity/single-task Regular task, should be done within days. gain/low This doesn't bring that much value to users. impact/high This issue impacts multiple/lot of users. kind/feature New feature or a request for enhancement.

Comments

@LecrisUT
Copy link
Contributor

LecrisUT commented Apr 15, 2024

Description

Have an option to use the upstream's release notes when the koji build's Release == 1, i.e. the Version has changed, not the Release.

Benefit

I've occasionally seen well formatted (markdown-like) release notes in the Discover app. It would be nice to have the packit generated notes have a similar format. Not sure what the format is supposed to be for that, maybe: It's just markdown copy-pasted in

**Changelog**
```
# Markdown formatted text?
```

Example

https://bodhi.fedoraproject.org/updates/FEDORA-2024-2ffe03eaa6
Screenshot_20240422_092539

Participation

  • I am willing to submit a pull request for this issue. (Packit team is happy to help!)
@lbarcziova lbarcziova added kind/feature New feature or a request for enhancement. area/fedora Related to Fedora ecosystem complexity/single-task Regular task, should be done within days. gain/low This doesn't bring that much value to users. impact/high This issue impacts multiple/lot of users. labels Apr 15, 2024
@lachmanfrantisek
Copy link
Member

Hi @LecrisUT , thanks for the suggestion.

Even though we currently mimic the behaviour of Bodhi (for Rawhide), this makes a lot of sense. Especially for stable releases. We've just discussed this within a team and a new action to (re)define the output might be the possible solution. (And similarly to the specfile changelog, we can provide various sources (e.g. specfile changelog and upstream changelog) in the form of an env. var.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/fedora Related to Fedora ecosystem complexity/single-task Regular task, should be done within days. gain/low This doesn't bring that much value to users. impact/high This issue impacts multiple/lot of users. kind/feature New feature or a request for enhancement.
Projects
Status: backlog
Development

No branches or pull requests

3 participants