[02:34] <mup> PR snapcraft#4010 opened: providers: push .bashrc to Multipass instances <Created by mr-cal> <https://github.com/snapcore/snapcraft/pull/4010>
[14:30] <InPhase> Hi.  I'm looking for solutions or a place to track work on solving the continuous "Pending update of ... Close the app to avoid disruptions" notifications without manual running of commands or long stretches of leaving programs closed.
[14:31] <InPhase> Installing a downloaded update upon close would seem a pretty obvious solution path for this rather than notifying at all.
[14:33] <InPhase> Or, alternatively, upon the next open.
[15:04] <loose> InPhase: there's been some progress on this fairly recently, see https://github.com/snapcore/snapd/pull/12280 and https://bugs.launchpad.net/snapd/+bug/1980271
[15:04] <mup> Bug #1980271: Snap doesn't refresh automatically immediately after snap is quit when update is pending <snapd:In Progress by rastersoft-gmail> <firefox (Ubuntu):Confirmed> <https://launchpad.net/bugs/1980271>
[15:04] <mup> PR #12280: many: implementation file monitoring for snap cgroups <Squash-merge> <Created by sergio-costas> <Merged by mvo5> <https://github.com/snapcore/snapd/pull/12280>
[15:39] <InPhase> loose: Ok.  I can see how that one would work as a component in a solution.  But I also notice there is no github issue list where this sort of stuff would normally be discussed and the connections planned out.  How does the developer community for snapd coordinate itself and plan when dealing with larger impact issues?
[15:50] <loose> InPhase: I'm not actively involved in snapd things, but afaik it's centered around the forums and the launchpad issue tracker https://bugs.launchpad.net/snapd