MONGOID-5908 Run upcoming Ruby and Rails builds on a bi-weekly schedule

[comandeo-mongo]

Runs the master branch test suite against the upcoming, in-development Ruby (ruby-dev) and Rails (master) versions on a regular schedule, so incompatibilities with the next releases are caught before they ship.

The ruby-dev and rails-master build variants already existed and already run off-PR (they are not tagged pr, so they only run on the master waterfall). This change adds the bi-weekly cadence and documents the setup.

Changes

CI config (Evergreen)

• .evergreen/config/variants.yml.erb — add batchtime: 20160 (14 days) to the test task of both the ruby-dev and rails-master variants, so each activates at most once every two weeks; add explanatory comments.
• .evergreen/config.yml — regenerated from the template (do not edit by hand).

Docs

• .evergreen/README.md (new) — documents the scheduled upcoming-version builds and the step-by-step Evergreen project-notification setup that opens a MONGOID Jira issue on failure (Evergreen fills in version, commit hash, and failing tasks).

Failure-to-Jira is an Evergreen project notification configured once in the UI, not something expressible in config.yml; the README records how to set it up.

Test plan

• ruby .evergreen/update-evergreen-configs regenerates config.yml cleanly.
• Verified batchtime: 20160 appears on both variant tasks in the generated config.yml.

CI-config/docs-only change; no runtime code paths, so no new specs.

Jira: https://jira.mongodb.org/browse/MONGOID-5908

[Copilot]

Pull request overview

Adds a bi-weekly cadence for Evergreen’s “upcoming” Ruby and Rails build variants so master-branch incompatibilities can be detected proactively, and documents the operational notification setup.

Changes:

• Adds batchtime: 20160 (14 days) to the test task for ruby-dev and rails-master build variants in the Evergreen variants template.
• Regenerates .evergreen/config.yml from templates to reflect the scheduling change.
• Adds .evergreen/README.md documenting the scheduled builds and Evergreen → Jira failure notification setup.

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
.evergreen/README.md	Documents scheduled ruby-dev / rails-master runs and the one-time Evergreen notification configuration to create Jira issues on failures.
.evergreen/config/variants.yml.erb	Adds a 14-day batchtime to throttle ruby-dev and rails-master runs and adds explanatory comments.
.evergreen/config.yml	Regenerated Evergreen configuration reflecting the new batchtime settings and comments.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.