On Sunday, November 12, 2017 at 7:49:25 AM UTC, Alexandre Brutelle wrote: > Thank you for your reply ! > > Do you think such upgrade to the next stable version will happen anytime soon > ? > > > > > > On 12 November 2017 at 00:47, Andrew David Wong <[email protected]> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA512 > > > > On 2017-11-11 13:01, [email protected] wrote: > > > When there will be a stable supported version of Qubes 4., and I > > > upgrade, will I be able to keep all my set ups and docs on each on > > > my VM's ? > > > > > > Or will I have to wipe it all in order to upgrade and install the > > > new version ? > > > > > > > If you're upgrading from 3.2 to 4.0, a clean reinstallation will most > > likely be required (or at least highly recommended). However, if you > > migrate using Qubes' backup and restore tools, your data and settings > > within each domU will be preserved. > > > > - -- > > Andrew David Wong (Axon) > > Community Manager, Qubes OS > > https://www.qubes-os.org > > -----BEGIN PGP SIGNATURE----- > > > > iQIbBAEBCgAGBQJaB4wLAAoJENtN07w5UDAw2AMP90wKEvDpxHo+rS7WF1E5e68P > > HNrB3TlwGUP/vduFfanUd2b1Zgi3Q4Q+4cc/NvdmFTtSadubEUeOjZDVe9lfZCEK > > n8P3lu0nES5xotb0i64CW/XfJxq3K8ca+EmIcp9YtZuwWeUBnJdbmU3YwE9HdAup > > xEtWX+BHYv3AAJf4vA75uuwoWgDG48pLYSmjNYtyyfuxdk/cFHQPVoHMVWyIpt/o > > nR2tdw3QSpBLZEduzlUsa5kNYzycZoGW9svT1DF4Vsx0/U4HB/MFhWsWcGWFvVcR > > PCdIZUCHtxSFTlBWlXw9GQyBA8xk6cHgnObugFJlG5f+aRMQnzrFqjHwSKG708Sp > > wNTo9CvfQZWf85lYHChzzwwDyMJ1klTDXF+/6j5vHrfDJhb29YtA0HZNhhtC/p7l > > 9AcJL1ntnLfHCxXwtKyt8kvl7pJJrEyPPMkkMPyk7RERBhxIDnKmKcfU0774Ex0A > > CspepiQ6N4t9+nZK2i3vYsWsDnDP97yjd/vY2wPfkOKmF/iCFEzvCh06K+RClTKM > > 4BkbjaMrqPCNdsJvbCn+N4sujP+8ix4ufrGEBMaazMssKadC7yNK0uvZLLMj0b8g > > ZaOwKgPB9ixUwC5wNsT7yu6BWWGqQyzqdabOKuQi9bXmaV3GS0NTWhFRK6XT7/8m > > lqaVGG9R98nLL22ZxNs= > > =mw3w > > -----END PGP SIGNATURE----- > > > > > > > -- > > > > > Alexandre Brutelle > > > http://linfinigeste.com/
Here you go, https://www.qubes-os.org/doc/releases/4.0/schedule/ Keep an eye out for release timetable updates here too, as you can see it had revisions and updates in the past, some may come in the future too. You find this link for the time tables directly below the download section on the official website, for all Qubes releases both past, current and the future releases to come. But currently, these are the official estimated release days given out by the Qubes team. Also a warning, don't do what I did! Frankly it's a bit embarrassing, since it's pretty obvious, but really, do not backup-restore any templates from Qubes 3.2 to Qubes 4... This worked just fine from Qubes 3.2. to another Qubes 3.2., but it won't work very well from Qubes 3.2. to Qubes 4, because the Qubes tools installed inside the VM's are different in their code between versions, and therefore not compatible (guessing from experience and hardships, I did not read the code though). At the very least, it gave me a lot of trouble, and it's at least partly explaining why qvm-run and qvm-open-in-vm did not work (partly). Seemingly Fedora templates work flawlessly now, if one does not do this mistake, but the debian template is still troublesome for some people (note: some people, not everyone), even if you re-install it. But aside from things like that, and as long as you can fall back on backups in case something goes wrong or you can spend time to try repair, then Qubes 4 is in my experience pretty stable now after some updates have been released. But this is mostly the common bugs everyone experienced, the uncommon bugs might possibly still give some people big issues, so you still need to watch it and be careful not to loose data or time, each hardware is unique and has its own personality, so to speak. Experiment with it, see if it's stable, and then make a decision whether you feel comfortable with it or not. Also another warning, ff you plan to install Qubes 4 while retaining QUbes 3.2. on the same machine through UEFI/EFI. You'll clear the EFI entry in the motherboard boot settings. At least i did not have much luck to use efibootmgr to restore my xen efi again, which always worked flawlessly in Qubes 3.2. So you need to have proper backups in place, just to be safe. On the other hand, Qubes installed through legacy BIOS boot appears not to have such issues though. Also be sure you meet the minimum requirements, as Qubes 4 is much more strict regarding having the hardware security features. Qubes 3.2. was more lax in this regard, so even if Qubes 3.2. worked, Qubes 4 may not. Have a look here https://www.qubes-os.org/doc/system-requirements/ -- 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/9c2a1ff3-5ca2-4ea5-944c-f1176af4c9de%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
