Hello, I don't want to participate in this thread right now, but I just want to propose a different view of the topic
> We don't know what ftpmaster think should happen next since they > haven't said. There is no indication that ftpmaster will start the > implementation work, nor that they are prepared to proceed without it. The months before a stable release pose a really high pressure on ftpmasters workload, as well as nobody wants to break dak when the freeze is approaching. So for this reason I think implementing this change after trixie release would be a "safer" option. I know this isn't a good answer, and not an excuse, but sometime we should also try to think what are the consequences of some actions in the release schedule. Freezes are annoying for everybody, keeping the freeze timeline shorter as possible is something many people wants, as well as the ability to use sid as they want, transition packages and upload new releases. So, in case of a bad implementation on ftpmaster side, also Release Team will need to delay the release process, and this is really not ideal. There is also a bug related to adding loong64 to the archive, and I guess the missing progress has a similar answer https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1089009 But nobody should add pressure *right now* to FTP/DSA/RT Teams, and let them finish the release job. I know after a lot of development, watching the result of the job not being live due to missing work on somebody else hands is... sad... Just my .02$
