aboutsummaryrefslogtreecommitdiffstats
path: root/releasevars.sh
Commit message (Collapse)AuthorAgeFilesLines
* Release procedure: Add information about key handlingDenis 'GNUtoo' Carikli2020-10-241-1/+10
| | | | | | | | | | Before, during and after a release, we need to manage signing keys: - We might need to take care of keeping the gpg signing key still valid (not expired) for some time after the release. - We also may need to migrate from one set of keys generated during the build process to a new one. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* releasevars.sh: guard against wrong RELEASE variableDenis 'GNUtoo' Carikli2020-10-241-1/+13
| | | | | | | | | This will prevent developers from accidentally pushing tags for a wrong version on new repositories that weren't tagged yet by the previous releases, and also prevent from pushing tags with the same name than branches. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* Remove VERSION to be able to use release.sh on branches tooDenis 'GNUtoo' Carikli2020-10-241-12/+12
| | | | | | | | | | | | | | | | | | | | | | To use these scripts, users and developers are expected to define the VERSION and RELEASE variables. For instance: VERSION="6.0" RELEASE="0004-rc2" However if you want to build Replicant 6.0 not as part of an official release process, all the scripts expect a minor version, which is not relevant for a branch. This could for instance be used by anyone, including people that don't have the ability to push tags to release their own builds of Replicant along with information about the source code used to produce these images. So instead of the VERSION and RELEASE example above we could have: RELEASE="6.0-0004-rc2" Or if we build a branch: RELEASE="6.0" Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* Bump RELEASE revision for Replicant 6.0 0004 rc2Denis 'GNUtoo' Carikli2020-07-181-1/+1
| | | | Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* Add Replicant 6.0 0004 rc1 supportDenis 'GNUtoo' Carikli2020-01-191-12/+12
| | | | | | | | | | | | | | | | This accomodates the following changes since last release: - The images paths changed to something like replicant-6.0-0004-rc1.zip - There is now a wrapper to build images in vendor/replicant/build.sh - Wolfgang's key has been replaced by my key This change doesn't take that into account but it should still be sufficent for adding the replicant-6.0-0004 tag to the various git repositories. Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* releasevars: Document RELEASE_IMAGES and cosmetics improvementsDenis 'GNUtoo' Carikli2020-01-191-2/+35
| | | | Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
* Replicant 6.0 0003 images releaseWolfgang Wiedmeyer2017-12-101-1/+1
| | | | Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
* Replicant 6.0 0002 images releaseWolfgang Wiedmeyer2017-09-101-3/+3
| | | | | | adds newly supported devices Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
* Replicant 6.0 0001 images releaseWolfgang Wiedmeyer2017-05-071-0/+44
Besides updating the scripts to account for changes introduced after Android 4.2, the following modifications were made: * Introduce releasevars.sh to store frequently used variables * Remove SDK parts and devices not yet supported by Replicant 6.0 * Add unpackbootimg to release tools * Use my GPG key for signing * Use more functionality from the repo tool to simplify the scripts * Only accept tags for git metadata. * Additionally tag the LineageOS mirror besides our forked repos. Ignore the manifest repo as it's tagged manually. * Add releasebuild.sh script to build all targets and the toolchain * Make sure a bash shell is used * Use repo tool from $PATH * Abort on error Signed-off-by: Wolfgang Wiedmeyer <wolfgit@wiedmeyer.de>
generated by cgit v1.2.3 (git 2.25.1) at 2024-04-28 08:12:18 +0000