Issues with current Releases page
I believe the current implementation of GitLab releases, see gitlab-org/gitlab-ce#41766, has multiple bugs and issues.
A few months ago I started using the Repository=>Tags page in GitLab and write some release notes there. Now I've discovered the new "Releases" page, and there are two quite big issues:
-
Only the "tags" that I gave a description in the "Tags" page on GitLab turn up on the Releases page. The other ones turn up of course on the Tags page, but not on the Releases page. I believe this to be quite confusing. Furthermore, what if I add "Release notes" now on the Tags page? Will it suddenly turn up on the Releases page? And then this is information duplication in the first place - there will be the same text/release notes displayed both on the Tags and Releases page.
-
The ordering in the Releases page went completely bogus for my project. A minor version released later than a patch version is at the bottom of the page. All the releases show "released 3 month ago". Not true. The date + time that is displayed there is neither the time of the commit nor the tag or anything else from git. Maybe this is the time when I added the "Release notes" on the Tags page...? But certainly I don't want to have the Releases ordered by what time I added the release notes on the Tags page!
Additionally, the Tags page has a button "Release notes", which makes the whole thing really confusing... Tags page, Releases page... two sets of release notes? Some releases displayed on one page but not on the other... pure confusion from a user's perspective.
And one minor issue: I believe the short commit hash and the tag should both link to the git commit. Currently they just have a tooltip. And the commit hash is not really useful for a human, if you can't click it.
Also, gitlab-org/gitlab-ce#53364, https://gitlab.com/gitlab-org/gitlab-ee/issues/3848#note_46472046, https://gitlab.com/gitlab-org/gitlab-ee/issues/5135 and &69 are related to this, particularly https://gitlab.com/gitlab-org/gitlab-ee/issues/3848#note_46472046 and the following comments bring up a few good points.
I'm happy to point GitLab support to the repo where this happened, it's a private repo, so please support contact me if they'd like to have the links.