blender release tracking #7

Open
opened 2025-04-28 11:29:19 -04:00 by adam · 1 comment
Owner

blender updates break compatibility with old files. (Frustratingly, without telling you that's what the problem is.) Fortunately, as a 2-man team, it's easy to say "everyone ready to update, ready set GO!".

less easily, keeno got informed of an update (which he dutifully applied), and I seem to have not gotten that memo. (or dismissed it a while ago, who knows).

therefore: Need some way to know when to update blender. And apparently in-app notifications only have 50% reach.

blender updates break compatibility with old files. (Frustratingly, without telling you that's what the problem is.) Fortunately, as a 2-man team, it's easy to say "everyone ready to update, ready set GO!". less easily, keeno got informed of an update (which he dutifully applied), and I seem to have not gotten that memo. (or dismissed it a while ago, who knows). therefore: Need some way to know when to update blender. And apparently in-app notifications only have 50% reach.
adam self-assigned this 2025-04-28 11:29:19 -04:00
Author
Owner

the developers [say](https://developer.blender.org/docs/handbook/release_process/release_cycle/

A new Blender version is targeted to be released every 4 months. The actual release cycle for a specific release is longer, and overlaps the previous and next release cycle.

ambitious, yet realistic. a good policy to work under.
However, doesn't solve this issue.

they have a beautiful page detailing their release versions. It does not provide an RSS feed.

they appear to use an internal Gitea repo (as ever, developers of taste and distinction). however, the main Blender project does not use that "releases" infrastructure. (fair enough, i guess.. don't want to confuse non-nerds with a snapshot of source code when they want a compiled binary) They do, however, use Tags.

and therefore, https://github.com/go-gitea/gitea/pull/21696 - gitea, Great Thing as it is, will let you filter an RSS feed to tags.

4.4.0 tag was added on march 18th. blender release page confirms, that's when blender released 4.4.0.

🎉 we're in good shape, the data is there!

the developers [say](https://developer.blender.org/docs/handbook/release_process/release_cycle/ > A new Blender version is targeted to be released every 4 months. The actual release cycle for a specific release is longer, and overlaps the previous and next release cycle. ambitious, yet realistic. a good policy to work under. However, doesn't solve this issue. they have [a beautiful page](https://www.blender.org/download/releases/) detailing their release versions. It does not provide an RSS feed. they appear to use [an internal Gitea repo](https://projects.blender.org/blender/blender) (as ever, developers of taste and distinction). however, the main Blender project does not use that "releases" infrastructure. (fair enough, i guess.. don't want to confuse non-nerds with a snapshot of source code when they want a compiled binary) They do, however, use Tags. and therefore, https://github.com/go-gitea/gitea/pull/21696 - gitea, Great Thing as it is, will let you filter an RSS feed to tags. 4.4.0 tag was added on march 18th. blender release page confirms, that's when blender released 4.4.0. 🎉 we're in good shape, the data is there!
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: beefhavers/_meta#7
No description provided.