String freeze for darktable 1.6

Dear all,

as we want to release darktable 1.6 some time at the end of the year, it now is the time to announce the string freeze. Please don't change any UI strings any more, so translators have a chance to catch up.

Translators: your updates should be committed to the master branch, there is no branch-off for a stable 1.6 version yet.

We should have the first release candidate packed up soon!

2 thoughts on “String freeze for darktable 1.6

  1. Is the database stable already? I’m considering upgrading to master but I wouldn’t like to convert my database to something which won’t be supported by the next stable version.

    Thanks,

    • If you don’t have any strong reason for the upgrade I would not recommend it.

      Having said this, the database should be stable (as it almost always is during development) and upgrading to master now with switching back to the release version later should not break things. As usual, make a backup before and be aware of the fact that you can’t switch back to 1.4.2 with the database once opened with git master.