This was previously a drop down. I think the drop down makes sense if we had a level of maturity where we knew that certain templates worked with certain versions for a variety of configs and we were able to rev the listings every time a point release came out. Neither of those things is currently true. I'd suggest we focus on increasing maturity in our publish process. Then if we get there, we lock it down. If we do that prematurely, users won't be able to override the version when our release schedule inevitably lags.
This was previously a drop down. I think the drop down makes sense if we had a level of maturity where we knew that certain templates worked with certain versions for a variety of configs and we were able to rev the listings every time a point release came out. Neither of those things is currently true. I'd suggest we focus on increasing maturity in our publish process. Then if we get there, we lock it down. If we do that prematurely, users won't be able to override the version when our release schedule inevitably lags.