jellyfin/jellyfin.org
1
0
Fork 0
mirror of https://github.com/jellyfin/jellyfin.org.git synced 2026-09-03 04:20:03 +03:00
Code Issues Packages Projects Releases Wiki Activity

Josh's Section

Browse Source 
See team discussion
This commit is contained in:
Joe Kribs
2026-05-15 10:54:49 -06:00
committed by GitHub
parent be50a55dc0
commit b5cc954ce1
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
blog/2026/05-15-state-of-the-fin/index.mdx
+3 -1
View File
@@ -16,7 +16,7 @@ Welcome to the second edition of State of the Fin! This update will be slightly
#### Versioning
As mentioned in the last [State of the Fin](/blog/2026/01-06-state-of-the-fin/index.mdx#versioning), we're dropping the major version "10" from our naming scheme. With 10.11.x being the final release branch to use it, the next major release will move directly to 12.0.
As mentioned in the last [State of the Fin](/blog/2026/01-06-state-of-the-fin/index.mdx#versioning), we're dropping the major version "10" from our naming scheme. With 10.11.x being the final release branch to use it, the next major release will move directly to 12.0. The primary reason for this is to reduce confusion about what a "major" version is and eliminate the redundancy of a never-changing `10`. version prefix.
#### LLM/"AI" Policy
@@ -34,6 +34,8 @@ Please remember Jellyfin is open source and is written by volunteers. There are
If you'd like to get involved in helping fellow users, hang out in the [standard matrix/discord channels](/contact), or look at the [forums](https://forum.jellyfin.org/)/[subreddit](https://reddit.com/r/jellyfin) and volunteer answers when you think the question is something you know. Straight AI searching and copy-paste answering aren't good responses, but if it's something you have dealt with, please contribute! The more people who help answer the easy questions, the more we can allow the devs to work on the hard stuff.
And of course, if you want to contribute code, we welcome it! Bug fixes are always welcome as-is; but features require a bit more work and a policy that we are still in the process of defining. But if you want to work on a feature, the short answer is: please ask us before you start implementing it and work with the team on a full design/scope discussion to help ensure your work will be accepted!
## Development Updates
<ActivityChart />