Why should one upgrade Fedora whenever a new version is released?

[Reindl Harald]

Am 14.07.2013 02:11, schrieb Ranjan Maitra:
> On Fri, 12 Jul 2013 21:48:40 +0200 Reindl Harald
> <h.reindl at thelounge.net> wrote:
>
>> Am 12.07.2013 21:45, schrieb Paul Smith:
>>> Why should one upgrade Fedora whenever a new version is released? What
>>> are the main reasons?
>>
>> because after F19 is released a month later F17 is EOL and
>> get no security updates and no support and the same for F19
>> after F20 is released
>>
>> if you do not want this use a LTS distribution
> 
> And frankly, I do not understand these horror stories.

which horror stories?

* that F17 is EOL end of this month?
* that F18 will be EOL a month after F20 is released?
* that every week new exploits for every sort of software
  are coming out? well, subscribe at securityfocus.com
  and then say again "horror stories" in case of using
  unmaintained systems connected to the web

this and nothing else is the answer of the question in the subject
and if you do not want to make at least once a year a dist-upgrade
you chosed the wrong distributiin - there is nothing between

> Maybe I have been lucky, but ever since the LiveCD's came out 
> (F8-9 or so?) and we moved to USB, installs are like a couple of minutes. 

no idea how this is related to my answer or the topic
frankly i make fedora dist-upgrades on a routine basis
all the year and most of my systems are upgraded from
F9 to F18 with yum

> Unfortunately, however, the new Anaconda has delayed the point of
> getting there (to installation) by quite a bit.

luckily i do not see Anaconda that often

once a machine is installed it is upgraded twice a year
and in case of new hardware the RAID disks are moved to
the new one or virtual sevvers are migrated online

but taht's all completly off-topic

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 263 bytes
Desc: OpenPGP digital signature
URL: <http://lists.fedoraproject.org/pipermail/users/attachments/20130714/bef7f2d1/attachment.sig>