Make 2.0 release: Harkonnen
Steps to release¶
- Reassign severity/priority of issues to to 2.0.
- Move issues to 3.0
- Tag all repos
- Use dry-run option with tagging to show what would happen for each repo without doing it, to make sure this still works.
- Update all tags for 2.0
./build.sh -t v2.0.0
- Generate changelog: MakeChangelog.sh in metabuild
./MakeChangelog.sh -s 2020-06-15
- Generate compressed release images (dd from installed SD card)
- Dev platform
make pkg (generates pibox-rpi<hw>-2.0.tar.7z)
- rpi1 & rpi2 (see matrix)
- System package collections: metabuild/build.sh (manually create 7z tarballs)
7z a -m0=lzma2 -mx=9 $(PKGDIR)/pibox-<hw>-$(VERSION)-<systemname>.tar.7z <pkgdir>/*.opk
- Dev platform
- Push release images to download site
- Push download archives (archives downloaded by xcc, buildroot, etc. as part of build process) to download site
- Update directory listing on upload site
- Update wiki (RM #958)
- Reference install.txt
- Update PiBoxProject.com
- New Layout
- Dev Platform
- Note HW/Display requirements for PiStore, PiSentry
- New Videos
- One for each System
- New Blog Entries
- One for each system
- One for each app
- Blog Post on 2.0 release
- New Layout
- Write up announcement
- % Done changed from 10 to 30
Doing all builds on my colo I've run into several problems related to networking and the Docker image.
- Docker iptables don't always mesh with the host iptables when doing certificate checks with wget. To get around this, add the following to ~/.wgetrc
- check_certificate = off.
- Docker may try to bind ipv6 addresses instead of ipv4 which can break when trying to connect to some remote archives. To get around this, enable ipv6 forwarding on the host
- sudo sysctl net.ipv6.conf.all.forwarding=1
- The colo site may block some remote sites in places like Russia (such as strace.io). This may require patches to the package.mk files in Buildroot.
I'm doing the builds on the colo to avoid large file transfers from home exceeding my xfer limits on Comcast. If I do them on the colo I can just copy the build artifacts to their local archive locations without any network bandwidth used. It's interesting to see what issues I run into when doing it like this that I don't see on my home systems.
- Issues have been reassigned for 3.0.
- Repos have been tagged.
- Changelogs have been generated and added to .ReleaseAnnouncement (which is not published yet)
- Dev platform and system packages generated
- Released images pushed to archive locations
- Download archives pushed to archive locations
- Directory listings on download site have been updated.
- Status changed from New to Closed
- % Done changed from 30 to 100
This is now complete. I posted the News item and a short blog post on the web site. But I didn't do a wider announcement because at this point I don't think it matters.
I'm closing this issue and starting work on 3.0. That will likely be my last release, unless I get a boatload done really quickly. After that, I'll retire the project or hand it off to some interested party.