Den ons 20 nov. 2024 kl 18:15 skrev Daniel Sahlberg < daniel.l.sahlb...@gmail.com>:
> So I'd say we have consensus on moving to the Python implementation - > several +1 and no-one objecting. And since this is far from core code and > it can easily be reverted I don't see a problem at all. > I've been working on this today: - svn-qavm has a local WC from /trunk (/home/svnsvn/src/svn/trunk) which is frozen in time. It used to be r1914207, I've updated to r1922008. (The reason to be frozen in time is to prevent someone with write access to the repository from committing code to the script which would then be executed on svn-qavm if the script is updated automatically. Now it require a separate pair of eyes before executing). - The backport r1922009 (see commits@) was done by merge-approved-backports.py, however I executed the script manually. - The backport is done via a cronjob (executing 04:00 UTC). The cronjobs are controlled by a Puppet configuration in https://github.com/apache/infrastructure-p6 (login with an ASF account required). I've committed an update and created a pull request update the cronjobs on the actual machine. - As soon as Infra has merged the crontab update, I'm going to update puppet. To test things I'm probably going to edit the crontab manually to make it run more often than normal, to get r1922010 merged today, while I'm having a bit of time to watch it. - I'll then revert to normal schedule, approve r1921266 and wait for it to be merged normally tomorrow morning. As I said before, I'd like to do a release of 1.14.5 when all this is done. I will be a bit overloaded for the next two weeks, but I plan to start the release process beginning of December. If anyone would like to include something else in the release, now is the time to nominate. Kind regards, Daniel
