On Thu, 28 May 2015 14:58:03 -0500 Michael Catanzaro <mcatanzaro@xxxxxxxxx> wrote: > On Thu, 2015-05-28 at 14:39 -0400, Przemek Klosowski wrote: > > Do you think the tech could stabilize enough to obviate the first > > reason? The 6-month workflow cadence remains a good idea, of > > course, but could result in a major offline upgrade, instead of > > an entire new distribution. > > I think we're already at the point where -- at least for Fedora > Workstation (not sure about Server/Cloud), and except for > infrastructure issues -- we can stop branding our releases with a > version number, and simply have a particularly big offline update > every six months. Behind-the-scenes, we still have the six-month > cycle, but this is hidden to users. They get Fedora and it's just > Fedora, not Fedora 21 or Fedora 22. People stop complaining about the > 13-months of support that isn't long enough for them: we wouldn't > have that short support window anymore, instead there is *indefinite* > support so long as you take your monthly QAed updates pack (five > small updates packs, then a big updates pack, then five smaller ones, > then a big one, ...). This is the model Windows is moving to, and it > makes a lot of sense to me. Well, this is sort of the old 'rolling release' vs 'timed releases' thing. ;) IMHO, some advanced users prefer/are happy with rolling releases, but I think the majority of users would not be happy at all. With rolling: you get the latest stuff soon, but you cannot decide when you want to deal with that stuff very easily, you have to take it when it's pushed to you (or block security and bugfixes). With timed: you don't get the newest thing, but switching to the new stuff is more on your schedule. You can ignore the new release for a while and still get bugfixes/security updates until you are ready to do the upgrade. In some kind of ideal world it would be great if rawhide was the rolling release and people who liked that model could use it day to day. (Which is really already the case, but things do break so you need to be good at troubleshooting and/or have alternatives in case the thing you normally use breaks). kevin
Attachment:
pgp4qDRhZzQTZ.pgp
Description: OpenPGP digital signature
-- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct