There's a confusion in the docs and the GUI about the terminology around updates and the proxy mechanism. The docs tend to use UpdateVM, but the Global GUI uses "Update Proxy".
I want to standardise this: 1. use "update qube" in the docs and the GUI for the actual qube 2. dispense with "updateVM" all together 3. reserve "update proxy" for the mechanism, and the process. I see no reason why we cannot use "update qube" for both dom0 and templates, although the mechanisms here are very different. (We already do this with update proxy.) I think this will be clearer to users and address the issues in QubesOS/qubes-issues#10162 Thoughts? -- I never presume to speak for the Qubes team. When I comment in the mailing lists I speak for myself. -- You received this message because you are subscribed to the Google Groups "qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/qubes-devel/agc-ZWYeSXBw7rDi%40thirdeyesecurity.org.
