Difference between revisions of "Developer Area/Release Instructions/Release day"
From Mahara Wiki
< Developer Area | Release Instructions
Line 14: | Line 14: | ||
ย | *โ
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? | |
ย | *โ
<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 [https://launchpad.net/~username/+editpgpkeys https://launchpad.net/~username/+editpgpkeys] | ย | *โ
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 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> |
ย | + | ||
ย | + | ==๐ Prep + run the first part of the release script == | |
ย | + | ||
ย | + | === rep 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: <code>./release.php X.Y.Z X.Y_DEV (For rc X.Yrc1)</code> | |
ย | + | * 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: <code> git config --global gpg.program gpg2 </code> | |
ย | + | ||
ย | + | 2) Tested if it was working: <code> echo "test" | gpg2 --clearsign </code> | |
ย | + | ||
ย | + | It wasn't so I had to do: <code> export GPG_TTY=$(tty)</code> | |
ย | + | ||
ย | + | then run again <code> echo "test" | gpg2 --clearsign</code> | |
ย | + | ||
ย | + | After all that when I ran release.php command again it didn't give me the error |
Revision as of 14:17, 25 February 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 lead
- โ 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
๐ Prep + run the first part of the release script
rep 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