Add stability section to README files

[koriym]

Added a new section detailing the stability of Ray.Aop in both README.ja.md and README.md. The section explains the project's adherence to semantic versioning and its commitment to maintaining backward compatibility since version 2.0.

Summary by CodeRabbit

• Documentation
  • Added a new "Stability" section to both README.md and README.ja.md, highlighting adherence to semantic versioning and commitment to backward compatibility since 2015.

[coderabbitai]

Walkthrough

The changes involve updates to two README files, README.ja.md and README.md, where a new section titled "Stability" has been added. This section details the package's adherence to semantic versioning and its commitment to backward compatibility since version 2.0, released in 2015. The updates emphasize the ongoing maintenance of stability in future releases, with no other modifications made to the existing content or structure.

Changes

File	Change Summary
README.ja.md	Added new section "安定性" (Stability) outlining semantic versioning and backward compatibility since version 2.0.
README.md	Added new section "Stability" emphasizing semantic versioning and backward compatibility since version 2.0.

Poem

In the meadow where bunnies play,
Stability shines bright as day.
With versions that hold true and fast,
Our code will thrive, built to last.
Hop along, dear friends, rejoice,
In every line, let's raise our voice! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 4536d0e and 99a72d8.

📒 Files selected for processing (2)

• README.ja.md (1 hunks)
• README.md (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• README.md

🔇 Additional comments (2)

README.ja.md (2)

229-231: LGTM! Clear and informative stability section.

The new stability section effectively communicates the project's commitment to:

• Semantic versioning
• Backward compatibility since v2.0 (2015)
• Ongoing stability maintenance

---

232-234: LGTM! Proper markdown formatting.

The horizontal rule and spacing around the new section maintain consistent document formatting.

---

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (2.x@4536d0e). Learn more about missing BASE report.
Report is 2 commits behind head on 2.x.

Additional details and impacted files

@@           Coverage Diff           @@
##             2.x      #226   +/-   ##
=======================================
  Coverage       ?   100.00%           
  Complexity     ?       225           
=======================================
  Files          ?        28           
  Lines          ?       583           
  Branches       ?         0           
=======================================
  Hits           ?       583           
  Misses         ?         0           
  Partials       ?         0           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.