| 29 Sep 2021 |
 jonringer | First order of business. Determing the release date. Generally it's pretty late in the release month, I'm going to toss out Nov 26th (a friday) as the initial target date, and create the timeline from there. That is a holiday in the US, so probably shoot for saturday as the expected release date. If we need to push the timeline (which usually happens because of hydra), then that monday also works :) | 23:57:00 |
| 30 Sep 2021 |
 nrdxp | I think Monday the 29th is a safe bet if we try to have everything ready by the Friday before 😅 | 00:02:12 |
| jonringer | Well, I would frame as, "try to do friday, but likely slip til monday". The main thing is aligning all of the previous staging-next cycles | 00:04:05 |
 tomberek | If there aren't any interactions with commercial entities that could be made difficult over Thanksgiving, it might even be easier. 26th Friday sounds good. | 13:28:21 |
| 1 Oct 2021 |
| tomberek | Looking at calendar we have -8 weeks tomorrow to warn for "Feature Freeze". | 03:30:35 |
| nrdxp | Alright sounds good. Jon, how did you approach this in the past? Should we reach out to codeowners individually or make announcements somewhere? | 03:50:54 |
| nrdxp | or both 🙂 | 03:51:04 |
| nrdxp | I'm assuming a milestone may also be in order | 03:53:17 |
| jonringer | I made an announcement, and cc'd a bunch of people | 06:01:12 |
| jonringer | example post: https://github.com/NixOS/nixpkgs/issues/121972 | 06:01:50 |
| jonringer | The main goal is to collect "what could possibly block a release, and is feasible in the current timeline". Don't be afraid to say that some change might be too much risk. | 06:06:10 |
| tomberek | is https://github.com/NixOS/nixpkgs/blob/master/.github/CODEOWNERS pretty reliable? | 06:13:24 |
| jonringer | that's where I did the initial list, and some people edited my post to add others | 06:39:55 |
| jonringer | * that's how I did the initial list, and some people edited my post to add others | 07:12:53 |
|  hexa joined the room. | 15:22:00 |
|  [0x4A6F] joined the room. | 15:29:16 |
|  lukegb (he/him) joined the room. | 15:39:34 |
| jonringer | nrdxp: tomberek : did you want me to c reate the release schedule. We are getting into that time frame where it's relevant. And for people working on staging (e.g. hexa ), it's good to starting aligning the staging cycles now | 16:04:01 |
| nrdxp | Do you mean a github project and feature freeze announcement? | 16:06:43 |
| nrdxp | I'll put up an announcement now | 16:11:52 |
| nrdxp | I'll basically copy what you did last cycle, discourse post linking to github issue | 16:13:39 |
| tomberek | i shared out a rough calendar with dates | 16:17:14 |
|  trofi joined the room. | 16:17:48 |
| nrdxp | I'm putting together a github issue right now | 16:19:12 |
| nrdxp | there doesn't seem to be a Gnome/GTK section in the codeowners file. Would @jtojnar still be the one to ping? | 16:29:11 |
| jonringer | In reply to @timdeh:matrix.org
Do you mean a github project and feature freeze announcement? For now, just a schedule on discourse, and a feature freeze on github | 16:35:41 |
| jonringer | a github project wouldn't be a bad idea though | 16:35:49 |
| nrdxp | hey tomberek, did you post that calendar on discourse? If not maybe you can now 🙏 | 16:36:25 |
| tomberek | no, that was just for us to come to a rough idea | 16:36:54 |
| jonringer | you can cc ryantm to pin stuff in discourse. :) | 16:36:58 |
