TCW wrote:
> On 3/13/2017 2:33 PM, Ronnie wrote:
>> TCW wrote:
>>> On 3/13/2017 2:08 PM, Ronnie wrote:
>>>> why is seamonkey saying it's 'out of date' when 2.46 was just recently
>>>> released?
>>>
>>> Because yes, it is out of date. I have seen some attempts to build
>>> 2.49 on the Mozilla site, t seems to be failing to build for Win32/64
>>> as it was previously. You should run the Adrian Kalla 2.48 build. It
>>> is stable. If you don't know where it is, I or someone else can point
>>> you to it.
>>> _______________________________________________
>>> support-seamonkey mailing list
>>> [email protected]
>>> https://lists.mozilla.org/listinfo/support-seamonkey
>>>
>> Well for linux distributions that heavily rely on repositories, until
>> those repositories are updated, which doesn't occur until an official
>> release. It only serves to make people uncomfortable running seamonkey
>> and move on to another browser.
>>
>
> Yeah but building Seamonkey has been busted on the official site for
> OVER a year+ and the recent successful build of 2.46 took nearly an
> act of God for it to be released. If repos continue to wait for those
> build to work and build properly again, it may be another year.
> Hopefully EWong can fix this bustage but I wouldn't get my hopes up.
> _______________________________________________
> support-seamonkey mailing list
> [email protected]
> https://lists.mozilla.org/listinfo/support-seamonkey
>
Regardless of the 'woes', my point still stands. There is no benefit to
announcing an out of date browser when no update is available yet. It
simply discourages people from using the browser which in turn means
less user which leads to a projects death.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
