-
Notifications
You must be signed in to change notification settings - Fork 1
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
Agree on key use cases #3
Comments
Hi @arunkpatra - please see if this helps and can be incorporated as a value-added outcome. https://gist.github.com/sachinlala/827662b6ce6835665608df096795a40e Cheers. |
Arun - the 3 points above look good as the outcome. |
Thanks @sachinlala , this helps. I opened up #14 to compile thoughts on breakage forecast. I'm yet to compile the wiki but kind of leaning towards one of the two approaches I mentioned there. My option 1 that I have in #14 is essentially alignes very closely with your gist :-) Here's the link to the wiki. |
@sachinlala I thought we were chasing scope as in #11 for now. But I will see how much I can finish. Essentially, all the work that I have gotten done is under Programming Challenge milestone. I have already closed a bunch of issues in that milestone. |
Implemented the logic to forecast breakage in a simplified way. We look at historical breakage rates and then extrapolate for the current year. |
Closing for now. |
Do these make sense, vis-a-vis objectives and schedule constraints?
The text was updated successfully, but these errors were encountered: