On Tue, 2017-03-14 at 13:14 +0000, Richard Hughes wrote:
On 13 March 2017 at 15:32, Robert McQueen <rob endlessm com> wrote:We don't at the moment. :( Typically our release notes are finalised in the days between tagging the release in our staging repo but before it's pushed to our production repo, in parallel with the image and static delta builds, etc.So you'd probably do something 100% out-of-channel for that in the future?
I’d prefer to keep it in-channel if possible. As I suggested elsewhere in the thread, OSTree detached metadata might work?
That said - I'm not sure if we have the cycles to do _all_ of that right now, but Philip is about to start thinking about applying OS update schedule/policy to our Flatpak runtimesYou also want to talk to Allan about that, he's got mockups for auto-installing flatpaks in gnome-software for next cycle.
This? https://github.com/gnome-design-team/gnome-mockups-software/blob/master /wireframes/updates.png Allan?
so this is a very opportune time to talk about what eos-updater would need to have to become ostree-daemon, and then we can dig into these kind of integration points with a little more generic interest.Right. The only niggle/showstopper I can see is that for Fedora we'd want to use rpmostree rather than plain ostree. We can discuss more at the hackfest I guess.
Sounds like a job for separate gnome-software plugins, I suppose. Yes, let’s set aside a few hours at the hackfest for discussing it. Are you around for the whole thing? (I am, though I’m arriving a bit later on Monday morning.) Philip
Attachment:
signature.asc
Description: This is a digitally signed message part