5
$\begingroup$

What is the difference between Blender Version X.Y.0 and X.Y.1? For example, between Version 3.6 and 3.6.1.

Are these just bug fixes or something? Or are there some relatively significant changes?

There is no change in the wiki documentation or the manual (It just shows the changes for X.Y and not for X.Y.Z)

$\endgroup$
1
  • 4
    $\begingroup$ From my understanding in X.Y.Z, X=major_version, Y=minor_version, Z=patch_version where updates mostly are bug fixes, performance improvements, and fixes for issues found after the previous release. These updates usually don't introduce new features. $\endgroup$ Aug 17, 2023 at 8:41

2 Answers 2

6
$\begingroup$

I use Blender casually since about v2.69, and more actively v2.79 so I can't speak for the past and I think the versioning before v3.0 was largely inconsistent.

However Blender 3.0 switched to Semantic Versioning (source):

+-------MAJOR version when you make incompatible API changes
|
| +-----MINOR version when you add functionality in a backward compatible manner
| |
| | +---PATCH version when you make backward compatible bug fixes
| | |
| | |
X.Y.Z
3.0.1
3.1.0
3.1.1
3.6.0
3.6.2

Examples of X=MAJOR version changes:

  • 3.0.0 was a belated increment (because the new versioning scheme was just picked), as it reflects the huge changes in 2.80 (interface, switch from Blender Internal Renderer to Eevee), but also the rework of Geometry Nodes from named attributes in 2.92/2.93 to fields, files compressed in 3.0 not opening in previous versions (source), new add-on requirements (source), rewrite of Cycles: removing branched path tracing, cubic and gaussian subsurface scattering, CMJ sampling pattern, NLM denoiser (source), breaking python changes and Bendy Bones causing issues when opened in previous versions of Blender (source)
  • 4.0.0 is still developed, but looking at the αlpha version we can predict the mesh data will open only in 3.6 (which can be used to convert it to older versions), more breaking python changes, perhaps disappearance of face maps (replaced by attributes, but in face maps adding a face to one map automatically removed it from other maps), migration from vertex groups to attributes could also come with some backward compatibility problems…

Examples of Y=MINOR version changes:

  • 3.5.0 can stop a node from automatically reconnecting links if it's dropped on a link with ⎇ Alt key pressed (ALT is also useful to get the old behavior of swapping links when connecting a link to an already used input), Python BGL module no longer works with Metal (yes I know it's a breaking change), OSL can now be used with OptiX on the GPU, new Flip Quad Tessellation operator (related to my 2nd question on BSE) and many more
  • 3.6.0 introduces a "Simulation Zone" and "Index of Nearest" node and subtypes in group inputs in Goemetry Nodes, added 13 nodes to Viewport Compositor, and many more.

Examples of Z=PATCH version changes:

  • Blender 3.4.1 bug fixes (e.g. prevent UV Unwrap from packing hidden UV islands, stopping Animation in Some Scenes Immediately Crashes Blender)
  • Blender 3.5.1 bug fixes (e.g. Cycles shadow caustics not working with area lights, entering Grease Pencil Vertex Paint mode crashes)

Additionally:

  • once per year, a new version (after the X or Y increments) gets LTS (Long Term Support) status. It means this version will be patched (Z increments) even though newer MAJOR/MINOR (X,Y) versions exist (the newest of which also gets patches).
  • since it's an opensource project, a version can be accessed as soon as devs start working on it, it's marked as α - alpha version, and is not intended for serious use, because e.g. it may be missing features (e.g. in an attempt to migrate from vertex groups to attributes, devs may delete vertex groups first, and you may download that revision before they reintroduce old features with attributes)
  • Once a revision is complete, it is temporarily marked as β - beta, as the bugs are much more likely to appear in freshly coded features…
  • There are also experimental forks, which seems self-descriptive, various things are tried there, and eventually this code may be moved to the main branch.
$\endgroup$
5
  • 1
    $\begingroup$ "as it reflects the huge interface changes in 2.8" I know what you are referring to, but the questioner and future readers may not. This answer should make very clear that 2.80 was a major, breaking revision (until 2.79b the Blender Internal renderer was the default format, but its save files can't be opened in 2.80 onwards). $\endgroup$
    – Matthew
    Aug 17, 2023 at 19:45
  • 1
    $\begingroup$ Perhaps worth noting that it's version 2.80 (two point eighty), not 2.8 (two point eight), the zero is significant. $\endgroup$
    – Andrew T.
    Aug 18, 2023 at 4:08
  • 1
    $\begingroup$ @AndrewT. you're absolutely correct, and this kind of confusion was one of the reasons to change the old versioning scheme. $\endgroup$ Aug 18, 2023 at 8:57
  • 1
    $\begingroup$ @Matthew, I can agree that I didn't provide a lot of information more important than the one I decided to provide, but in the end of the day those were just examples, and I concentrated on versions 3.0.0 forward, as that's the beginning of the new versioning scheme. $\endgroup$ Aug 18, 2023 at 8:57
  • 2
    $\begingroup$ Thank you for taking the time to reply. Your reasons are sensible and I think the edit you made does help to alert other users to the issue. $\endgroup$
    – Matthew
    Aug 19, 2023 at 15:17
2
$\begingroup$

The difference between Blender version x.y.0 and x.y.1 is that the latter is a bugfix release of the former. It contains fixes for bugs that were found in the previous version.

Info Found Here: https://code.blender.org/2020/02/release-planning-2020-2025/#comment-114842

$\endgroup$
3
  • $\begingroup$ 3.6.2 which is available now also has changes which allow compatibility with the forthcoming 4.0. The weekly Blender Today Live video talks about the changes here. $\endgroup$
    – John Eason
    Aug 17, 2023 at 11:26
  • 1
    $\begingroup$ Can this be called a pre-bugfix? It fixes bugs that would happen in the future x) $\endgroup$
    – Lauloque
    Aug 18, 2023 at 16:15
  • $\begingroup$ I'm not sure. But this is what it means according to the source: X = Major Release Y = Addition Features within a Major Release Z = Bug Fixes within that Feature set $\endgroup$ Aug 19, 2023 at 8:06

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .