Below describes moving from 00-19-01 to 00-20-00. See TdaqOneSixNotes for moving to 01-06-00.
Conversation 15/1/2004
Matt: I am using 00-20-00, but I think we may need to keep 19-01 because 20 requires DCS people to move to PVSS 3.0beta which they haven't done yet....hence the separate branch thing
(14:12:39) bjg1492: I'm using 00-19-01
(14:13:22) bjg1492: I don't suppose the modified config files work in 19-01 too?
(14:13:37) Matt: No, we need to keep two sets for now....
(14:14:47) Matt: But I think it is important to pressure a move to 20 (tho they may want to go straight to 21 in February which I think will include PVSS 3.0) because 21 will be a big change for us, but will be the combined test-beam release
(14:16:18) ajb57: Bruce are you using the version in /usr/local/atlas?
(14:17:19) bjg1492: Yes
(14:18:33) Matt: OK, in config/databases and daq-1/is, check out tag ONLINE-00-20-00 to get the right files. The HEAD is still 00-19-01.
-> You may need to remove old daq-1 jar files from the share/lib dir
(14:18:55) Matt: I will now be fixing the config files for 00-20-00 (and then I'll do the same to 00-19-01)
(14:19:13) bjg1492: I suspect that once we get something working well enough we will be under pressure (at least from Georg) not to change anything possibly till the next barrel...
(14:19:31) bjg1492: Fixing in what way?
(14:19:51) Matt: For SctTest and PMG synchronisation stuff
(14:22:26) bjg1492: OK
Matt: Yes, online 21 will be a watershed release. It will be out in February (new schedule to be presented on 20th Jan) and this will include the new CORBA engine. This is extremely significant for us - once the change is made, that is it., we will not go back. Sticking with the old online software is possible, but that means more pain at some future point and lack of support for the online stuff. It also means old versions of the dataflow, DDC and eventually PVSS......so you take your pick...