Teeworlds - development

[teeworlds/teeworlds] Pull request opened: #3188 Refresh ServerBrowser using F5

Went through the issues and saw this low-hanging fruit; should resolve #2421. The issue also mentions controller/tabbing navigation. That's a task with lots of design questions though, I'd split that into a separate item once this is integrated.

Hope me just picking an issue at random and working on it is alright.

the PR looks good to me

17:13

unfortunately, development has pretty much stalled, you might not see an answer from Oy in months

1

Ah, sad to hear. Already gathered as much, so I'm fine with that. Figured I'll just contribute something, even if it takes months or years to hear back.

Yeah

ViMaSter

Hope me just picking an issue at random and working on it is alright.

It's a good approach imo

Was wondering if automating the releases could help. I work in DevOps for a living, but not sure how to best approach that, given most (if not all of it) is done by hand atm and I'm not sure if that's even wanted

We already have CI and automated trunk zips

So I figured "another button mapping, that's doable!"

(edited)

17:23

Only for dev builds though, right?

Yeah but there isn't much point in randomly doing releases that tweaked a couple things in the engine and the UI

17:24

Actually crafting the release isn't nearly as much work as all the media stuff around it

all the media stuff around it

Such as?

ViMaSter

all the media stuff around it

Such as?

https://teeworlds.com/?page=journal

Hm. Could set up a system that skims the GitHub Issues that were addressed between the last and next release and generate patch notes based on that, if we add a "what does this issue mean for players?"-section to them.

17:28

No idea what kinda CMS that's using though, the website isn't on GitHub I guess?

punbb

18:22

with some blogging extension, i guess (edited)

18:23

it might make sense to create some summary for github releases that can be copy & pasted into a new blog post. it's pointless to automate it completely. (edited)

alternatively populate the GH releases via a pipeline and just have the website mirror it? that way if there's things like typos or updated binaries for some reason, they'd automatically propagate to the website

ViMaSter

Hm. Could set up a system that skims the GitHub Issues that were addressed between the last and next release and generate patch notes based on that, if we add a "what does this issue mean for players?"-section to them.

We already pretty much do that, categorize and try to find the most meaningful issues from a player perspective, and have some nice new stuff to advertise with screenshots etc.

ViMaSter

alternatively populate the GH releases via a pipeline and just have the website mirror it? that way if there's things like typos or updated binaries for some reason, they'd automatically propagate to the website

We had that awhile ago

18:45

Getting releases done, even considering that, isn't that much effort. I could craft one for tonight if we wanted to. Releases are rather conditioned by either getting enough interesting features or a security release

18:45

All past releases were triggered by this afaik

18:46

We lack both an active maintainer and enough content, and the two are in a bit of a negative loop