Show plugin release date in plugin manager

[daniel-beck]

This was one of the feedbacks at the contributor summit at FOSDEM: It would be helpful to see at a glance when a plugin was released, to help understand how actively it is maintained.

Up to date screenshots in #4535 (comment)

Proposed changelog entries

• Show plugin release date in plugin manager

Proposed upgrade guidelines

N/A

Submitter checklist

• [n/a] JIRA issue is well described
• Changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developer, depending on the change). Examples
  • Fill-in the Proposed changelog entries section only if there are breaking changes or other changes which may require extra steps from users during the upgrade
• [n/a] Appropriate autotests or explanation to why this change has no tests
• For dependency updates: links to external changelogs and, if possible, full diffs

Desired reviewers

@mention

Maintainer checklist

Before the changes are marked as ready-for-merge:

• There are at least 2 approvals for the pull request and no outstanding requests for change
• Conversations in the pull request are over OR it is explicit that a reviewer does not block the change
• Changelog entries in the PR title and/or Proposed changelog entries are correct
• Proper changelog labels are set so that the changelog can be generated automatically
• If the change needs additional upgrade steps from users, upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the PR title. (example)
• If it would make sense to backport the change to LTS, a JIRA issue should exist and be labeled as lts-candidate

[StefanSpieker]

That is a nice feature. Thanks 👍

[timja]

Alignment of the version column seems wrong on the available tab:

It's fine on the installed column, and I don't have any plugin updates atm, but I assume it's fine there as that's what is screenshotted

I was also happy to see that the date is localised and I get the date format that I am used to

[timja]

See #4535 (comment),

should be a minor fix hopefully

[timja]

Hmm taking another look without this change,
it already seems to be misaligned but this makes it worse,

Removing my change requested but I still think it should be improved:

it was already there, although this makes it worse

[daniel-beck]

Alignment of the version column seems wrong on the available tab:

It's due to ridiculously long version numbers like 1.12+build.201809061734 or 3.8.20200204-101107.d1d344b and left-alignment of the column content. Unrelated to this change.

[oleg-nenashev]

I wonder whether formatting would differ depending on the user locale, but it is fine even if it is not

[daniel-beck]

I wonder whether formatting would differ depending on the user locale

It does, that's the whole point of using this control.

[timja]

I wonder whether formatting would differ depending on the user locale, but it is fine even if it is not

if you see my screenshot it has a different locale to DB's

[daniel-beck]

This now depends on #4534 not being merged before this, or https://github.com/jenkinsci/jenkins/pull/4535/files#diff-6c89c5cced7eb382005a0b0825a45140R70 needs onclick removed otherwise. Should be trivial to do on GitHub and ideally not hold off merging for technicalities.

[fqueiruga]

I know I'm late to the party but I have a suggestion. Can we consider, instead of having another numeric column showing the date, showing the last release as text? That will remove mental load for the user.

We could also show that message within the version column. The information relates to the version anyway. An example:

[daniel-beck]

We could also show that message within the version column. The information relates to the version anyway.

I considered that, but was unsure how this would impact sorting by this column. Given how useless sort by version is, I guess this column would then sort by release date? Is that useful UX?

[fqueiruga]

If we want to sort by release date, we would definitely need a column just for it IMO

[daniel-beck]

If we want to sort by release date, we would definitely need a column just for it IMO

Well, the table is sortable. Right now it's possible to sort by name and version number (🤣). Sorting by date is potentially the most useful of any of them (even if there's no obvious use case other than something like getting general ecosystem status at a glance).

Anyway, I like your "time span" idea a lot better than just displaying the date. I will implement that. The specific date can always be the tool tip.

[fqueiruga]

May I also suggest using the <time> tag? With tooltip would look something like this <time datetime="2019-08-15" tooltip="15/08/2019">8 months ago</time>.

[daniel-beck]

Updated based on feedback. It now looks like this:

[jvz]

Looks nice!

[daniel-beck]

Universal approval, so marking ready-for-merge so this can go into the upcoming weekly.

[timja]

@daniel-beck are you able to resolve the conflicts please?

[daniel-beck]

*cough* #4535 (comment) *cough* 😁

[timja]

Lol, other one had been updated more recently so it was higher in the list, and your comment got buried above many other comments :p