Source downloads
Below is a list of all of the releases of the Second Life viewer source code, in reverse chronological order. Be sure to pay attention to the applicable licenses.
| Date | Branch (see Branching process below) |
Source | Libs |
|---|---|---|---|
2007-Jan-26 (FL-1.13.2.27) |
off of the beta-1-14-0 branch (where the First Look viewer comes from) |
Viewer |
|
2007-Jan-26 (20070126a) |
off of the "release" branch |
Viewer |
|
2007-Jan-26 (1.13.2.15) |
off of the Branch_1-13-2 branch (where our official releases come from) |
Viewer |
|
2007-Jan-19 (1.13.2.12) |
Branch_1-13-2 (r56958), last synced with release at r56659 |
(note: these were refreshed 20:58, 19 January 2007 (PST) ; if you downloaded earlier, please download again) Viewer |
|
2007-Jan-17 (20070117a) |
release (r56851) |
Viewer |
ViewerOther |
2007-Jan-17 (1.13.2.11) |
Branch_1-13-2 (r56833), last synced with release at r56659 |
links deleted: wrong source was uploaded | |
2007-Jan-12 (20070112a) |
release (r56702) |
ViewerOther |
|
2007-Jan-08 (20070108c) |
open source prep branch (r56647), branched from release (r56551) |
Viewer |
The "branch" column indicates what branch the source was pulled from in Linden Lab's internal source repository, as well as the version number. This is helpful in determining how and when to do merges.
Branching process
Though Linden Lab doesn't provide a public version control repository, it's useful to understand how Linden Lab deals with branches for understanding the code drops above.
Linden Lab does feature development on independent branches. As those features mature, they are merged into the "release-candidate" branch. The QA group tests the feature, and either reject or approve it for inclusion in "release". When a major release is about to happen, a branch is created for work on that release (e.g. "Branch_1-13-2"), which gets synced with the "release" branch periodically. Then, stability work is done on the branch, and the new code is deployed. After that, any stability work gets merged back into "release", and the process repeats for the next major release. In the meantime, stability work continues on the branch for maintenance releases.
Note that the dated releases (e.g. 20070117a) are sourced from the working trunk (the "release" branch), and the numbered releases (e.g. 1.13.2.xx) are to sync with the official viewer releases. This means that often, but not always, the dated releases are newer.
