My understanding is vague in relation to the blender release cycles - is 2.69 the final stable release for this series, or will 2.70 be the last version of the 2.6 cycle? I wouldn’t want to download 2.69 only to find an updated, more stable instance a couple weeks later.
This is a good question. I don’t think it has been 100% decided yet. It seems there will still be bug fix releases for 2.69 even after 2.7x starts. I don’t know for certain though. You can read it here:
But, it should be said that 2.69 is quite stable. It is a pleasant release. So unless you have the bad luck that it contains a bug that is bad for your workflow, you won’t have problem with it.
Big realease like the differences between 2.68 and 2.69 - no. Yet bug fixes and some custom builds sure.
Why not? Is the 50MB download that big of an investment for you?
This is the page you should look at…
…hope it helps.
2.70 and later are allowed for the devs to break forward compatibility, so it means that yes 2.69 is the last of the 2.6 release cycle.
2.70 will be the release in which the UI will have changed, the start of a new UI work with tabs and etc…
Now, if you’re using the knife and bevel in your modelling sessions, 2.69 is not good enough as both tools are just buggy.
In 2.70 both tools have been fixed thanks to HowardT efforts, so if your modelling work require those tools to be functionning correctly, you’ll move to 2.70 anyways.
Piotr,
Haha, no, I just have a lot of clutter on my computer. One extra version here or there doesn’t make a real difference, but the time spent downloading, dealing with stability issues, and setting my preferences could (in theory) add up over time - not really a big deal, but I’m to lazy to try and keep up with the cutting edge.
Sanctuary,
Although I appreciate these tools, I was really waiting for one that would accurately generate vertexes at the intersection points between edges and planes. I know a boolean modifier could be used as a crude substitute, but it doesn’t offer the same level of user control that a manual intersect tool hopefully would.
Sanctuary,
Geom tools used to do exactly what I needed. I am surprised they where never updated or replaced with something similar. I actually tried Tiny CAD VTX a while ago but it wasn’t quite enough. Intersection looks perfect - is it totally broken in edit?
You’re in luck then, there are no stability issues to ‘deal with’ (whatever that means), and you can import your settings from the previous release with one click on the splash screen.
Yes.
There will almost certainly be no updates to 2.69, however nothing is stopping anyone from making backports of fixes to older Blender releases. (2.49x for example got a few fixes committed but as far as I know nobody ever made a release from it).
Though there is not really that big a difference from 2.69 to 2.70, the number change sounds significant but this is really just a regular release (maybe 2 releases since we spent longer this time between releases).
Is it? I thought there would be some compatiblity breaking in 2.70. That would in some sense be a milestone, right?
@PhysicsGuy, that is/was the plan, but not that many breaking changes ended up getting in. Though it depends where you work - freestyle Python API was re-arranged and had some breaking changes, Image.gl_load() api call had an argument re-arranged… off hand I cant think of many though.