Fix the default CondDB tag for 2017

@cattanem I suppose this should go to 2017-patches as well. Let me know if you prefer to cherry-pick from here or I should target 2017-patches first

@rmatev, yes it should. I'll try to cherry-pick from here but may not be the whole story as the DDDB tag in 2017-patches is also older.

While we are at it we should set up also a first default for 2018, identical to 2017, but with initial time

# set initialization time to a safe default
            self.__set_init_time__(datetime(2018, 12, 31, 23, 59))

Probably best to do it with a separate MR, to not interfere with the cherry-pivk to 2017-patches

Yes, I just did the MR for 2018: !1086 (merged)

Ok, let's do it the other way around then, I think it'll be a tiny bit cleaner

changed the description

changed target branch from 2018-patches to 2017-patches

added 26 commits

mentioned in merge request !1086 (merged)

I added the fix for the 2018-patches branch in !1086 (merged)

merged

mentioned in commit bd0e7509

mentioned in merge request Brunel!350 (merged)

mentioned in commit Brunel@8c543d8a

Admin message