gnu-efi/docs
Callum Farmer 57d2e370d8
Add more detail to ABI notice
Signed-off-by: Callum Farmer <gmbr3@opensuse.org>
2024-09-24 13:28:41 +01:00
..
README.ABI.md Add more detail to ABI notice 2024-09-24 13:28:41 +01:00
README.elilo.md Move docs to Markdown 2024-09-16 16:07:23 +01:00
README.git.md Add more notes to GitHub release info 2024-09-24 13:28:41 +01:00

README.git

Generating releases on GitHub is a very simple process;

Set version in repo

  1. Edit the file "Makefile". Changing the "VERSION" line to the new version.
  2. Do a "git commit" just for the version number change.

Create new release

  1. Go to the GitHub release page

  2. Enter the version number in the tag field, selecting "create tag on publish"

    Ignore GitHub's suggestion of prefixing the version with a "v"

  3. Set previous tag manually

    • Last stable for stable releases
    • Last alpha/beta for alpha/beta releases

    Ensures GitHub sets the Full Changelog to be between the last release in the cycle and not the start of the repository

  4. Add a release title - use the version number

    Otherwise GitHub will add the last commit name as the title

  5. OPTIONAL Add a release description and/or a list of pull requests and contributors via "Generate release notes"

  6. For alpha/beta versions, set it to be a pre-release

  7. Release the new version

  8. GitHub will automatically generate a GZ compressed TAR file and a ZIP file of the repo