What should we run to test on devnet right now?

[LionelTrichet]

Hi all,

We run a mainnet validator and two stock nodes, and a node on devnet that we use for testing the lending amendments. Question is about the devnet one.

Devnet is on 3.4.1 and has fixBatchV1_2 enabled. Our node can't join it: 3.3.0 doesn't know that amendment, so it never gets a validated ledger and just loops on wrongLedger. 3.4.0 wouldn't help — the amendment isn't in that tag, or in develop, or in any open PR. (Our servers only had the id; XRPScan names it fixBatchV1_2 and marks it as introduced in 3.4.1, and the hash of that name matches the id exactly.)

The apt repo has stable 3.3.0-1 and unstable 3.4.0~rc1-1, so there's nothing there to install either.

So: what are operators meant to run to test against devnet at the moment? Is there a branch or tag we should be building, or is the answer simply to wait for 3.4.1?

Same question matters for mainnet, where the amendment reaches its two weeks on 9 October.
And a related one, since roughly a third of our peers were already running 3.4.1 before any of it was public. If builds reach some operators ahead of publication, is there a way for the rest of us to be in that loop — a list to join, or criteria to meet? We're not on a default UNL, and if that's the bar then fair enough, but if there's a path we're supposed to follow, we'd like to follow it. Our xrp-ledger.toml publishes an operator contact, and we've subscribed to the ripple-server group.

[mvadari]

Packages for 3.4.1 have been released.