| 16 Apr 2024 |
 kitsune | 0.9 development is happening real fast! | 17:41:01 |
 GitHub | 🔵 KitsuneRal opened a new PR quotient-im/libQuotient#742: "Forward-port 0.8.x fixes" with labels enhancement | 17:41:53 |
| GitHub | ☑ Workflow CI failed 😟 for quotient-im/libQuotient on branch dev
| 17:52:09 |
 nvrwhere | kitsune I was going to rip out the deprecated User stuff, just wanted to check that you hadn't started already | 18:28:35 |
| kitsune | I haven't, go ahead and do it :) | 18:51:48 |
| GitHub | ✳ KitsuneRal merged PR quotient-im/libQuotient#740: "Bump API version" | 19:08:48 |
| GitHub | ☑ Workflow CI failed 😟 for quotient-im/libQuotient on branch dev
| 19:32:28 |
| GitHub | 🔵 nvrWhere opened a new PR quotient-im/libQuotient#743: "Rip the Deprecated User Stuff" | 20:05:31 |
| GitHub | ☑ Workflow CI failed 😟 for quotient-im/libQuotient on branch nvrwhere/rip_user_room
| 20:35:04 |
| 17 Apr 2024 |
| GitHub | ✳ KitsuneRal merged PR quotient-im/libQuotient#742: "Forward-port 0.8.x fixes" | 05:35:53 |
| GitHub | ☑ Workflow CI failed 😟 for quotient-im/libQuotient on branch kitsune/up-compiler-versions
| 14:51:48 |
| GitHub | ☑ Workflow CI failed 😟 for quotient-im/libQuotient on branch kitsune/up-compiler-versions
| 14:56:02 |
| GitHub | ☑ Workflow CI failed 😟 for quotient-im/libQuotient on branch kitsune/up-compiler-versions
| 15:03:14 |
| GitHub | ☑ Workflow CI failed 😟 for quotient-im/libQuotient on branch kitsune/modernise-and-refresh
| 20:52:52 |
| 18 Apr 2024 |
| GitHub | ☑ Workflow CI failed 😟 for quotient-im/libQuotient on branch kitsune/modernise-and-refresh
| 05:19:37 |
| kitsune | I feel like these CI failure notifications are not really helping anything any more, at least for me; and they are not scalable, producing lots of spam when active work is happening (like here). Going to switch them off (PRs and issues will still be there). | 06:14:14 |
| kitsune | Is it still so wrong to commit what used to be treated as a fundamental sin in CMake and collapse the entire list of source files into a file(GLOB) invocation? | 14:08:00 |
| kitsune | (with CONFIGURE_DEPENDS passed to file(GLOB) of course) | 14:08:30 |
 Tobias Fella | my local cmake expert says "Don't" | 14:18:32 |
| kitsune | Alright, thanks for input... | 14:26:05 |
| GitHub | 🔵 KitsuneRal opened a new PR quotient-im/libQuotient#744: "Up requirements, modernize and refresh some code" with labels enhancement | 18:43:53 |
| GitHub | ✳ KitsuneRal merged PR quotient-im/libQuotient#743: "Rip the Deprecated User Stuff" | 19:27:07 |
| GitHub | ✅ TobiasFella approved quotient-im/libQuotient#744 "Up requirements, modernize and refresh some code" | 20:24:52 |
| 19 Apr 2024 |
| GitHub | ✳ KitsuneRal merged PR quotient-im/libQuotient#744: "Up requirements, modernize and refresh some code" | 06:49:15 |
| kitsune | Tobias Fella: I guess it's about a good time to merge or rebase the cross-signing PR - most of the things to be removed are removed by now. | 07:13:15 |
| Tobias Fella | rebased for now; I'm afraid it's not completely finished yet. BTW, you might want to have a look at how I'm (ab)using verification events to make in-room verification work, maybe you can come up with something better | 08:28:53 |
| 21 Apr 2024 |
|  Martix joined the room. | 19:44:49 |
| 22 Apr 2024 |
| kitsune | It looks like Omittable<> has run its course - with std::optional<> getting those monadic operations, and other differences being pretty negligible, there's not much reason to keep it around. I think of keeping it as an alias for now and deprecate later down the road, maybe after releasing 0.9.0. | 05:44:19 |
| GitHub | ⚪ KitsuneRal drafted a new PR quotient-im/libQuotient#745: "Deprecate Omittable and start switching to std::optional" with labels enhancement | 17:20:24 |
| 23 Apr 2024 |
| GitHub | 🔵 nvrWhere opened a new PR quotient-im/libQuotient#746: "Clean up the rest of the User stuff around connection" | 19:29:30 |
