You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It was pointed out by @czubair that the releases for September were going into October's release notes yml files.
The problem is inside of the eng/pipelines/template/steps/generate-releasenotes.yml which is being used by the automation - azure-sdk - version-updater pipeline. The inline powershell script for the Set Release Period Value step sets the ReleaseStartDate to the second Friday of the month. In the case of September, 2023, the first Friday was September 1st and the second was September 8th which means everything after the 8th is being added to October's release yml. Release cycles run mid-month to mid month. So, the September release notes will include anything released 8/14-9/15, for example but because the second Friday was September 8th, it's putting everything released after the 8th into October's yml.
The text was updated successfully, but these errors were encountered:
It was pointed out by @czubair that the releases for September were going into October's release notes yml files.
The problem is inside of the eng/pipelines/template/steps/generate-releasenotes.yml which is being used by the automation - azure-sdk - version-updater pipeline. The inline powershell script for the Set Release Period Value step sets the ReleaseStartDate to the second Friday of the month. In the case of September, 2023, the first Friday was September 1st and the second was September 8th which means everything after the 8th is being added to October's release yml. Release cycles run mid-month to mid month. So, the September release notes will include anything released 8/14-9/15, for example but because the second Friday was September 8th, it's putting everything released after the 8th into October's yml.
The text was updated successfully, but these errors were encountered: