Barney Boomslang

Living a Second Life. In a Treehouse.

Official Linden Blog: Second Life will be back up with its previous 1.12.1 release

Official Linden Blog » Blog Archive » Second Life will be back up with its previous 1.12.1 release – well, you know, I would be one of the first to applaud a canceled release if problems arise. But well, this thing still doesn’t make me happy. Why? Well, this can’t be a problem that shows up only under high load – there was no high load in the grid, yet, as it still is closed. So essentially they did a full grid deploy to find something that they should have seen in the preview grid in the first place. This smells like last-minute-changes without actual testing. Again.

You know, Phillip Linden – the problems with getting out a stable update without either borking it completely or ridiculing yourself and the residents – that’s really pulling me down.


Written by barney

October 4, 2006 at 18:24

Posted in Second Life

10 Responses

Subscribe to comments with RSS.

  1. It’s almost noon… do you know where your Lindens are?

    Kali Zeluco

    October 4, 2006 at 18:50

  2. Kind of have to agree with Barney…

    Zia Zia Bo Bia

    October 4, 2006 at 18:51

  3. to simulate such realism and to give so many options is a mindboggling thing and takes a lot of talent, to keep working the bugs out is dedication, to those that complain of the minor inconeniences, if you can go better, open your own website so you can show your superiourity, if you can’t, then give credit where it is due, enjoy the site and try to do something constructive and stay off peoples backs.

    zale barrett

    October 4, 2006 at 18:56

  4. Well, after a day working I wait now for hours to play.
    It’s now 21:00 hr (GMT +1 in Amsterdam Holland.)
    Yeah I know it’s good for my 1st life to have any social contacts now 😉


    October 4, 2006 at 18:58

  5. I have to disagree. One major difference between the test and release grids is the number of sims interacting with each other and the asset servers. Such highly parallel development systems are extremely difficult to test and debug.

    I have to say this – it says much more that they found the problem BEFORE opening the grid and withdrew it. You know as well as I what you, and others, would be saying if they went ahead with the release and people found this issue instead. Give them the credit they deserve, instead of finding a way to make assupmtions that turn it into a sign of incompitance.

    Having done software development for over 20 years, I have a good idea what they are dealing with, and while I am not happy with every release, I will still give them full credit when they admit to a problem and take the appropriate steps.


    October 4, 2006 at 19:00

  6. Yep, you are so right I think. Of course im not a compurter gurue but I am one of the general sl players and if this way of doing the updates keeps on it will make some very unhappy.Unhappy enough to just leave the sl, it has happen before.
    I played in tso for 4 yrs and i know it’s not the same as this sl but the way they did things was uncalled for and along the same lines as this is doing now. people started to leave and it just kept going and now if you look at it it’s a dieing game.

    Bob Parker

    October 4, 2006 at 19:09

  7. Hmmm, curiouser and curiouser…that’s been going on since the last update…sounds like this one made the bug more prominent and they’ll be forced to fix. Gawd I hope so…I have a dear friend who’s face becomes a missing image after every single teleport.
    PLEASE fix this LL, I miss my friend!

    Lizbeth Marlowe

    October 4, 2006 at 20:43

  8. Hi Barney,

    I’d just like to take a moment to clarfy a couple of things for you. The problems we noticed with the 1.12.2 deploy this morning were first noticed on the beta test grid as more than 120 avatars came in when the main grid was closed. The specific problem we were seeing had to do with the way avatar skin and clothing textures are “baked” and stored for each user. Since that function had not been changed by any new code in this release, we wanted to take our time to fully understand its cause (and solution) before deploying any of the new code to the production grid. Anytime we see unexpected behavior like this we’re going to pause fully until we understand it completely. It may well prove to be a configuration issue with the beta grid, but we’ll take the cautious route, today and in the future, if a situation like this arises. All of the code in the 1.12.2 release package has had several separate complete rounds of testing. The code appears on the beta test grid many iterations after it’s initial rounds of formal QA.

    I just wanted to clear up the misconception that errors in this release were found on an “unloaded” production grid this morning. They were never deployed.


    Joe Linden

    October 4, 2006 at 20:52

  9. I have to agree with that. Problems like that should not occur if proper release management is being applied, which we know is not the case, otherwise things like that cannot/would not happen. C’mon Lindens, it is really SO problematic to hire a few folks that know how to run a commercial site?
    No pun intended, you guys are great developers, but I have the feeling very few of the lindens have actually been responsible for sites this size, and are learning how to handle real web sites as we go along. I have been in the industry for way too long to know that snafoos like this should never happen, especially if you have release management in place. Of course if you are doing a fly by night operation that is different *smiles*

    Andy Sao

    October 4, 2006 at 23:32

  10. joe: well, if they never where deployed – what was deployed, took up 5 hours to deploy and was pulled because of this bug you say was allready found in the preview grid? Or did you notice the bug, still deployed the release just to pull it because of a bug you allready noticed in the preview, so would have been able to prevent the mis-deploy completely by just listening to yourself?


    October 7, 2006 at 12:57

Comments are closed.

%d bloggers like this: