Skip to content

Research: Include correct version number on Gitlab Preview Page

The Preview page previously showed version number (see image below). That challenge with this was that between the 18th and the 22nd, it would jump to the next version based on this logic, and be incorrect, causing confusion for customers (Slack threads: https://gitlab.slack.com/archives/C0NFPSFA8/p1595269752151900; https://gitlab.slack.com/archives/C016AV33NE8/p1595348706459700) regularly. (The page is based on this logic)

Via MR www-gitlab-com!56879 (merged) we decided to test removing version number. We believe this will have its own challenges in that now, all month, we won't have a clear version number referenced thus more potential confusion for sales team and customers. We plan to address this as the feedback rolls in but copy adjustments are ultimately not going to fix this problem.

The proper solution would be to find a way to have the correct version number show on this page, but given that we're moving toward upgrading and leveraging the in product Releases feature in the future, we don't want to over invest in a short term problem.

What could be a good solution to add the version number to the page, without too much heavy lifting in terms of engineering work? Are any of these viable options:

  • Have the date version numbers change hard coded, since we know the release will always happen on the 22nd
  • Have the page logic rely on the release post merging to change version numbers
  • Somehow modify our unreleased folders so that we don't blend two releases together toward the end of the cycle and can keep the version number / date / source consistent until the 22nd.

Screen_Shot_2020-07-21_at_4.22.42_PM

Edited by Farnoosh Seifoddini