chore: add release documentation

[mmartinv]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @mmartinv, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces essential documentation for the release process of the go-fdo-client project. By adding a RELEASING.md file, it standardizes the steps required to publish new versions, ensuring consistency and clarity for all future releases. This change aims to streamline the release workflow and reduce potential errors.

Highlights

• New Release Documentation: A new file, RELEASING.md, has been added to the repository, providing comprehensive documentation for the release process.
• Step-by-step Release Guide: The document outlines a detailed, step-by-step guide for releasing new versions of the go-fdo-client, using v0.0.1 as a practical example.
• Comprehensive Release Workflow: The guide covers the entire release workflow, including creating a release branch, updating version numbers in go-fdo-client.spec, verifying builds, committing changes, creating a pull request, tagging and signing the release, and drafting the release on GitHub.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

The pull request introduces a new RELEASING.md document, which provides a clear and comprehensive guide for releasing new versions of the go-fdo-client. The steps outlined cover everything from preparing the repository and updating version numbers to tagging the release and publishing it via the GitHub UI. The document is well-structured and easy to follow. I've provided a few suggestions to enhance clarity and robustness, particularly around version management and the rationale behind certain steps.