[02:30] *** nine left
[02:35] *** nine joined
[05:35] *** hurufu joined
[05:37] *** hurufu left
[05:38] *** hurufu joined
[07:00] <releasable6> Next release in ≈2 days and ≈11 hours. There are no known blockers. Please log your changes in the ChangeLog: https://github.com/rakudo/rakudo/wiki/ChangeLog-Draft

[10:25] *** hurufu left
[10:25] *** hurufu joined
[12:40] *** hurufu left
[13:29] *** hurufu joined
[16:46] *** Geth joined
[17:12] <[Coke]> team - please start work to find another release manager. Having a single point of failure here (with jdv on hiatus) is dangerous.

[17:20] <[Coke]> just so we're clear: NO MORE COMMITS ON MAIN UNTIL POST RELEASE WITHOUT CHECKING WITH THE RELEASE MANAGER for MoarVM, NQP, and rakudo. Cheers.

[17:20] <[Coke]> even if you think they're perfectly safe.

[17:20] <[Coke]> I am happy to discuss a different approach, but I know there's been resistance to having commits go to branches first as a default approach.

[17:25] <ugexe> one method is a release branch is branched off main and that gets used to do the release, and which is ultimately merged back into main after the release. although having to do so across three repos does make that a less appealing option

[17:25] <[Coke]> I'm also not sure it makes sense to do monthly releases in perpetuity.

[17:26] <[Coke]> ugexe: There are basically 2 users in that situation, the devs working on something, and the release manager trying to test and construct the release.

[17:27] <[Coke]> it does not seem that much more complicated for the release manager than the current byzantine setup that already needs 3 repos.

[17:27] <timo> do you think we should consider a "megarepo"?

[17:28] <timo> or is it "monorepo"?

[17:28] <[Coke]> we have different licenses/copyrights, so I would hesitate from that standpoint

[17:29] <timo> oh, and different requirements to contribute too

[17:29] <timo> makes sense

[19:27] *** hurufu left
[21:13] <[Coke]> verified jdv will eventually come back, but that's a few months out.

[21:18] <patrickb> I'm willing to do releases. But currently lacking tuits. This will change in a month or two (at least I dearly hope so).