Notes |
|
|
It was still supported at the time of Doomseeker 1.3.1 release, so this affects only 1.3.2 so far. |
|
|
(0021718)
|
Blzut3
|
2021-08-10 17:38
|
|
Just to add my thoughts here: I'm going to leave things be until we have some pain point with GCC 5, CMake 3.5, or Qt 5.5 (that would be solved with GCC 7, CMake 3.10, and Qt 5.9). Given that there was expressed interest to go to C++17 in 0003806 I can't imagine it will be long (and to be clear I have no objections to doing so), but that of course depends on how much time we have to work on this. Right now my goal is to get Doomseeker able to compile against Qt 6. |
|
|
|
|
|
(0022045)
|
Blzut3
|
2021-12-29 04:34
|
|
Nothing changed on my opinion here. It doesn't hurt to know that Doomseeker still compiles on 16.04's software versions, but there shouldn't be any hesitation to change the docker image if it breaks in a way that would be solved by bumping to 18.04. I'm not sure how one would assign a target version to that? |
|
|
|
I'm not sure how to track this effectively on the tracker either. Though now that I do think of it, I wonder if the Dockerfile can be – or should be – hosted in a seperate Git repository. |
|
|
(0022065)
|
Blzut3
|
2021-12-30 22:18
|
|
I don't see any benefit to putting it in a different repo.
My proposal is to just close this ticket, it will take care of itself when the time inevitably comes. |
|