docs: Create RELEASES.md

[amye]

Draft release checklist that may be way too heavy!

[gemini-code-assist]

Summary of Changes

Hello, 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 a structured and detailed release process for the Agent2Agent (A2A) project. The newly added RELEASES.md document outlines all necessary steps from pre-release preparation and validation to the actual release creation and post-release tasks, aiming to standardize and streamline future releases.

Highlights

• New Release Checklist Document: A new RELEASES.md file has been added, providing a comprehensive, step-by-step checklist for managing releases of the Agent2Agent (A2A) protocol specification and associated documentation.

Changelog

• RELEASES.md
  • Added a comprehensive release checklist for the Agent2Agent (A2A) protocol.

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

This pull request introduces a release checklist in RELEASES.md. The checklist is very thorough and well-structured. My feedback includes a few minor formatting suggestions for consistency and readability, as well as a suggestion to merge some duplicated steps to make the process more streamlined, addressing your concern about it being potentially 'too heavy'.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[holtskinner]

Some of the parts in the process are automated with release-please already, so we might not need to spell them out directly, but overall good steps.

[amye]

Some of the parts in the process are automated with release-please already, so we might not need to spell them out directly, but overall good steps.

I knew they were already here just generally, but I'm documenting nearly everything that I can think of! For example, every time we push a release, we should update /docs/roadmap.md to help keep things clean and give ourselves a good boundary to make sure we're on top of our communications.

I'll hold off committing this until we're through the release process for 1.0 and we can update subsequently from here.