Release #895
Updated by Hammel 11 months ago
Once all the scheduled 2.0 issues are closed I can make a 2.0 release. See RM #691, RM #538, RM #427 and RM #348 for examples of making the release. Ironman will not be released with Harkonnen. The Dev Platform and all System package collections (RM #894) must be archived and compressed (RM #782). h1. Steps to release # -Reassign severity/priority of issues to to 2.0.- Update metabuild support for "replacing tags":https://stackoverflow.com/questions/20076233/replace-remote-tag-with-git/55250897#55250897 ## -Move issues to 3.0- Assumes tag has already been applied but in wrong place. ### These all assume being on master branch ### Delete existing tag: git push origin :refs/tags/<tagname> ### Move tag in local repo: git tag -fa <tagname> ### Push the tag: git push origin --tags # Tag all repos ## Use Add dry-run option with to 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 2.0 # Generate changelog: MakeChangelog.sh in metabuild # Generate compressed release images (dd from installed SD card) ## Dev platform + System package collections ## rpi1 & rpi2 (see matrix) ## Naming convention: pibox-rpi<hw>[rpi<hw>...]-<system>.img, as in pibox-rpibplus-devplatform.img or pibox-rpi2rpi3-media.img ## Don't include source or staging archives anymore! # 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 ### Systems #### 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 # Generate changelog: MakeChangelog.sh in metabuild # Write up announcement ## add it to News (as in "this example":http://redmine.graphics-muse.org/news/17) ## Announce to "RPi Forums":http://www.raspberrypi.org/forums/viewtopic.php?p=611042#p611042 ## Announce to "eLinux.org":http://elinux.org/RPi_Distributions#PiBox ## Post to ### LinkedIn-: Raspberry Pi and Embedded Linux groups ### User groups: blug, clue, pplug, CS Open Source Meetup # Reassign severity/priority of pre-2.0 issues. ## Move issues to 2.1, 2.2 or 3.0