-
Notifications
You must be signed in to change notification settings - Fork 0
reconsider the 2023Q4 parameters once they have been thoroughly investigated #176
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
For posterity regarding scenarios:
Things that were flagged on Teams and ADO but may not have been formally addresse:
|
actually, decision for scenarios is supposed to be here, no? |
I'm not sure where it is "supposed to be", I'm just saying where it is haha. I had a call to solicit scenario decisions and documented all decisions as a comment, tagging all involved in the call. Maybe a good idea to also add it to the ticket you linked? |
I've added a comment to a similar effect to the ADO ticket you linked, with the latest verbal decisions that I have a record of from the last "Scenario Decision Making" call |
Not to be nit-picky, but I'd really like us to have a well-defined place where it is "supposed" to be recorded so that it's easy to go back to and verify if needed. Comments in various threads have, in the past, conflicted with each other, so I think it's advantageous to have one fixed, agreed place where the decision is made clear. (thanks for your effort towards that @jdhoffa) |
@jdhoffa says (in the ADO ticket) that the 2023Q4 parameters have been thoroughly reviewed and verified.... closing |
Uh oh!
There was an error while loading. Please reload this page.
#136 added the 2023Q4 config under time pressure with inadequate validation of the parameters. Once they have been thoroughly validated, we should update the config with the most correct values we can figure out.
AB#10387
The text was updated successfully, but these errors were encountered: