-
selstajeffro256: do you think 9135 will be ready for the next release? or will it require more work?
-
m-relay<jeffro256:monero.social> I think it's good as-is. I might push more tests, but that's it
-
m-relay<jeffro256:monero.social> But it *should* be ready for next release
-
selstaok! i'm running it locally currently
-
m-relay<jeffro256:monero.social> Awesome !
-
m-relay<jeffro256:monero.social> me too
-
m-relay<jeffro256:monero.social> any issues thus far ?
-
selstanot yet
-
selstai'm just a bit worried since it's a large change that can cause subtle bugs
-
m-relay<jeffro256:monero.social> me too...
-
m-relay<jeffro256:monero.social> it would be nice to get at least 1 other reviewer
-
selstajeffro256: i thought about it again, i would prefer to make a release now and then include 9135 in a follow up release as soon as it's well tested
-
m-relay<jeffro256:monero.social> That's fine by me
-
selstai've been delaying this release for too long now
-
m-relay<jeffro256:monero.social> What're going to be the big changes for this release?
-
selstamain reason I want to put out the release is for macOS RandomX fix
-
selsta.merges
-
xmr-pr8940 9130 9136
-
gingeropolousi guess i can try running 9135 on top of release. master is giving me random systemd initiated restarts
-
selsta.merge+ 9159 9158 9156 9155 9145 9143 9137 9136 9130 9128 9125 9121 9006 9008 9005 9004
-
selsta.merges
-
xmr-pr8940 9004 9005 9006 9008 9121 9125 9128 9130 9136 9137 9143 9145 9155 9156 9158 9159
-
gingeropolouswe're gonna do 9130 without a hf? i guess the differences between old and new wallets won't be too drastic
-
gingeropolouswell i guess a hf wouldn't really do it, because a non-upgraded wallet could still connect to a new node. is there tx version relay rules.....