Closed kloczek closed 3 years ago
Duplicate of https://github.com/OSGeo/gdal/issues/3012
BTW IMO it wold be good to split gdal and autotest into two repos or merge them pernmanently up to dist tar balls, or starting care to not commit sinhgle commits across those two directories because curretly it is really hard to pick exact subset of git patches to fix some issues which are already fixed in git repo.
Do you have any plans to make new 3.1.x release soon? (I see that more issues has been sorted out on 3.1 branch)
BTW IMO it wold be good to split gdal and autotest into two repos or merge them pernmanently up to dist tar balls, or starting care to not commit sinhgle commits across those two directories because curretly it is really hard to pick exact subset of git patches to fix some issues which are already fixed in git repo.
Every choice has trade offs, but having single commits with code change + related test is a major plus as a developer when investigating the impact of a code change.
Do you have any plans to make new 3.1.x release soon?
Probably end of this month
Every choice has trade offs, but having single commits with code change + related test is a major plus as a developer when investigating the impact of a code change.
Looking on the code I think that the best would be just move gdal/* level up to have autotest/ as subdirectory.