Actions

Developer Area/Release Instructions/Release day: Difference between revisions

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 15: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

📋 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

Retrieved from ‘https://wiki.mahara.org/index.php?title=Developer_Area/Release_Instructions/Release_day&oldid=12777’