Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Solus 4.7 Release Checklist #4226

Closed
28 tasks done
TraceyC77 opened this issue Nov 3, 2024 · 1 comment
Closed
28 tasks done

Solus 4.7 Release Checklist #4226

TraceyC77 opened this issue Nov 3, 2024 · 1 comment
Assignees
Labels
Type: Chore Not a feature or a bug

Comments

@TraceyC77
Copy link
Contributor

TraceyC77 commented Nov 3, 2024

Action Item checklist for final release

  • Write blog post Update for 4.7 Release solus-site.github.io#59
  • Bump baselayout Still broken, so no
  • Update os-release
  • Sync to Shannon
  • Take decluttered screenshot in each desktop edition at 1080p (Installed environment with only default desktop icons after install). Create a desktop collage image and save to the release images folder Evan was first, use images from Help center PR https://github.com/getsolus/help-center-docs/pull/596/files
  • Test all the things in Software Center Third Party, update where necessary
  • Download and import the Solus private releng GPG key from BitWarden
  • Cook and upload all ISOs based on stable (aka Shannon) using the ISO creation script:
    ./infrastructure-tooling/build_isos.sh release
    • The uploaded assets will need to be copied to the appropriate /srv/www/downloads/isos/ folder on packages.getsol.us. For Release ISOs, this would be /srv/www/downloads/isos/${VERSION}/
    • From there it'll need to be hard linked into all backer tier folders. Use the command ls -golthr to see how many hardlinks an ISO has
      sudo mkdir /srv/www/downloads/isos/${VERSION}
      sudo ./infrastructure-tooling/make_links.sh -s ${UPLOADED_ISOS_DIR} -d ${VERSION} -t crew,beta,releasetesters
  • Validate all ISOs. See the GitHub task for the current release
    • Budgie
    • GNOME
    • Plasma
    • Xfce
  • Take de-cluttered screenshot in each edition at 1080p for use as updated release images
  • Update Help Center
    • Update Editions
      • Add/remove any editions (check paths src/components/editions.jsx and docs/user/editions/ as of 4.5)
      • If there are new editions, create skeletal structure for it and create issue to document configuration and tips n' tricks sections for the new edition. (check paths docs/user/editions/ as of 4.5)
      • Update edition screenshots with updated release images (check path src/editions/$EDITION.{jpg,png} as of 4.5)
      • Ensure edition descriptions to match the descriptions on the download page e.g. Budgie: A feature-rich, luxurious desktop using the most modern technologies. (Check paths src/components/editions.jsx and i18n/en/code.json as of 4.5.)
    • Update Help Center Docs references from current release to upcoming release (e.g. 4.1 -> 4.2) Update docs for new release help-center-docs#596
  • Sync modules via make sync in solus-site This is an old step from somewhere
  • Update data/info.yaml in solus-site with the new version, media size, and sha256sum Update for 4.7 Release solus-site.github.io#59
  • Create featured image for release blog post (imagemagick collage)
  • Create torrent files using qBitTorrent with the following settings (if not mentioned, leave the setting at its default):
    • Torrent format: V1
    • Tracker URLS:
      udp://tracker.opentrackr.org:1337/announce
      udp://tracker.openbittorrent.com:6969
    • Web seed URLs:
      https://downloads.getsol.us/isos/${VERSION}/Solus-${VERSION}-${EDITION}.iso
    • Comments:
      Solus ${VERSION} ${EDITION} Edition Official Release
    • Example qBitTorrent GUI image:
      qBitTorrent example .torrent creation screenshot
    • Create the .torrent file with a name template matching Solus-${VERSION}-${EDITION}.torrent; e.g Solus-4.4-Budgie.torrent
  • Upload .torrent files for each edition to packages.getsol.us and place them in /srv/www/torrents/
  • Deploy site
  • Deploy Help Center
  • Publish to social media
  • Party time! 🎉

Associated PRs

@github-project-automation github-project-automation bot moved this to Triage in Solus Nov 3, 2024
@EbonJaeger EbonJaeger self-assigned this Jan 24, 2025
@EbonJaeger EbonJaeger added the Type: Chore Not a feature or a bug label Jan 24, 2025
@EbonJaeger EbonJaeger moved this from Triage to In Progress in Solus Jan 25, 2025
@davidjharder
Copy link
Member

davidjharder commented Jan 26, 2025

Stashing my torrent creation script here for now.

Notes

  • Requires py3createtorrent install with pipx or similar
  • Assumes you are in a directory with the isos, see the globbing in INPUT, not terribly sophisticated
  • Name jank: Pass FILENAME.iso and ask for output FILENAME.iso creates FILENAME.iso.torrent, we expect FILENAME.torrent. Probably makes sense to change website links to suit
#!/bin/bash
set -E pipefail

for EDITION in "Budgie" "GNOME" "XFCE-Beta" "Plasma"
do
    VERSION="2025-01-26"
    RELEASE_TYPE="Release"
    TRACKER1="udp://tracker.opentrackr.org:1337/announce"
    WEBSEED="https://downloads.getsol.us/isos/${VERSION}/Solus-${EDITION}-${RELEASE_TYPE}-${VERSION}.iso"
    COMMENT="Solus ${EDITION} ${VERSION} Official Release"
    OUTPUT="Solus-${EDITION}-${RELEASE_TYPE}-${VERSION}.iso"
    INPUT="*${EDITION}*"
    py3createtorrent $INPUT -t $TRACKER1 -n $OUTPUT -c "$COMMENT" --webseed $WEBSEED
done

@github-project-automation github-project-automation bot moved this from In Progress to Done in Solus Jan 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Chore Not a feature or a bug
Projects
Status: Done
Development

No branches or pull requests

3 participants