show web ui version number to users

[tbsbdr]

Description

User Stories

• As a owncloud product owner/manager I want to know the version of oc Web that im currently looking at in a deployment so that i can qualify meaningful bugreports.

Value

• save developers time

Acceptance Criteria

• show web ui + backend version number in html meta tag
• show web ui + backend version number in console

examples:

• <meta name="generator" content="ownCloud Web UI 4.5.0, ocis 10.0.11 reva">
• <meta name="generator" content="ownCloud Web UI 4.5.0, ownCloud 10.8.0 community">
• print version number in console "ownCloud Web UI 4.5.0"
• print version number in console "ocis 10.0.11 reva"

Definition of done

• Functional requirements
  [ ] functionality described in the user story works
  [ ] acceptance criteria are fulfilled
• Quality
  [ ] code review happened
  [ ] CI is green
  [ ] critical code received unit tests by the developer
  [ ] automated tests passed (if automated tests are not available, this test needs to be created and passed
• Non-functional requirements
  [ ] no sonar cloud issues

[kulmann]

We typically have the syntax v4.4.0

But I see a different issue: Right now we're releasing ownCloud Web as one bundle with a couple of core apps, with only one single version number for the whole bundle. But each extension could have its own version number, and especially when it's not maintained by ownCloud, it probably / hopefully will have one. So my main question is: what are we trying to solve?

• versioning information for support/engineering?
• versioning information for admins?
• is the version of the web ui really sufficient? don't you also want to know the version of the backend?

I think the visible area of the web ui is not the best place to provide versioning information. We could give a comprehensive list of involved software and their respective versions in the browser console. Or in a dedicated System info panel which is reachable from some sub menu.

The least info I'd expect is the backend version and the version of the web-ui. If the backend is oCIS it typically contains a certain release of the web ui, so in that case we wouldn't even need the version of the web-ui, but only the oCIS version.

[tbsbdr]

as discussed: lets write the version and additional info as you like as meta tags into the html header

[dragotin]

@hodyroff FYI