Replies: 6 comments 6 replies
-
|
We took again way too long to release it. I don't see 4.0.0 being any better though. |
Beta Was this translation helpful? Give feedback.
-
|
Broken links: I did check it locally and it didn't give any issues. However I don't believe this. Likely there's a "recursive" flag that should be added to the docs. |
Beta Was this translation helpful? Give feedback.
-
I believe sourceforge has a download counter. As it should be automatically updated in 99% of the cases via webhook it should be fine. We may need to set the correct latest release though- especially as I deleted the first failed try SourceForge may have gotten confused. CC @gilgongo |
Beta Was this translation helpful? Give feedback.
-
|
Translation contributors
It got way more difficult once we moved to weblate. We should have one responsible person for each language. And this person should be in the script and approve the respective PR. I believe the script is outdated -> let translators re confirm their commitment. Otherwise remove them from the script and open an issue that the language is unsupervised. |
Beta Was this translation helpful? Give feedback.
-
|
Checkkeys: Skimmed over it but didn't do an in depth check. As it's hard to find real clashes we may need to find a way to do this differently. CC: @softins |
Beta Was this translation helpful? Give feedback.
-
|
Hi guys, seems I missed the fact there was a new screenshot needed for the website, MIDI Control settings. |
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I went through the 3.12.0 release process and grabbed most of the points that hadn't been closed off for this, as a starting point. I've also added my comments in.
We managed without one.
I'm not clear what the process is: even if it's through Weblate, I don't know enough about it.
Postponed to fix post-release?
Maybe we can get a workflow that will do this? Build, deploy and start up the website in a container, then run the link check against it, taking down the website container when complete.
Tried from 3.12.0rc1 and didn't get a notification. Tried again from 3.11.0 and did get the notification. Bug raised. (Yes, it does say
but we should still notify older intermediate releases).
Do we have any tracking of SourceForge traffic? (This hasn't been done yet.)
Well, I did update2 - I'll send an email as well.
I did a few as we went along. We probably should review it, though.
Hence this post.
Beta Was this translation helpful? Give feedback.
All reactions