Prerequisites for changing Solus versioning scheme

Open
#4,829 0 comments 4 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Domain
documentation, release, tooling

Research direction

Start by reviewing the prerequisite checklist and the existing website and tooling affected by release version numbers; the issue names no specific files or tests. Done means the Solus 4.9 announcement, scheduled social posts, sync notes, and OC emailings cover the change, and the version switch is confirmed not to break the website or tooling.

Written by the indexing model from the issue text.

Description

Priority: Normal Topic: Plumbing

In meetings, we have discussed a desire to change to a date-based versioning system for Solus releases instead of the traditional numbers we use now. Since we are a curated rolling release distribution, a regular version number like "4.6" is largely meaningless. By moving to a date-based system, for example, "Solus 2025.01", it then becomes very clear when an ISO is from, which may be helpful for troubleshooting later on. Our ISO file names already include the date they were generated.

Before we can switch to a new system, though, we need to do some things in advance to let users know that the change is upcoming. This should be done so that when the time comes, there is less of a chance that users will be blindsided by having the version number jump by over 2000.

Prerequisites
  • Mention in the next release's blog post (Solus 4.9)
  • Social media posts 1 month ahead of the switch
  • Mention in each week's sync notes starting 1 month ahead of the switch
  • Mention in OC emailings each week starting 1 month ahead of the switch
  • Ensure that the version switch doesn't somehow break our website or tooling
Dominant language
Python
Stars
141
Forks
146
Avg merge
11h 7m
Merged PRs (30d)
407

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from getsolus/packages

All issues in getsolus/packages

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.