#342 Overloading of "tag"
Closed: Fixed None Opened 8 years ago by tibbs.

There are git tags shown under the "Tags" menu, and tags you can place on issues. I happened to want to look at the interface for tagging issues and clicked the Tags menu looking for that.


Tagging issues is done on the issue itself.

Then in the settings of the project you can edit or drop tags used on issues.

What about renaming the Tags tab Releases ?

I thought I replied to this via email {just to see if that works} and my client indicates that the message was sent but it was never received. I'll file a separate ticket for that.

In any case, I guess "Releases" matches what github does, but then I know how you don't really like to correlate tags and releases. I can't really think of anything else to use.

On Sun, Aug 16, 2015 at 01:49:44AM +0000, pagure@pagure.io wrote:

I thought I replied to this via email {just to see if that works} and my client indicates that the message was sent but it was never received. I'll file a separate ticket for that.

In any case, I guess "Releases" matches what github does, but then I know how you don't really like to correlate tags and releases. I can't really think of anything else to use.

Well, if upstreams do their job correctly a tag corresponds to a release, so I
am fine with this (note: pagure allows uploading a tarball as well).

So let's change the tab and url endpoint to be Release instead of Tags
and redirect the existing url from /tags to a /releases as well.

This is an easyfix, I'll mark it as such

Thanks!

This has been fixed already actually :)

Indeed it has, though I would suggest "Releases" instead of "Release". Not that it makes much difference.

Login to comment on this ticket.

Metadata