isapego commented on code in PR #5953:
URL: https://github.com/apache/ignite-3/pull/5953#discussion_r2120637879
##########
RELEASE.md:
##########
@@ -28,13 +28,20 @@ For all the commands going forward:
## Preparing the Release
1. Go to the project home folder.
-2. Create a Git tag:
+2. Update RELEASE_NOTES.txt with the changes since the last release. Commit
and push to the `main` branch.
+3. Update versions in `main` branch to the next development version (e.g.,
`x.y.z-SNAPSHOT`):
+ * Update `gradle.properties` manually.
+ * Run `./gradlew :platforms:updateVersion` to update platforms versions
(.NET, C++, Python, etc.)
+ * Commit and push changes.
+4. Create and push a new branch for the release `ignite-{version}`.
+5. Update versions in `ignite-{version}` branch to the current release
version, remove `-SNAPSHOT` suffix - same steps as in point 3.
+6. Create a Git tag from `ignite-{version}` branch head:
```
git tag -a {version}-rc{rc} -m "{version}-rc{rc}"
git push --tags
```
-3. Setup properties in gradle.properties.
- You can specify it in project gradle.properties but DO NOT FORGET to revert
it before push.
+7. Setup properties in `gradle.properties`.
+ You can specify it in project `gradle.properties` but DO NOT FORGET to
revert it before push.
Review Comment:
Can we somehow prevent accidental push of credentials here? Because I feel
like sooner or later this will happen if we don't have any utomatic mechanism
to prevent it.
--
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: notifications-unsubscr...@ignite.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
