Daniel Sahlberg wrote on Mon, 18 Dec 2023 10:44 +00:00: > Den mån 18 dec. 2023 kl 09:40 skrev Daniel Shahaf <d...@daniel.shahaf.name>: >> To prevent recurrence, options include (1) make the cron job use the .py >> implementation; (2) add a regression test to backport_tests.py [sic] and >> then fix backport.pl's parsing. >> >> Glad to see backport.py being used :-) >> > > I'm considering to switch to backport.py after the release of 1.14.5 > (should be discussed on dev@ first of course) for the reasons mentioned in > the readme: "written in a language that many more active developers are > comfortable with"). If we could add the missing functions (Reviewing STATUS > and Adding new entries) or decide that those ore not needed anymore we > could then remove backport.pl and have one way of doing stuff.
And even if we don't implement F3 and F4 in backport.py, deploying the already-existing backport.py implementation of F1 in production would still be a step in the right direction. It's not clear to me whether F2 runs in production currently or not. Cheers, Daniel [Terms from backport.py: > F1. Auto-merge bot; the nightly svn-role commits. > F2. Conflicts detector bot; the svn-backport-conflicts-1.9.x buildbot task. > F3. Reviewing STATUS nominations and casting votes. > F4. Adding new entries to STATUS. ]
