On Wed, 5 Feb 2025 at 21:05, Daniel Gustafsson <dan...@yesql.se> wrote: > For reference, you meant 53 right?
Yes, I meant 53 > If the > CFBot always need one in "Future" state we should document that to make sure > we > don't miss that going forward (and perhaps automate it to make sure we dont > make manual work for ourselves). Afaict it doesn't need at least one in the "Future" state, instead it needs one after the current[1] commitfest. I don't think it should rely on that though. So I created an issue to fix that[2]. It does seem silly that we require people to manually create new commitfests though, so I created an issue to track that[3] [1]: https://commitfest.postgresql.org/current/ [2]: https://github.com/macdice/cfbot/issues/22 [3]: https://github.com/postgres/pgcommitfest/issues/25
