UniVerse 11 continued with 11.4.1 long after 12 was released. The two remained in parallel until 14 due to some sites not being able to migrate to v12.  According to the matrix, 11.4.1 is EOM 2026, EOS 2027 and EOLS 2029. So it you want to stick with 11 you have some time.

I don't know all the reasons for different sites, but one was generally around problems with the system buffer, which caches updates to the database. If sites are doing things at the OS level, e.g. copying files (one of my clients takes a full copy of everything before and after running overnight processes) those would be out of sync since the OS doesn't know about the buffer. There are other, similar use cases that fell foul of the changes introduced in v12 - and the lack of good documentation on the new configurable settings and what had changed did not help. As it happens I've been using 12 quite happily but most of my clients steered clear owing to the confusion around that version and lack of confidence in upgrading.  

Looking forward to moving to 14 when I get the chance. On the face of it, that should be a smoother upgrade from v11 than was v12.

We found version 12 of Universe to be weird but usable. We have been on 14.1 ever since it came out. Other than the fact that they got rid of version 12 weirdness, the release is stable.

We just finished testing the beta of 14.2. The new features, such as try/catch and JSON objects, will require a lot of code changes, which you will need to decide if they are worth it. Moreover, we found that the UOJ dataset copy used in our Universe EclipseIDE tools is about 5 to 8 percent slower. When they finally release it we will be the first on board since we found no issues with our UOJ middleware, Universe subroutines, Universe functions, and the entire environment.

Last auto-saved at: 06-02-2025 15:55