- add 6.0.x to release scheduler workflow
- upgrade Antora to 3.2.0-alpha.2
- remove Antora patch to support linked worktrees
- upgrade Antora Collector to latest alpha
- remove dispatch.sh script (handled by gh run workflow)
- consistently use gh run workflow to trigger workflows
- remove step to publish generated docs (no longer in use)
- upgrade Antora to 3.2.0-alpha.2
- remove Antora patch to support linked worktrees
- upgrade Antora Collector to latest alpha
- remove dispatch.sh script (handled by gh run workflow)
- consistently use gh run workflow to trigger workflows
- remove step to publish generated docs (no longer in use)
* remove unused workflows, scripts, and configuration (now handled by docs-build branch)
* upgrade Antora to 3.1 (and Node.js to 16)
* tune playbook settings
* reconfigure docs build for local build only
* add patch to support using linked worktree as Antora content source
* remove Antora extensions not needed for local builds
- set up placeholder and trigger for Deploy Docs workflow in docs-build branch
- set up placeholder and trigger for Rebuild Search Index workflow in docs-build branch
- remove obsolete Deploy Reference workflow
- upgrade Antora to 3.1
- reconfigure docs build for local build only
- add patch to support using linked worktree as Antora content source
- remove Antora extensions only needed for the production docs build
This step introduces the concept of a release train to determine the appropriate release dates and schedules milestones as needed. It uses the following rules:
- If the current SNAPSHOT version is a minor release (patchVersion == 0), checks to see if a GA release exists. If not, a release train is scheduled as follows:
- Finds the next available release train starting month (including this month), either January or July.
- Schedules a release train with M1, M2, M3, RC1 and GA versions on either January/February/March/April/May or July/August/September/October/November
- If the current SNAPSHOT version is a patch release (patchVersion != 0), checks to see if a GA release exists. If not, an individual milestone is scheduled on the next even month whose release day is in the future (can include this month).
- In either case, the release day used to schedule the release is based on the configured weekOfMonth (1-4) and dayOfWeek (1-5), e.g. 3rd Monday of the month (3, 1).
If a milestone already exists, nothing is created. Once created, milestone due dates can be updated manually as desired.
Closes gh-10458
Josh Cummings
jongwooo
Steve Riesenberg
Dan Allen
Marcus Da Coregio
Kirk Lin
Rob Winch
Steve Riesenberg
naveen