We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
No description provided.
The text was updated successfully, but these errors were encountered:
To my satisfaction, this is done.
Is there a decoder ring for Epic? or a clue as to the expected lifecycle of such issues? What sort of evidence should I present that this is done?
Sorry, something went wrong.
Hi Dan - good questions. In most cases, Epics should just have underlying Issues which can be closed out. Once 100% are closed then the Epic is done.
I'm managing this in a separate project management UI and didn't actually realize that Epics showed up in GitHub
... I'm managing this in a separate project management UI and didn't actually realize that Epics showed up in GitHub
ah. that makes sense. I'll stay tuned for more about that.
The proof of concept was in the context of #511 ; in particular, Oct 28 seemed like a pretty good result for a proof of concept:
With the fix to the snapshotting maps issue we get thru all 70 deliveries!
For reference, the relevant code...
https://github.com/dckc/agoric-sdk/commits/xs-snap-generator c206eaa
dckc
No branches or pull requests
No description provided.
The text was updated successfully, but these errors were encountered: