Hi,
Am 12.03.19 um 01:28 schrieb Patrick Shanahan:
* Heiko Bauke <heiko.ba...@mail.de> [03-11-19 20:21]:
[...]
Regarding the custom module, I am on my own of course. However, I
wonder: does the database conversion require that users migrate from
2.6.1 when 2.8 will be released?
aiui: the database is updated with *each* newer version.
but you do not have to "migrate", upgrade. if you upgrade *usually* your
database is not backward compatable, ie: you do not want to "downgrade".
I understand that I can not downgrade my database. My question was
about possible upgrade paths.
If the database version changes with every stable darktable release, is
it required to upgrade step by step from one version to the next later
version or is it possible to skip a stable version in between? In other
words, will users be required to upgrade from, let's say, version 2.6 to
2.6.1 to 2.8 or will one be able to jump from 2.6 to 2.8? I think,
this is a very relevant issue because the release cycles of darktable
are much shorter than the release cycles of some popular Linux
distributions (especially for users of long-term support distributions).
Heiko
--
-- Number Crunch Blog @ https://www.numbercrunch.de
-- Cluster Computing @ https://www.clustercomputing.de
-- Social Networking @ https://www.researchgate.net/profile/Heiko_Bauke
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
