Channel and Version Requirements

Setting a Viewer Identifier for an Open Source Viewer

A Viewer Identifier is unique to a particular release of a viewer. It is composed of two parts: the Viewer Channel Name and the Version Number.

Viewer Channel Name

The Viewer Channel Name should be a unique base name for your viewer, optionally combined with a variant name (typically used to distinguish the type of build). Linden Lab viewer builds use:

Second Life

as the base name, followed by either

Release

for release builds

Beta project-name

for early release user test builds

Project project-name

for integration builds (which may or may not be publicly available)

Test

for developer builds

The default Version Name is Second Life Test

NOTE: Any Channel Name containing "Second Life" is reserved for use by Linden Lab (if you are building a test version for submission to Linden Lab, there is no need to change this)

The Channel Name can be any ASCII string. It should not violate Linden Lab's trademark policy. We recommend that the Channel Name be the name of the Open Source Viewer.

To set the channel name, set the cmake variable on the autobuild command line:

autobuild configure -- -DVIEWER_CHANNEL='"channel"'

or

autobuild configure -- -DVIEWER_CHANNEL="\"channel\""

Version Number

The Version Number is in the form major.minor.patch.build: any four numbers, separated by periods.

• We recommend using the Major and Minor numbers from the most recently merged Linden Lab source code.

The 4 numbers together should uniquely identify a version of the sources from which the viewer was built; Linden Lab uses an internal number from our build farm system for the Build number to ensure uniqueness.

To change the first three elements of the version number, edit the file indra/newview/VIEWER_VERSION.txt

To set the revision, set the revision environment variable. If that variable is not set, the indra/cmake/BuildVersion.cmake file will attempt to get the local revision number from your Mercurial working copy (which will not change for any changes that have not yet been committed), or if that is not found then it will use 0.

Updating an Open Source Viewer

• Anyone distributing an Open Source version of the Viewer is responsible for messaging updates to residents using that client.
• We recommend using your login url for directing residents to updates.
• Clients not based on the Linden viewer code base should ensure that the XMLRPC login connection sends:
  • channel = the channel name, e.g. "My Viewer"
  • version = a four-part version, e.g. "1.2.3.4"

Linden Lab Updates

• Linden Lab updates will not affect non Linden Lab channels. This includes optional and mandatory updates. It is the responsibility of other distributors to ensure that security patches are provided to residents using their client.
• NOTE: If Linden Lab determines that a particular client distribution contains security vulnerabilities or exploits, Linden Lab may block that particular version of the client from logging in.
• NOTE: If Linden Lab introduces a server update that requires a particular capability in order to connect to the server, Viewers that do not include the required capability will be unable to connect to regions running that version of the server. It is the intention of Linden Lab to make these required updates infrequent, and to make the Viewer code available well in advance of the server update.