What's different from upstream LoopKit/Loop? #5
Unanswered
taylorpatterson-T1D
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
TLDR;: PowerPack is a derivative fork that adds seven opt-in features. The closed-loop dosing engine is LoopKit's and is unmodified.
Long version: https://github.com/LoopPowerPack/LoopWorkspace/blob/feat/AllFeatures/DIVERGENCE.md
If you're a LoopKit/Loop maintainer or user wondering whether PowerPack is upstream-compatible — the relevant points:
• PowerPack tracks LoopKit/Loop:main (not :dev) for stability
• Upstream merges are automated weekly (upstream-probe.yml on LoopPowerPack/Loop)
• PowerPack does not file bugs, feature requests, or PRs against LoopKit/Loop
• Bug reports for upstream behavior go to LoopKit/Loop directly
Beta Was this translation helpful? Give feedback.
All reactions