Dear Peter,
Upgrading from any version should be trivial. Simply, each time VB is started, it checks whether the version of the SemanticTurkeyData folder is older than its own version. In affirmative case, update routines for the data folder are invoked. The update routines are organized “per version” update and are run in strict order in case of a non-trivial leap skipping several versions.
That said, everything could happen and, indeed, it’s quite some time you didn’t update VB: the oldest version 10.x, which is 10.1 (we never published 10.0), is almost 6 years old.
Unfortunately, “not trivial” is a little vague as a reference :-)
The simplest hint I could give is: try with a smooth evolution, moving from 10 to 11, then to 12. This won’t take too long and some little patience might be expected after such a long time without an update.
I’m pretty sure that if they reach a more recent version, then they can try a longer jump (e.g. from, say, 12.1 to 15.1).
Also, pay attention to the version of Java:
Until version 11.4.1 Java 8 was needed
On version 12.0 we finally moved out of Java 8, with Java 21 required
On version 12.1 we downgraded the requirement to Java 17 (they might probably skip 12.0 and, even if doing the version by version upgrade, they could move from a version 11 directly to 12.1, so changing java only once from Java 8 to Java 17)
Providing some more insights about the issues met can also help.
Kind Regards,
Armando
--
You received this message because you are subscribed to the Google Groups "vocbench-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vocbench-use...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/vocbench-user/CA%2BGAPA6P8pper2DzHtVVarQnomiMF1wG_-9DpvMrdiTb_GeVEw%40mail.gmail.com.