Difference between revisions of "Channel and Version Requirements"

From Second Life Wiki
Jump to navigation Jump to search
(New page: == Setting a Channel and Version for an Open Source Viewer == 1. Choose a channel name * The default channel name is "Second Life Release" * Other Linden Lab channel names are "Second Life...)
 
Line 29: Line 29:
* Anyone distributing an Open Source version of the Viewer is responsible for messaging updates to residents using that client.
* 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.
* We recommend using your login url for directing residents to updates.
== 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.

Revision as of 09:39, 28 September 2007

Setting a Channel and Version for an Open Source Viewer

1. Choose a channel name

  • The default channel name is "Second Life Release"
  • Other Linden Lab channel names are "Second Life Release Candidate" and "Second Life First Look [Feature]"
  • The channel name can be any ASCII string, however we suggest something along the lines of:
    • "Second Life Open Source [Brand and/or Feature]"

2. Choose a version number

  • The version number is in the form Major.Minor.Patch.Build
  • The version number can be any four numbers
  • We recommend using the Major, Minor, and Patch numbers from the most recently merged Linden Lab source code.
  • We recommend using a Build number >= 100 to indicate a non Linden Lab version.
    • Linden Lab uses the Subversion revision number for the build number for non Release / Release Candidate builds

3. Set the Channel and Version in the code

  • Edit indra/llcommon/llversionviewer.h
    • Modify LL_CHANNEL with the Channel Name
    • Modify LL_VERSION_BUILD with the appropriate build number
  • Update the version number in the following files:
    • indra/newview/res/newViewRes.rc - "FileVersion" and "ProductVersion" in the Version section
    • indra/newview/Info-SecondLife.plist - CFBundleVersion
    • indra/newview/English.lproj/InfoPlist.strings - CFBundleShortVersionString
  • Build the code

Packaging for Distribution

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.

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.