[#VWR-2700] Keep the pre-voice 1.18.0.x viewer branch alive for builders

1. Second Life Viewer - VWR

Keep the pre-voice 1.18.0.x viewer branch alive for builders

Created: 08/Oct/07 04:53 PM Updated: 21/Jan/09 04:38 AM

Return to search

Component/s:

Performance

Affects Version/s:

1.18.1.2, 1.18.2.0, 1.18.3.5

Fix Version/s:

None

Environment:

N/A

Issue Links:

Relates

This issue Relates to:

~~VWR-2051~~ Regular viewer freezes since update to Voice viewer

~~VWR-210~~ Support Voice on Linux

This issue is related to by:

VWR-11642 Meta-Issue: Voice problems with the GNU/Linux viewer client

Description

« Hide

As nicely put by Lex Neva at http://blog.secondlife.com/2007/09/18/second-life-url-handler-exploit/#comment-479385
"Some of us have chose to stick with a pre-voice viewer for a few more major releases until all of the bugs and undesirable interface changes have been ironed out."

Phoenix Linden's blog comment as a response on that day was:
"We will investigate making a special channel to keep the 1.18.0 branch alive with security patches."

This is a follow up on the subject.

Due to the poor performance and the continuous freezes with the new voice client, ( http://jira.secondlife.com/browse/VWR-2051 )
builders should be entitled to be given a viewer that doesn't prevent them from actually working.

I therefore suggest a release of 1.18.0.7 (or 1.18.0.x branch) as suggested by Lex Neva until LL figure out a way to make the voice client as stable as what 1.18.0.6 was.

All

Comments

Change History

Sort Order:

[ Permlink | « Hide ]

Mercia Mcmahon added a comment - 09/Oct/07 01:07 AM

Changed to Feature Request, which is what this is (I.e., asked for expected behaviour to change, rather than unexpected behaviour occurring). This would be welcomed by many Linux users as it means they do not have a viewer that has a screen for setting Voice that does not work (yet).

[ Permlink | « Hide ]

Bryon Ruxton added a comment - 09/Oct/07 03:47 PM

Mercia, will all due respect, I see your point but I beg to differ. A new feature is defined as: "A new feature of the product, which has yet to be developed". This is not entirely the case, it's about keeping/restoring already existing features unless LL says otherwise. The core of this issue is about new bugs added and a way to find a decent temporarily solution for us not having to bear the consequence of the "unexpected behavior occurring" with 1.18.3.x. I would bet that the 1.18.0.6 viewer would still be working fine to this day for Mac and Linux Users (with no url handler exploit risks) if re-authorized today.

Since the 'Improvement' type is not given as a choice, I chose to classify it as bug which is the most correct category in my view for lack of better alternatives. It's about "a problem which impairs or prevents the functions of the product" that needs to be addressed in a different way, but nevertheless it's about bugs solving more than a new feature in itself. Please allow me to change it back and also changing 'Affects Version/s': to 1.18.3.5 since the bugs affecting 1.18.3.x is the reason behind this request. Thanks

[ Permlink | « Hide ]

Gigs Taggart added a comment - 09/Feb/08 03:16 PM

Byron

If you want to use an obselete viewer you can just put

-channel "My Channel"

on the command line on the shortcut or whatever

[ Permlink | « Hide ]

Bryon Ruxton added a comment - 06/Mar/08 08:32 PM

Thank you Gigs, I wish i had know this earlier...

I am closing this issue since LL is clearly not committed to stability, preferring having multiple teams working on different things always conflicting one another, rather than doing one thing at a time really, really well with the full power of its entire staff.