[prev in list] [next in list] [prev in thread] [next in thread] 

List:       qubes-devel
Subject:    Re: [qubes-devel] guest OS support matrix
From:       Joanna Rutkowska <joanna () invisiblethingslab ! com>
Date:       2016-01-14 10:26:42
Message-ID: 20160114102641.GB965 () work-mutt
[Download RAW message or body]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Thu, Jan 14, 2016 at 03:02:09AM +0000, Patrick Schleizer wrote:
> Marek Marczykowski-Górecki:
> > On Wed, Jan 13, 2016 at 10:06:10AM +0000, Zrubi wrote:
> > > Hi,
> > 
> > > Do we have any official statement about the supported guest OS versions?
> > 
> > Actually we don't have even official statement about which Qubes
> > versions are supported...
> > We should work on it, thanks for bringing it up!
> > 
> > > Where supported means you (ITL/Qubes developers) provide qubes related
> > > packages for a specific Qubes release.
> > 
> > > I mainly interested about fedora releases - but the same info would be
> > > helpful about other distributions as well for sure.
> > 
> > I think the answer here is (in practice):
> > R2: fc21 (which is no longer supported by Fedora)
> > R3.0: fc21, (fc22), fc23
> > R3.1: fc21, (fc22), fc23
> > 
> > And for Debian it would be:
> > R3.0: (wheezy) jessie
> > R3.1: (wheezy) jessie (stretch)
> > 
> > In parentheses I've put versions for which we publish the packages, but
> > don't do excessive testing.
> 
> That table would be useful in the documentation.
> 
> Yes, best to not support that many with excessive testing. For example
> on Debian, just jessie. And moving on to stretch once that gets close to
> the new stable.
> 
> > > And because we have more than one supported Qubes versions and more
> > > than one guest OS distributions/versions we should have create a
> > > compatibility/support matrix.
> > 
> > > Right now the docs only talking about ITL supported vs Community
> > > supported templates - but not about OS versions.
> > 
> > I think we should have some clear policy on that. For both supporting a
> > Qubes versions and VM templates. Some proposition:
> > We support (release updates with bug fixes) for the most recent Qubes
> > stable version and for the previous stable version up until a year after
> > releasing the current one.
> > This would mean:
> > R3.0: supported, not end date set yet (will be a year after releasing
> > R3.1)
> > R2: supported until Oct 1 2016 - a year after releasing R3.0
> > 
> > Generally IMO we should encourage users to upgrade to newest available
> > version, so maybe even harder policy, like:
> > - full support up to 6 months after releasing the next stable release
> > - security fixes only, within next 6 months
> > 
> > What do you all think about it?
> 
> Go short. I am amazed how productive you are, but loading too much
> maintenance work on you for old versions is not great. You know best how
> much effort it generates. Go shorter. Long time support versions are
> enterprise features. So interested enterprises should pay for this. As a
> user of a security focused distribution, I am more interested in latest
> security rather than old versions. Ultimately up to the Qubes Council.
> 

+1 for what Patrick is saying about the long term support being more of a
pay-for-it feature.

joanna.
-----BEGIN PGP SIGNATURE-----

iQIcBAEBCAAGBQJWl3fhAAoJEDOT2L8N3GcYMlkQAMgPkyrv8nmbzaamx77mJt6R
viqJdpZCdTtvYIJH1rQcxoOP4YkaJT2HtSikj4ta3I2xJVDD+j6ZHWskA8Itr+hd
9yPRa/jdNG+P74q4smDL6Jrfin06MRy8rXiUGGXtRS7VDrsMuFLxlcNorE/o5zls
o+eB9py7/2suPcxToJMst8QAdympLseHO8tQcvHoZ51fCIGiUYTBbiKB07l7J74G
uMD7vgOjpBXghYltVdh3b7XpLY/Flnk4wJnGyHG691/JlNKYW7cQvD3tl01aEiDw
12e5XPjNnRFCAjbX+LMlXJLf01/4sC0cM9XWtUUyn8RJYKZIlvgE47bcgdEhtWAE
briEaWfAoUDaUeRwVjnQIUeDODDeqaM3AvKJOcPMoJ4QWJ5cjqfMRYbYDjmGXDPf
phsVByhzgekNgbbt60MzCoH0TqhHbs4av/QGVnum4UGLCnJI+VfiRVMYkh3QN4Kj
5FQP04FflpAeW0+QuTPN0KdcODG7LNVsf4v6jNxP1qksD2bjcYO2QRupk0cTxhTz
XotbQseJDpWHBu6S8tXOx3Mw7OpeZbbWAylblOf0nltva0iz+YtQXZXFUIqkj/Xf
D1HXsK5GGF4GdcBZRojEDJFYSnaDpcTyBATwuxzx5LHOjdnEDP7bNcFC6MVE1IIe
o3658moJJqhwMCVmbalu
=hkeu
-----END PGP SIGNATURE-----

-- 
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 qubes-devel+unsubscribe@googlegroups.com. To post to this group, \
send email to qubes-devel@googlegroups.com. To view this discussion on the web visit \
https://groups.google.com/d/msgid/qubes-devel/20160114102641.GB965%40work-mutt. For \
more options, visit https://groups.google.com/d/optout.


[prev in list] [next in list] [prev in thread] [next in thread]