> I usually think of software as the opposite of things like cars... the longer a piece of software lives the more the software itself gets complex and is more difficult it is to support and maintain. Fortunately older software doesn't wear out and break down like physical things do.
>
> The difference is the number of people interested in maintaining it, and ultimately (IMO) that's all that matters with software: how many people are interested in it? How much can you share the cost of maintenance with others?
>
> With release4.0 there may be lots of people using it an interested in it, but no one would know since there isn't much activity reporting bugs and contributing patches in that branch... ;)
>
> -David
>
>
> On Apr 18, 2010, at 12:56 AM, Adrian Crum wrote:
>
>> From my perspective, old versions of software are like old cars - how long are you willing to pour money into them to keep them running?
>>
>> Anyone who has tried to maintain an old car will know the answer to that question.
>>
>> -Adrian
>>
>>
>> --- On Sat, 4/17/10, Ean Schuessler <
[hidden email]> wrote:
>>
>>> From: Ean Schuessler <
[hidden email]>
>>> Subject: Re: Release 4 on the download page
>>> To:
[hidden email]
>>> Cc:
[hidden email]
>>> Date: Saturday, April 17, 2010, 10:22 PM
>>> ----- "BJ Freeman" wrote:
>>>> If support is important then the Phrase
>>>> "you need to upgrade to current trunk"
>>>> should be evaluated.
>>>> one of the things I try to keep is what commits will
>>> work with what
>>>> versions.
>>> Yeah, I don't think we want to have any pages that advise
>>> "upgrade your production environment to trunk". That is just
>>> going to lead to heartbreak for most people who try it.
>>>
>>> Eventually I hope we will be in the position to port stuff
>>> like these recently identified XSS attacks to older
>>> releases, much as security fixes are back-ported to older
>>> stable Debian releases. As Jacopo has identified, we don't
>>> really have the man-power to reach that goal. I still think
>>> it should be a goal and should be one of the things we
>>> suggest for new developers that want to get started working
>>> on the infrastructure. It would be a great way to learn
>>> about how things have been evolving.
>>>
>>> --
>>> Ean Schuessler, CTO Brainfood.com
>>>
[hidden email]
>>> -
http://www.brainfood.com - 214-720-0700 x 315
>>>
>>>
>>>
>>
>>
>
>
Locked
