The current process has been to keep the default_settings.ANNOTATION the same historically and then patch it
See vgtest2.py (which is setup to use latest stuff)
This is not great when setting up a new machine as you have to go and work out where the latest config is.
I think it's better that we put latest in default_settings and then configure the historical stuff in server specific deployments - all of which are in variantgrid/settings/env/
Even better would be to configure everything, and only have a few settings to select between columns versions etc - though not sure this would work. We have been pretty consistent in bumping everything together in big "columns versions"
The one difficulty is we don't store the dev config in source control, so they may experience an "unexpected upgrade" and need to change some settings
The current process has been to keep the
default_settings.ANNOTATIONthe same historically and then patch itSee vgtest2.py (which is setup to use latest stuff)
This is not great when setting up a new machine as you have to go and work out where the latest config is.
I think it's better that we put latest in default_settings and then configure the historical stuff in server specific deployments - all of which are in
variantgrid/settings/env/Even better would be to configure everything, and only have a few settings to select between columns versions etc - though not sure this would work. We have been pretty consistent in bumping everything together in big "columns versions"
The one difficulty is we don't store the dev config in source control, so they may experience an "unexpected upgrade" and need to change some settings