02:50:08 <m-relay> <j​pk68:matrix.org> Qt6 migration PR seems to be looking for reviews now (I'm sure people will have seen this anyways)
02:50:49 <m-relay> <j​pk68:matrix.org> It doesn't seem to compile for me... also, the use of `mmap` in the helper script could be a bit problematic
04:07:42 <m-relay> <o​frnxmr:xmr.mx> .. i doubt its going to get a proper review in its current form
04:09:03 <m-relay> <o​frnxmr:xmr.mx> Its like 100 messy commits and, just on the ci, there are a bunch of random changes, and capped off with a merge commit
04:09:52 <m-relay> <o​frnxmr:xmr.mx> Idk if this is majority AI development, or just messy.. (i havent looked in depth), but i dont like it
10:53:56 <tobtoht> yea this isn't going to get reviewed without passing CI
10:54:08 <tobtoht> getting builds working for all targets is most of the work for the migration
11:08:27 <tobtoht> it doesn't help that GUI build system is in a pretty abysmal state
11:09:39 <tobtoht> at this point migrating to Guix might make sense, since most of it can be copied from Feather
11:15:20 <tobtoht> might be possible to piggy back off Guix/depends scripts in the monero submodule (once the release branch has it) and just maintain a GUI specific manifest and extra depends package definitions in the GUI tree, rather than copying over everything
12:20:07 <plowsof> a Monero gui re-skin for feather is the only way (re-adding the freezing and delays like for like will be the hardest part)
12:20:41 <plowsof> otherwise the end user will notice something changed :P
14:13:35 <m-relay> <j​pk68:matrix.org> Yeah, probably the latter
14:15:50 <m-relay> <j​pk68:matrix.org> Has this been merged into master yet? Sorry for being out of the loop :P
14:58:05 <m-relay> <o​frnxmr:xmr.mx> Ya. Master uses guix
17:39:28 <m-relay> <j​pk68:matrix.org> Any idea when this will be merged into a release? I'm just catching up with the Gitian/Guix stuff now :)
21:58:04 <m-relay> <o​frnxmr:xmr.mx> when we create a new major version
22:04:38 <m-relay> <o​frnxmr:xmr.mx> There are some people who want to branch from master to create v0.19 asap (myself included), but it might not happen before fcmp hardfork
22:39:22 <m-relay> <j​pk68:matrix.org> So the first 0.19 release will be the same one that includes the FCMP++ logic?
22:40:01 <m-relay> <j​pk68:matrix.org> Or that's more around the time the hardfork is supposed to activate?
22:48:09 <m-relay> <o​frnxmr:xmr.mx> Possibly
22:48:23 <m-relay> <o​frnxmr:xmr.mx> depends if we branch "now" or if we wait for the hard fork
22:49:12 <m-relay> <j​pk68:matrix.org> Thanks, yes, I meant if we didn't :)