Overview

Request 1188686 accepted

Update to version 3.1.0
with shortened change-log

Loading...


Alexandre Vicenzi's avatar

Can we clean up GitHub issues associations from the changelog? It looks odd and pollutes the changelog. I also noticed that there are a few old entries that also include, while many don't. Having consistency is also good.


Johannes Weberhofer's avatar

What form would you prefer? Completely remove the references for new features? They might be of interest for bug fixes. Wen could also group the issues thematically. I personally like the gh#.../...# prefix, because the issues are directly linked via OBS.


Alexandre Vicenzi's avatar

We could keep it, but perhaps clean up a bit. Grouping the issues could be useful also.

Each fix should be a one-liner, not split into multiple lines, and ideally just include a #123 or gh#123, removing the "by user" part.

Anything that users can read easily and understand to be honest, currently it feels hard to understand what is going on with a given update.

Something like:

  • [k8s,k8s/gatewayapi] Support invalid HTTPRoute status

or

[k8s,k8s/gatewayapi] Support invalid HTTPRoute status (#10714)

or

[k8s,k8s/gatewayapi] Support invalid HTTPRoute status (gh#10714)

I believe all issues belong to gh#traefik/traefik, if not, it does not make much sense to link to another project, that is why perhaps only #10714 could be used.


Johannes Weberhofer's avatar

The nice think on the gh#...#number notation is, that you can see it on the "mentioned issues" tab in OBS.


Request History
Johannes Weberhofer's avatar

weberho created request

Update to version 3.1.0
with shortened change-log


Alexandre Vicenzi's avatar

avicenzi accepted request

openSUSE Build Service is sponsored by