Release 20.4.0

[Tobianas]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @Tobianas, 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 marks the official release of version 20.4.0 by transitioning all project and dependency versions from their SNAPSHOT state to the stable 20.4.0 release. It includes comprehensive updates across various Maven pom.xml files, ensuring all modules, applications, and examples reflect the new version. Additionally, several underlying OpenDaylight dependencies and build plugins have been upgraded to their latest compatible versions, enhancing stability and aligning with upstream improvements. The changes also include updates to SCM tags and example documentation to reflect the new release.

Highlights

• Project Version Update: The primary change across the repository is the update of all project and parent versions from 20.4.0-SNAPSHOT to the stable 20.4.0 release version in their respective pom.xml files.
• Third-Party Dependency Upgrades: Several OpenDaylight (ODL) related dependencies, such as odlparent, aaa-artifacts, controller-artifacts, mdsal-artifacts, and yangtools-artifacts, have been upgraded to their latest patch versions, ensuring compatibility and incorporating recent fixes.
• Build Plugin Version Alignment: Build-related plugins like yang-maven-plugin and mdsal-binding-java-api-generator have also been updated to align with the new ODL dependency versions, ensuring a consistent and functional build environment.
• SCM Tagging for Release: The Source Code Management (SCM) tags within the main pom.xml files have been explicitly set from HEAD to 20.4.0, formally marking this release in the version control system.
• Documentation Updates: Minor updates were made to README.md files in example directories to reflect the new 20.4.0 version in their java -jar commands and other usage instructions.

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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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 issue 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 prepares for the 20.4.0 release. The changes primarily involve updating version numbers from 20.4.0-SNAPSHOT to 20.4.0 across numerous pom.xml files, bumping dependency versions, and updating SCM tags. The documentation in README.md files has also been updated to reflect the new release version. Overall, the changes are consistent with a release process and look correct. I've found a couple of minor typos in the documentation that should be addressed for clarity.