< bitcoin-git>
bitcoin/master 49c6040 Hennadii Stepanov: qt: Use PeerTableModel::StatsRole
< bitcoin-git>
bitcoin/master b3e9bca Hennadii Stepanov: qt, refactor: Drop no longer used PeerTableModel::getNodeStats function
< aj>
MarcoFalke: (not sure if you're comment on the 22.0 schedule was related to mine; i just fixed the year from last year to this year, and made a joke about it still being last march)
< bitcoin-git>
[bitcoin] fanquake closed pull request #20849: net: disconnect peers by address without using a subnet (master...disconnect_by_subnet_fix) https://github.com/bitcoin/bitcoin/pull/20849
< MarcoFalke>
aj: Wasn't related. Just a comment on the schedule in general
< MarcoFalke>
Maybe I should bring it up in the meeting?
< wumpus>
in any csae, i've always based the schedule on the *real* release date (-final)
< wumpus>
normally i don't even post the schedule for the next release while the previous one is still open, but it was slipping too much and this at least gives some kind of time window
< wumpus>
it's likely that 22.0 will slip too by at least a month
< wumpus>
so i'm not sure how much it makes sense to plan more than one release ahead in the first place
< jonasschnelli>
agree
< MarcoFalke>
Whatever we do, it just seems suboptimal to do any kind of release process (branch-off, bugfixes, -final) during december
< MarcoFalke>
vasild: yes
< MarcoFalke>
vasild: Maybe I checked out the previous commit. Sorry, I destroyed the vm I was testing in. Will re-check
< MarcoFalke>
wumpus: It is not about aligning with ubuntu. It is more about picking months that don't collide with major holidays (like december or august)
< bitcoin-git>
[gui] hebasto closed pull request #174: refactor: No need to implement index for non-hierarchical models (master...210102-index) https://github.com/bitcoin-core/gui/pull/174
< wumpus>
MarcoFalke: Whatever we do, it just seems suboptimal to do any kind of release process (branch-off, bugfixes, -final) during december <- I agree with that and will take that into account for 0.23 planning, what I was doubtful about is whether that needs to affect the 0.22 schedule
< wumpus>
vasild: whoops
< MarcoFalke>
wumpus: Probably not affecting 22.0, but good to keep in mind for 23.0, thx