#9 v0.13.0-1

Merged
yksflip merged 4 commits from v0.13 into master 9 months ago
yksflip commented 9 months ago
Owner

Release Procedure

Version: v0.13.0-1
Gluon Version: 2019.1.2

Notes:

  • First Build had to be canceld because of missing GLUON_BRANCH variable during build. Which led to a wrong autoupdater setting in factory image

Pre-Build

Summarize changes on site-ffhl:

  • Add batman adv compat15 domain

  • Add Scheduled-Domain-Switch for 03.09.2020 22:00

Build Firmware

Beta Release

Sign Firmware

Monitor Beta Nodes

Then check for about 2 weeks that nodes with the beta branch selected in their autoupdater updated and run fine. Make sure to have at least one device of the more popular ones on a beta branch.

If not, abort and repeat process with increased build number

Stable Release

Pre-Stable-Rollout

Peri-Stable-Rollout

  • Daily:
    • Check that the predicted number of nodes updates to the new firmware version
    • For the nodes which updated successfully, check their status page:
      • enough RAM
      • load ok (usually < 1)
      • neighbor link quality ok
    • Monitor mailing lists for passenger feedback

In case of any issues occurring, abort.

Post-Stable-Rollout

See wiki for more details.

# Release Procedure Version: v0.13.0-1 Gluon Version: 2019.1.2 Notes: * First Build had to be canceld because of missing GLUON_BRANCH variable during build. Which led to a wrong autoupdater setting in factory image ## Pre-Build - [x] Create Version Branch - [x] Update README.md Summarize changes on site-ffhl: - Add batman adv compat15 domain - Add Scheduled-Domain-Switch for 03.09.2020 22:00 - [x] Create Versions Tag - [x] Create Merge Request ## Build Firmware - [x] Build Firmware / Run CI. (Firmware for rollout should be build on trusted hardware) - [x] Visually check that `output/images/*` and the contents of `output/images/sysupgrade/{stable,beta}.manifest` looks fine. - [x] make sure, all desired targets were built - [x] copy output images to srv02 (/var/www/firmware/) - [x] chown to directory `www-data:www-data` ## Beta Release - [x] manually download and flash a few images to a few devices to check that the overall build process went fine. ### Sign Firmware - [x] Get minimum amount of signatures - [x] Update the beta.manifest on the server with the new, added signatures below the "---" in the local copy of the beta.manifest. - [x] update `beta` symlink on srv02 ### Monitor Beta Nodes Then check for about 2 weeks that nodes with the beta branch selected in their autoupdater updated and run fine. Make sure to have at least one device of the more popular ones on a beta branch. - [x] Nodes are alive and stable with new version number (check node's status page) - [x] Check that all wifi interfaces are up and running (run ``iwinfo`` via ssh) - [x] Check that meshing works (run ``batctl o`` via ssh) - [x] Check that the process list looks fine (run ``ps`` via ssh - no missing processes? no new, suspicious processes?) - [x] Check that `/etc/config/autoupdater` looks fine and has the correct public keys - [x] Check that `/etc/dropbear/authorized_keys` was left unmodified If not, abort and repeat process with increased build number ## Stable Release - [x] Update DATE in local stable.manifest - [x] Get minimum amount of signatures - [x] Update the DATE in the stable.manifest on the server with the new start time. - [x] Update the stable.manifest on the server with the new, added signatures below the "---" in the local copy of the stable.manifest. - [x] update `stable` symlink on srv01: ### Pre-Stable-Rollout - [x] Verify that images are downloadable via https://luebeck.freifunk.net/firmware/0.xx.y-z/sysupgrade/ - [x] Verify that stable.manifest on the server contains a sufficient amount of valid signatures - [x] Verify that the start DATE of the stable.manifest on the server is correct - [x] Then prior the stable update start date, inform passengers: Inform about scheduled landing time of the new release and the firmware changes it contains on the talk@luebeck.freifunk.net mailing list. ### Peri-Stable-Rollout * Daily: * Check that the predicted number of nodes updates to the new firmware version * For the nodes which updated successfully, check their status page: * enough RAM * load ok (usually < 1) * neighbor link quality ok * Monitor mailing lists for passenger feedback In case of any issues occurring, abort. ### Post-Stable-Rollout - [x] Check if any nodes might have failed updating (any nodes that might have gone offline, especially during the update time at about 04:00 o'clock. * If available, inform individual node owners via the contact information they set in the config-mode about their failed update. If possible, determine cause for failure. - [x] Check that new Firmware version is available on the wizard and add new firmware to the list https://firmware.luebeck.freifunk.net/wizard - [x] Update https://luebeck.freifunk.net/: Add a new blog entry to inform about the new firmware release - [x] Inform via Twitter about the new firmware release - [x] Increment DEFAULT_GLUON_RELEASE in https://gitlab.com/freifunk-luebeck/site-ffhl/blob/master/site.mk See [wiki](https://wiki.luebeck.freifunk.net/docs/firmware/release-procedure/) for more details.
paul approved these changes 9 months ago
paul left a comment

looks fine to me

yksflip changed title from WIP: v0.13.0 to WIP: v0.13.0-1 9 months ago
yksflip changed title from WIP: v0.13.0-1 to v0.13.0-1 9 months ago
yksflip merged commit 8afd322360 into master 9 months ago

Reviewers

paul approved these changes 9 months ago
The pull request has been merged as 8afd322360.
Sign in to join this conversation.
No reviewers
No Milestone
No Assignees
2 Participants
Notifications
Due Date

No due date set.

Dependencies

This pull request currently doesn't have any dependencies.

Loading…
There is no content yet.