Developer Area/Release Instructions/Release day: Difference between revisions
From Mahara Wiki
< Developer Area | Release Instructions
No edit summary |
|||
| Line 1: | Line 1: | ||
==📋 Final checks before starting release day == | ==📋 Final checks before starting release day== | ||
🚨 Make sure that any security reviews/patches are merged before proceeding 🚨 | 🚨 Make sure that any security reviews/patches are merged before proceeding 🚨 | ||
🔒 '''Security team''' (if you don't have +2 review status, you won't be able to see these patches) | 🔒 '''Security team''' (if you don't have +2 review status, you won't be able to see these patches) | ||
🛠 '''Release | *✅ Merge the 'Draft' security patches. | ||
*✅ Update the related Launchpad bugs to 'Public security'. | |||
🛠 '''Release manager''' | |||
*✅ CVE #'s - Security issues have an assigned CVE number? | *✅ CVE #'s - Security issues have an assigned CVE number? | ||
| Line 13: | Line 14: | ||
*✅ Bugs fixed - all bugs going into his release have their fixes ''merged'' for all supported versions? | *✅ Bugs fixed - all bugs going into his release have their fixes ''merged'' for all supported versions? | ||
*✅ Comms - to Mahara partners + drafted the forum posts? | *✅ Comms - to Mahara partners + drafted the forum posts? | ||
👷🏻 '''For all devs''' | 👷🏻 '''For all devs''' | ||
*✅ What minor point release are you going to do? | *✅ What minor point release are you going to do? | ||
*✅ <code>git pull [https://git.mahara.org/scripts/mahara-scripts mahara-scripts]</code> | *✅ <code>git pull [https://git.mahara.org/scripts/mahara-scripts mahara-scripts]</code> | ||
*✅ Valid GPG - do you have a [https://wiki.mahara.org/wiki/Developer_Area/Release_Instructions/Creating_a_GPG_key valid GPG key] added to your Launchpad account? See | *✅ Valid GPG - do you have a [https://wiki.mahara.org/wiki/Developer_Area/Release_Instructions/Creating_a_GPG_key valid GPG key] added to your Launchpad account? See https://launchpad.net/~username/+editpgpkeys | ||
* ✅ <code>lptools</code> - do you have the lp-upload-project installed for uploading the release tars? <code> apt-get install lptools</code> | *✅ <code>lptools</code> - do you have the lp-upload-project installed for uploading the release tars? <code> apt-get install lptools</code> | ||
==WIP Prep + run the first part of the release script == | ==WIP Prep + run the first part of the release script== | ||
=== Prep change log and release notes to go into Launchpad? === | ===Prep change log and release notes to go into Launchpad?=== | ||
// TODO | // TODO | ||
| Line 28: | Line 31: | ||
Run the first step: <code>./release.php X.Y.Z X.Y_DEV (For rc X.Yrc1)</code> | Run the first step: <code>./release.php X.Y.Z X.Y_DEV (For rc X.Yrc1)</code> | ||
===Important Check the terminal output in case there are GPG errors, === | *creating tarballs | ||
*It will also spit out another script (release-X.Y.Z-cleanup.sh) to be run later. | |||
===Important Check the terminal output in case there are GPG errors,=== | |||
Example: Tag new version bump commit as 'X.YRC2_RELEASE' error: gpg failed to sign the data error: unable to sign the tag | Example: Tag new version bump commit as 'X.YRC2_RELEASE' error: gpg failed to sign the data error: unable to sign the tag | ||
Revision as of 14:14, 11 March 2022
📋 Final checks before starting release day
🚨 Make sure that any security reviews/patches are merged before proceeding 🚨
🔒 Security team (if you don't have +2 review status, you won't be able to see these patches)
- ✅ Merge the 'Draft' security patches.
- ✅ Update the related Launchpad bugs to 'Public security'.
🛠 Release manager
- ✅ CVE #'s - Security issues have an assigned CVE number?
- ✅ Backporting - security fixes backported to all supported versions that need them?
- ✅ Bugs fixed - all bugs going into his release have their fixes merged for all supported versions?
- ✅ Comms - to Mahara partners + drafted the forum posts?
👷🏻 For all devs
- ✅ What minor point release are you going to do?
- ✅
git pull mahara-scripts - ✅ Valid GPG - do you have a valid GPG key added to your Launchpad account? See https://launchpad.net/~username/+editpgpkeys
- ✅
lptools- do you have the lp-upload-project installed for uploading the release tars?apt-get install lptools
WIP Prep + run the first part of the release script
Prep change log and release notes to go into Launchpad?
// TODO
The following uses the script you got in the previous step.
Run the first step: ./release.php X.Y.Z X.Y_DEV (For rc X.Yrc1)
- creating tarballs
- It will also spit out another script (release-X.Y.Z-cleanup.sh) to be run later.
Important Check the terminal output in case there are GPG errors,
Example: Tag new version bump commit as 'X.YRC2_RELEASE' error: gpg failed to sign the data error: unable to sign the tag
So this is what I did to fix it, all commands are on command line:
1) Updated the gpg program to use: git config --global gpg.program gpg2
2) Tested if it was working: echo "test" | gpg2 --clearsign
It wasn't so I had to do: export GPG_TTY=$(tty)
then run again echo "test" | gpg2 --clearsign
After all that when I ran release.php command again it didn't give me the error