25.11 release annoucement

[jopejoe1]

Currently the logo is a draft as we wait for the finished version!

[github-actions]

🚀 Deployed on https://692c7bdd556ae7d968645b7d--nixos-homepage.netlify.app

[github-actions]

🚀 Deployed on https://692c7dfee33d1dee87f89ce2--nixos-homepage.netlify.app

[github-actions]

🚀 Deployed on https://692c80f841b519f454515677--nixos-homepage.netlify.app

[thilobillerbeck]

I'd kindly ask you to at least wait for one of the marketing team mebers to review a PR

[wolfgangwalther]

What does the marketing team have to do with the release? I don't get it.

[thilobillerbeck]

Nothing, but we maintain this repo and especially if something breaks, we are the ones who will be addressed. This is why we usually want to review PRs by ourselves as well.

[wolfgangwalther]

OK, but if the expectation is that a marketing team member reviews this kind of PR - then the release team doesn't need write permissions at all, right? Because the marketing team could then merge it as well.

So why does the release team have write permissions? Is it not exactly because of publishing the release announcement in a timely manner?

Either they have these privileges for something else and were overstepping, or they have these privileges for exactly this scenario and your request is invalid.

[mweinelt]

Availability of marketing did vary over the years, so I think that is why release team got write access eventually.

[thilobillerbeck]

OK, but if the expectation is that a marketing team member reviews this kind of PR - then the release team doesn't need write permissions at all, right? Because the marketing team could then merge it as well.

what @mweinelt says. If something goes terribly wrong in terms of lack of administration, then people can act (especially since we are pretty small).

So why does the release team have write permissions? Is it not exactly because of publishing the release announcement in a timely manner?

In a perfect world we would have had some time before the release to review. I guess noone knew that I kept track of Github the whole day and I also heard there was kind of a hurry this time. So I guess there was some messed up communication.

Either they have these privileges for something else and were overstepping, or they have these privileges for exactly this scenario and your request is invalid.

I don't want to have a pretty high bus factor in this repository, but a one hour time frame does not leave any breathing room for reaction, though as stated above, I kind of get why this needed to happen.

Sorry if I my initial comment sounded a bit harsh.

[leona-ya]

In this case, I planned to do a draft PR a few days back for the marketing team to review it. Due to unexpected, acute personal problems I didn't have time and capacity for that, I'm sorry.

Also, for the same reasons I have not the mind capacity to make this better for that I'm also sorry. (and btw I'm also relatively unavailable for the project in the next days)

[thilobillerbeck]

In this case, I planned to do a draft PR a few days back for the marketing team to review it. Due to unexpected, acute personal problems I didn't have time and capacity for that, I'm sorry.

Absolutely understandable. I hope your problem got resolved. Take care. :)