Here’s the link to the latest weekly build of darktable 5.7, https://www.dropbox.com/scl/fi/i5pdd6facohyenqmxnzgc/darktable-5.7.0-537.g13f3092df1-win64.exe?rlkey=d6gsdp02hopzh8zczcpxn5m5c&st=q3ayuptk&dl=0. The list of latest changes is at Comparing c19e88f8d8…13f3092df1 darktable-org/darktable · GitHub
I noticed this installed a parallel darktable dev rather than replace 5.6.0.
Is this intended to be run side-by-side?
I didn’t get the warning about upgraing databases. Other than new features in edits, is it compatible with the 5.6.0 lighttable operations and 5.6.0 edits?
Just wanted to make sure it’s not going to do anything irreversable.
Also, how much of this is 5.6.1 bug fixes vs. 5.8.0 new features?
Yes and no. Depends on what you want. Lots of folks here are using the nightly for their daily editing. Currently there are a lot of bugs in the nightly to be squashed so I’d at least Sa be cautious.
The database itself doesn’t might become incompatible and you could end up using features in 5.7 (=nighlty=insider program) that are not available in 5.6 (e.g. the new contrast and texture module), which could lead to incompatible edits.
I’d advise to run 5.7 with a separate config. See here: darktable user manual - using a test environment
Hard to say. Lots of 5.8 stuff by now I guess. Lots under the hood, some new features.
1 Like
The database can get incompatible if there is a new feature forcing a database revision. Right now we have none, but I think there is a PR that could trigger one.
If you want a 5.6.1 branch (bug fixes), you will need to compile it.