Browse Source
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-10458pull/11336/head
2 changed files with 23 additions and 2 deletions
Loading…
Reference in new issue