Update the release schedule in the release protocol after release v1.23

[mazursasha1990]

In this PR the section Release Schedule in the Release Protocol was updated after release v1.23.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[barecheck]

React App | Jest test suite - Code coverage report

Total: 26.41%

Your code coverage diff: 0.00% ▴

✅ All code changes are covered

[coderabbitai]

Walkthrough

The RELEASE-PROTOCOL.md document has been updated to include new release versions, specifically v1.24.0 and v1.25.0, along with their respective release and code freeze dates. The section on "Requirements and key results" has been expanded to provide clearer objectives for the Software Development Life Cycle (SDLC). Other sections, including "Environments," "Versioning," and "Git branches and tags," remain unchanged, while the overall structure and protocols for development and release have been preserved.

Changes

File Path	Change Summary
doc/release/RELEASE-PROTOCOL.md	- Added v1.24.0 with release date November 16, 2024 and code freeze date November 12, 2024.
	- Added v1.25.0 with release date November 30, 2024 and code freeze date November 26, 2024.
	- Expanded "Requirements and key results" section to clarify SDLC objectives and key results.

Possibly related PRs

• Updated RELEASE-NOTES.md file for 1.24 version #396: The changes in this PR involve the addition of release notes for version 1.24.0, which directly corresponds to the new entry added in the main PR's release schedule for the same version.

Suggested reviewers

• roman-stolar
• Innavin369
• VadimKovalenkoSNF

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 9835463 and 7c9d079.

📒 Files selected for processing (1)

• doc/release/RELEASE-PROTOCOL.md (1 hunks)

🔇 Additional comments (1)

doc/release/RELEASE-PROTOCOL.md (1)

49-50: LGTM! Release schedule updates are consistent and well-formatted.

The new entries maintain the established two-week release cadence and follow the standard 4-day code freeze window before each release.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[barecheck]

Dedupe Hub App | Unittest test suite - Code coverage report

Total: 56.14%

Your code coverage diff: 0.00% ▴

✅ All code changes are covered

[barecheck]

Countries App | Unittest test suite - Code coverage report

Total: 100%

Your code coverage diff: 0.00% ▴

✅ All code changes are covered

[barecheck]

Contricleaner App | Unittest test suite - Code coverage report

Total: 98.91%

Your code coverage diff: 0.00% ▴

✅ All code changes are covered

[barecheck]

Django App | Unittest test suite - Code coverage report

Total: 77.91%

Your code coverage diff: 0.00% ▴

✅ All code changes are covered