Difference between revisions of "Developer Area/Release Instructions/Release day"
From Mahara Wiki
< Developer Area | Release Instructions
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 13: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