I don't believe an exception is required. The assets to be released are cycle-with-intermediary and as such Ironic does not cut Release Candidate releases. Our drop dead absolute window for intermediary releases is R-1 per the release schedule[1]. If requirements.txt requires a change, then I believe that will require an explicit individual approval. For what it is worth, everyone's CI is in horrible shape this week. [0]: https://releases.openstack.org/reference/release_models.html#cycle-with-inte... [1]:https://releases.openstack.org/xena/schedule.html On Tue, Sep 21, 2021 at 8:25 AM Iury Gregory <iurygregory@gmail.com> wrote:
Hello everyone,
The ironic CI last week was in a very bad shape and we couldn't merge some patches that we wanted to have in the Xena release, we knew last week was the RC1 and we should have proposed the release for our derivables. Today we were able to merge a workaround to get our CI green again, we will probably have all the required patches merged by EOD or tomorrow morning. I would like to ask for an exception so we can release our deliverables tomorrow.
Thanks! -- Att[]'s Iury Gregory Melo Ferreira MSc in Computer Science at UFCG Part of the ironic-core and puppet-manager-core team in OpenStack Software Engineer at Red Hat Czech Social: https://www.linkedin.com/in/iurygregory E-mail: iurygregory@gmail.com