Re: [PR] Revise CHANGES.md for upcoming release [beam]

2026-01-07 Thread via GitHub


damccorm merged PR #37243:
URL: https://github.com/apache/beam/pull/37243


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [PR] Revise CHANGES.md for upcoming release [beam]

2026-01-07 Thread via GitHub


damccorm commented on PR #37243:
URL: https://github.com/apache/beam/pull/37243#issuecomment-3720533062

   Thanks - fixed both


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [PR] Revise CHANGES.md for upcoming release [beam]

2026-01-07 Thread via GitHub


Abacn commented on code in PR #37243:
URL: https://github.com/apache/beam/pull/37243#discussion_r2669752057


##
CHANGES.md:
##
@@ -59,7 +59,12 @@
 * ([#X](https://github.com/apache/beam/issues/X)).
 -->
 
-# [2.71.0] - Unreleased
+
+# [2.XX.X] - Unreleased
+
+## Beam 3.0.0 Development Highlights

Review Comment:
   We can remove this section



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [PR] Revise CHANGES.md for upcoming release [beam]

2026-01-07 Thread via GitHub


Abacn commented on code in PR #37243:
URL: https://github.com/apache/beam/pull/37243#discussion_r2669751176


##
CHANGES.md:
##
@@ -59,7 +59,12 @@
 * ([#X](https://github.com/apache/beam/issues/X)).
 -->
 
-# [2.71.0] - Unreleased
+
+# [2.XX.X] - Unreleased

Review Comment:
   should be [2.72.0] ?



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [PR] Revise CHANGES.md for upcoming release [beam]

2026-01-07 Thread via GitHub


github-actions[bot] commented on PR #37243:
URL: https://github.com/apache/beam/pull/37243#issuecomment-3719497450

   Assigning reviewers:
   
   R: @shunping added as fallback since no labels match configuration
   
   
   Note: If you would like to opt out of this review, comment `assign to next 
reviewer`.
   
   Available commands:
   - `stop reviewer notifications` - opt out of the automated review tooling
   - `remind me after tests pass` - tag the comment author after tests pass
   - `waiting on author` - shift the attention set back to the author (any 
comment or push by the author will return the attention set to the reviewers)
   
   The PR bot will only process comments in the main thread (not review 
comments).


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



Re: [PR] Revise CHANGES.md for upcoming release [beam]

2026-01-07 Thread via GitHub


gemini-code-assist[bot] commented on PR #37243:
URL: https://github.com/apache/beam/pull/37243#issuecomment-3719233014

   ## Summary of Changes
   
   Hello @damccorm, I'm Gemini Code Assist[^1]! 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 prepares the CHANGES.md file for future releases by 
introducing a templated structure for upcoming versions, including a dedicated 
section for Beam 3.0.0 development highlights and security fixes. It also 
reorganizes existing release note entries to align with this new, 
forward-looking format.
   
   ### Highlights
   
   * **Release Note Templating**: The CHANGES.md file has been updated to 
include placeholders for an upcoming 2.XX.X release and a new "Beam 3.0.0 
Development Highlights" section.
   * **Security Fixes Section**: A dedicated "Security Fixes" section has been 
added to the release notes template to clearly delineate security-related 
updates.
   * **Content Reorganization**: Existing detailed release notes for version 
2.71.0 have been moved and re-categorized to fit the new, templated CHANGES.md 
structure.
   
   🧠 **New Feature in Public Preview:** You can now enable **Memory** to help 
**Gemini Code Assist** learn from your team's feedback. This makes future code 
reviews more consistent and personalized to your project's style. **Click 
[here](https://codeassist.google/code-review/login) to enable Memory in your 
admin console.**
   
   
   
   
   
   
   
   
   Using Gemini Code Assist
   
   
   The full guide for Gemini Code Assist can be found on our [documentation 
page](https://developers.google.com/gemini-code-assist/docs/review-github-code),
 here are some quick tips.
   
   Invoking Gemini
   
   You can request assistance from Gemini at any point by creating a comment 
using either `/gemini ` or `@gemini-code-assist `. 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](https://developers.google.com/gemini-code-assist/docs/customize-gemini-behavior-github).
   
   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 
:thumbsup: and :thumbsdown: 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](https://google.qualtrics.com/jfe/form/SV_2cyuGuTWsEw84yG).
   
   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](https://cloud.google.com/products/gemini/code-assist).
   
   
   
   
   
   [^1]: Review the [Privacy Notices](https://policies.google.com/privacy), 
[Generative AI Prohibited Use 
Policy](https://policies.google.com/terms/generative-ai/use-policy), [Terms of 
Service](https://policies.google.com/terms), and learn how to configure Gemini 
Code Assist in GitHub 
[here](https://developers.google.com/gemini-code-assist/docs/customize-gemini-behavior-github).
 Gemini can make mistakes, so double check it and [use code with 
caution](https://support.google.com/legal/answer/13505487).
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]