#701 Per-release pages possibly with release notes (tag message/changelog file diff/explicit text)
Closed: Fixed Opened by jpokorny.

Since I started a practice of tag message = changelog summary, I really
miss a choice to link directly to persistent pagure.io project-namespaced
URL for details about particular release (say, in spec changelog).

Best if this is carefully considered together with issue #570, as there
is likely an overlap and the UI complexity should rather not be increased
significantly.

Also relevant is issue #420 in which I originally asked for propagating
at least some (=headline) bits from the tag message at all. Now, I am
simply asking also for the rest :)


I am not sure to fully understand what you are looking for, would you have an example? Perhaps on gitlab or github or elsewhere?

I don't like to provide ready-made examples as they may be, undesirably, taken as the only way the feature can be implemented (hence the suggestion to take also diff of changelog [possibly user-provided path] against the previous tag into account to at least go a bit further), but since you asked, I want to rewrite links like following to point to pagure.io:

https://pkgs.fedoraproject.org/cgit/rpms/clufter.git/tree/clufter.spec?id=66c5d87c7434e578110d621e9e3074f1da63b62e#n273

And all these info are stored in git? As part of the tag?

git clone https://pagure.io/clufter.git && git tag -ln999 v0.56.0

Also cgit supports the bare bones that would be handy for me.
When it gets eventually published (there's a delay):
https://fedorapeople.org/cgit/jpokorny/public_git/clufter.git/tag/?id=v0.56.0

Note that GPG signatures should be stripped.

Tag messages are now shown as of pagure 2.0:

https://pagure.io/clufter/releases

Thanks to @ryanlerch at https://pagure.io/pagure/pull-request/879

Closing this :)

Thanks, @ryanlerch.
THere are still some subtleties, though, see PR #933.

Metadata