|
I use linux elog, and if you upgrade to v3.x.x, it's difficult to go back to v2.9.x. This is because the log files get grouped in year sub directories at v3.x.x.
In 2.9.x, the logfiles are store as (made up example) /home/logfiles/yymmdda.log
In 3.x.x they are stored as /home/logfiles/2024/24mmdda.log /home/logfiles/2023/23mmdda.log etc. I think I got the labelling of the subdirectories correct, Stefan will no doubt correct if I am wrong.
I assume the same is true for the Windows version as it would be weird for a split in the program by OS for something important but trivial to impliment for all OS.
It's a bore to sort that out if you have to revert to 2.9.x - I know, I've done it - but I don't recall any change in format in the individual yymmdda.log files with an early v3.x.x version I tried. There may be additions to the log files made in much more recent v3.1.x or so versions, but I guess you are ok with whatever they may be as you've checked the change log.
| Patrick Upson wrote: |
|
Thanks. I did eveuntaully find the change log and made the decision to upgrade the at-sea machines. So far the configuration file we update for each mission still works. I have a copy of the 2.9.2 installer that if something catostrophic happens I can remove the new version and take it back, but I don't think it'll be a problem. We archive logbooks at the end of a mission, but each mission basically starts from a fresh install like state anyway.
| Stefan Ritt wrote: |
|
If 3.1.4 runs safely on your laptop, there should be no problem to update the 2.9.2 one. But first do it on a copy of your logbooks from the at-sea. The get converted automatically into a newer format but that should be transparent.
On the other hand you don't really need a new system if your old installation works fine and you don't need any of hte new features.
The changelog ist here: https://elog.psi.ch/elog/download/ChangeLog
Stefan
| Patrick Upson wrote: |
|
I've inherited a position that includes deploying elog for an at-sea mission. Once at sea there's no gauntee of internet connection so I have to be sure things are going to work before hand. The machines I currently have (we have several backup machines) are running elog version 2.9.2 and I'm looking for a change log, or feature list to determine if it's safe to update the at-sea laptops to the latest version of elog.
On one hand, I could leave things as they are and I'm sure it will just work, on the other hand, I hate seeing things get out of date to the point that something just stops working some day and there's no ability to get support for old software.
I'm already running elog 3.1.4 on my personal machine I use for configuration development and testing and it seems to work well. The config file is pretty simple and seems to work with 2.9.2 on the at-sea machines, but I don't want to run into any suprises if there ends up being a compatibility issue at sea.
|
|
|
|