| 17 Jan 2023 |
|  void joined the room. | 17:07:04 |
| void | golang heights | 17:08:04 |
 @qbit:tapenet.org | such great heights? | 19:18:46 |
|  zamicol joined the room. | 20:09:38 |
|  pinpox joined the room. | 20:17:30 |
| 18 Jan 2023 |
|  [a4]nd[e3]r[s5][o0]n joined the room. | 08:29:00 |
| @qbit:tapenet.org | hola! | 15:06:20 |
|  hexa joined the room. | 15:11:14 |
| hexa | qbit: are you aware of the go release schedule? | 15:11:35 |
| @qbit:tapenet.org | relatively - every 6ish months | 15:12:35 |
| hexa | tl;dr: last two releases supported, two releases per year, next release in 1-2 months | 15:12:39 |
| hexa | https://endoflife.date/go | 15:12:41 |
| hexa | we need 1.20 for the nixos 23.05 release | 15:12:57 |
| hexa | as to not be stuck on 1.19 when it goes eol during 23.05s lifecycle | 15:13:17 |
| @qbit:tapenet.org | makes sense | 15:13:32 |
| hexa | just want to make sure someone is aware, because during the last releases go maintenance was always a bit behind | 15:14:06 |
| hexa | and needed to be pushed | 15:14:15 |
