Newest at the top
| 2026-04-02 21:16:12 +0200 | <Athas> | I have heard that some released software has bugs, so maybe fixing them all is not necessary before tagging a release. |
| 2026-04-02 21:15:52 +0200 | <tomsmeding> | (There's probably more!) |
| 2026-04-02 21:15:43 +0200 | <tomsmeding> | also fixing all the bugs in the GPU backend. That took us a year or so |
| 2026-04-02 21:15:27 +0200 | <tomsmeding> | Athas: kinda yes, but also what's mostly slow is getting everyone to respond to an email. |
| 2026-04-02 21:15:00 +0200 | <tomsmeding> | davean: I something in an area that could involve Accelerate, but likely will not for practical reasons |
| 2026-04-02 21:14:20 +0200 | <Athas> | Also, Accelerate comprises many packages, so release engineering is harder than a tag (I suppose). |
| 2026-04-02 21:14:19 +0200 | <tomsmeding> | currently forming is a new category containing 1 person who is not moving on and yet not a PhD student any more. We'll see how that category develops |
| 2026-04-02 21:14:10 +0200 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-04-02 21:14:05 +0200 | <EvanR> | someone write "AI" somewhere on accelerate to get more funding and support |
| 2026-04-02 21:14:03 +0200 | <davean> | Well what is your postdoc? |
| 2026-04-02 21:13:32 +0200 | <tomsmeding> | I wasn't even officially connected to accelerate, really, but I dragged myself into it (for better or for worse), and am now transitioning from 3 to 1 |
| 2026-04-02 21:12:52 +0200 | <tomsmeding> | davean: the people "connected" with accelerate fall into 3 categories: 1. moved on (other job, other interests, etc.); 2. is a full professor and is busy; 3. is a PhD student and is busy |
| 2026-04-02 21:12:47 +0200 | wootehfoot | (~wootehfoo@user/wootehfoot) wootehfoot |
| 2026-04-02 21:12:30 +0200 | ss4 | (~wootehfoo@user/wootehfoot) (Remote host closed the connection) |
| 2026-04-02 21:12:27 +0200 | ss4 | (~wootehfoo@user/wootehfoot) wootehfoot |
| 2026-04-02 21:11:19 +0200 | <davean> | tomsmeding: haha, why has it failed to get updates? Its lack of maintanership really hurts it. |
| 2026-04-02 21:11:02 +0200 | <tomsmeding> | At least, Ivo's intent is to have a release earlier than five years from now, but then, previously there was also an intent. |
| 2026-04-02 21:09:08 +0200 | <Athas> | A productive end. |
| 2026-04-02 21:05:54 +0200 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds) |
| 2026-04-02 21:05:35 +0200 | <tomsmeding> | This was my last act of vengeance here in Utrecht before I leave for a postdoc :) |
| 2026-04-02 21:05:02 +0200 | <tomsmeding> | I hope not, but that's out of my hands :) |
| 2026-04-02 21:04:50 +0200 | <tomsmeding> | I don't know! |
| 2026-04-02 21:04:11 +0200 | <Athas> | tomsmeding: will it be five years untli the next update? |
| 2026-04-02 21:03:24 +0200 | arandombit | (~arandombi@user/arandombit) arandombit |
| 2026-04-02 21:03:24 +0200 | arandombit | (~arandombi@2a02:2455:8656:7100:a19d:edd6:ba09:3a91) (Changing host) |
| 2026-04-02 21:03:24 +0200 | arandombit | (~arandombi@2a02:2455:8656:7100:a19d:edd6:ba09:3a91) |
| 2026-04-02 20:59:05 +0200 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-04-02 20:57:07 +0200 | tessier | (~tessier@ec2-184-72-149-67.compute-1.amazonaws.com) (Ping timeout: 276 seconds) |
| 2026-04-02 20:55:28 +0200 | tessier_ | (~tessier@ip68-8-117-219.sd.sd.cox.net) tessier |
| 2026-04-02 20:54:14 +0200 | Pozyomka | (~pyon@user/pyon) pyon |
| 2026-04-02 20:50:26 +0200 | alter2000 | (~alter2000@user/alter2000) alter2000 |
| 2026-04-02 20:48:50 +0200 | alter2000 | (~alter2000@user/alter2000) (Ping timeout: 248 seconds) |
| 2026-04-02 20:48:18 +0200 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 248 seconds) |
| 2026-04-02 20:43:41 +0200 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) merijn |
| 2026-04-02 20:33:13 +0200 | arandombit | (~arandombi@user/arandombit) (Ping timeout: 248 seconds) |
| 2026-04-02 20:32:23 +0200 | somemathguy | (~somemathg@user/somemathguy) (Quit: WeeChat 4.1.1) |
| 2026-04-02 20:26:25 +0200 | Pozyomka | (~pyon@user/pyon) (Ping timeout: 245 seconds) |
| 2026-04-02 20:19:40 +0200 | ChanServ | +v haskellbridge |
| 2026-04-02 20:19:40 +0200 | haskellbridge | (~hackager@96.28.224.214) hackager |
| 2026-04-02 20:16:35 +0200 | <tomsmeding> | Athas: that seems to be blocked only on a bounds bump in linear-accelerate; I've pinged the maintainer. :) |
| 2026-04-02 20:14:44 +0200 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) (Client Quit) |
| 2026-04-02 20:14:18 +0200 | haskellbridge | (~hackager@96.28.224.214) (Read error: Connection reset by peer) |
| 2026-04-02 20:14:18 +0200 | target_i | (~target_i@user/target-i/x-6023099) target_i |
| 2026-04-02 20:13:18 +0200 | target_i | (~target_i@user/target-i/x-6023099) (Ping timeout: 246 seconds) |
| 2026-04-02 20:13:01 +0200 | <[exa]> | tomsmeding: cooooooool |
| 2026-04-02 20:12:37 +0200 | merijn | (~merijn@host-cl.cgnat-g.v4.dfn.nl) (Ping timeout: 265 seconds) |
| 2026-04-02 20:11:10 +0200 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) humasect |
| 2026-04-02 20:10:03 +0200 | <haskellbridge> | <sm> I've never used it, but that sounds like an excellent update |
| 2026-04-02 20:08:58 +0200 | target_i | (~target_i@user/target-i/x-6023099) target_i |
| 2026-04-02 20:08:18 +0200 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) (Remote host closed the connection) |