On Wednesday, December 13, 2017 at 2:05:30 AM UTC, Andrew David Wong wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 2017-12-12 17:33, grv wrote: > > I see on https://www.qubes-os.org/doc/releases/4.0/schedule/ that > > Dec 11 is the last date mentioned to decide if rc3 is final. Have > > we taken the decision? > > > > As far as I know, the decision has not yet been made. Either way, the > schedule will be updated soon. > > > If I install rc3, would I be able to update to QubeOS 4 in place > > (without having to migrate my VMs manually) ? > > > > We'll announce this as soon as we can. We usually can't say > for certain whether an in-place upgrade will be possible until very > close to the stable release. > > If we say that it'll be possible based on our current plans, and those > plans change, users may be inconvenienced (or worse). If we refrain > from changing our plans because we've already said that an in-place > upgrade will be possible, that limits our ability to improve the final > release while it's still in testing. We don't want to make promises > that we can't keep, but we also don't want to lock ourselves into a > path that turns out to be sub-optimal. That's why we wait to announce > things like this until we can be reasonably certain. > > - -- > Andrew David Wong (Axon) > Community Manager, Qubes OS > https://www.qubes-os.org > > -----BEGIN PGP SIGNATURE----- > > iQIcBAEBCgAGBQJaMIrWAAoJENtN07w5UDAwFb0P/jXEX9uR9gRG4epXtm0MD6Nb > VRfFclrqa/stuPlRkqnI3Ny/l8nDzltw3SX3RH9Ju9c2mK78XVKBGabw9VQbnLCP > lqKAVn2rcEZsMorKhUjjuwIsQjE6WJ9/OwrofTGjBLGlURNy2MvtChxe70u1XMw8 > PlTrmA4JgS3lBLLP7LLNi71WyQ2HZNZaI/k9yJ1v7LdCwyikVyhBnh3P3dc/YlZi > I9i4k/h2W8rDcBuTG3/S+MntMkAMypGpdqDwWEQCtR+JSsV1x5qT8gc6/WVPOhVs > A1I7qBLT2F5GjZg5ZUCTKdXIOu1FVM1pYsuYuTrLx5XbVvXVCWWEjC/DqQLEul77 > zUzZQDqkm/NfV7L8i3/CP1rlzG8PKPpzV4bM0ERsP5vrmOybyeKIu6rwoJzPPnLB > 8Ci2VOKG/I3/Ywf29GIl4uDydyBd5jHJYK5vxllGdNPwiBsQGPkRe4CSdp7QG2eO > o1ukxocmNSdKHgzs98ry1AvDPrbVKo62zRc+Q11W6B7/P0f4u5qIK5cVnVhk6jb2 > N/tgx2y4wMRJb2u3fF0t/YRci3qtA9GyaC1mxF9UOCYY+lalOxrT/tyhgd8p6mgu > 6f6X6pjgli+kbwCOszy1N1t5xrHyUY/KmDvEb4HkyrLu2Ut1y8IM+mS4nk0NygvR > temARax0ky3Duiw/Cg3C > =fZMg > -----END PGP SIGNATURE-----
Hey Andrew, Is there any chance if we can get recommendations, as for when it is recommendable to re-install between the Qubes release candidates? I.e. an extra line in the release schedule saying re-install recommended, or something akin to that? I'm just pondering thoughts here, whether it's possible or not. >From what I can gather, release candidates can be seen in two ways. - 'Updates are so major, that a re-install for the next release candidate makes for a more stable and reliable system.' or - 'Some systems won't work properly before updates are applied, therefore creating an impossible circle if booting, installing, reaching the update process, is unreachable.' When decisions are made in keeping or making a new release candidate, it would be greatly appreciated to have a means to know if re-install is the former, or the latter, scenario, or maybe even sometimes both. This would save a lot of time for many people to re-install, or even be worried and stressed about not doing so, when not knowing if one should or not. Is it possible we can include this tiny detail somewhere, i.e. in the release schedule, or somewhere else that is a sensible location that is easy to find for users? -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/b9c6b28b-e72f-41fb-b0cd-1eaf2ab96156%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
