You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In any case, 1. is not much work by itself, while 2. is quite intense. Both would need to go through a LOT of RAD testing and since they're pretty independent things but very likely causing big changes in responses, we should do one-by-one and separate RAD testing.
It was also concluded that, while strictly speaking we wouldn't have to bump the major version for any of these, it's probably a good idea to phase it in over a period of time, e.g. by providing separate copy/paste/edit costing models or a new next_gen boolean flag in the request, for users to turn on & trial the new logic.
The text was updated successfully, but these errors were encountered:
In #3896 I suggested another way of weighting costing factors. We discussed it in more detail last week and found:
use_*
factorsIn any case, 1. is not much work by itself, while 2. is quite intense. Both would need to go through a LOT of RAD testing and since they're pretty independent things but very likely causing big changes in responses, we should do one-by-one and separate RAD testing.
It was also concluded that, while strictly speaking we wouldn't have to bump the major version for any of these, it's probably a good idea to phase it in over a period of time, e.g. by providing separate copy/paste/edit costing models or a new
next_gen
boolean flag in the request, for users to turn on & trial the new logic.The text was updated successfully, but these errors were encountered: