The release schedule on "whattrainisitnow" is maintained by relman and is accessible via an API. Instead of manually looking up these dates and hard-coding them into Shipit, I propose querying this API. This automation will not only ensure consistency between "whattrainisitnow" and Shipit but will also reduce the need for manual updates and deployments related to these dates.
Implementing these changes will help the progress of issue #1418.
This issue pertains to the merge duty step outlined here.
Currently, we manually retrieve the LAST and NEXT known dates from the "whattrainisitnow" service and hard-code them into our configuration file:
https://github.com/mozilla-releng/shipit/blob/01cc5f56a9121052377a0f0c7c9839492a50224b/api/src/shipit_api/common/config.py#L57-L65
The release schedule on "whattrainisitnow" is maintained by relman and is accessible via an API. Instead of manually looking up these dates and hard-coding them into Shipit, I propose querying this API. This automation will not only ensure consistency between "whattrainisitnow" and Shipit but will also reduce the need for manual updates and deployments related to these dates.
Implementing these changes will help the progress of issue #1418.