Beta Testing 1.27.0

A preliminary version of server 1.27.0 has been installed on the "Second Life Beta Server" regions of Aditi.

A list of Aditi regions and whether they are in the Beta Server channel or not is here:


The 1.27 Release Notes are here:

Can LL please allocate the time to do another agent/asset snapshot? It has been a few months since the last one.

/me fixes links (for some anyway) by tacking '?' chars on..

edit: Hey! No http://jira.secondlife.com/browse/SVC-4142??? Should we even bother with pjira any more??

What about scripts, compile date and name of resident compiling?

I've raised this issue to see if the fix is small enough to get into 1.27 at this point. I can't provide any guarantees, however.

Oooo.. TY, Dante! It's a really, REALLY annoying bug.

/me hits Dante's "love" button.

Want to put that in a pjira, if it's not already there?

Not in public!

Aaww don't be shy Dante

Can we request regions in beta grid to be put on 1.27 if they are not already? (for those of us that have their own regions mirrored on the beta grid)

Is the baked texture uploading not already suported in some clients/proxy plugins as a way to upload textures local to a sim without being charged?

Looking forward to the http-in features, it could be a good alternative to email for inter sim communication between objects.

Dante, the last week or so has brought a big increase in the number of people having performance problems on their regions. Stuff like what's being said in this thread: .

Is LL aware of this? Got a JIRA I can vote for?

edit: /me starts a poll on how many people are seeing this..

I second the plea for a new snapshot. Someone said their inventory updated... mine did not. I will do a clear cache and relog... but I *need* my new inventory. I've got scripted objects that rely on new textures, and a whole builders tool I'd like to see in Aditi for a variety of reasons... but the new version won't show up there.

Which regions are yours that you'd like to have moved to 1.27?

We're working on it. The problem with doing an entire refresh like we've done in the past is that we would need to keep Aditi down until such a refresh is complete. We need Aditi to be up for 1.27 testing, so we're going to use a different approach to updating inventory. There should hopefully be a blog post and/or a forum post later this week about it.

Bet you saw this question coming... is there any way to opt out of such a refresh? Ideally, the refresh would be opt-in, and a resident could do it anytime.

Also, what is the current (or estimated, or guessed) timeline for 1.27 getting deployed on the main grid?

Thanks!

Unfortunately, it's not opt-in, and there is no good way to opt anyone out that scales for us. If you want to keep inventory items, maybe you could put them into a rezzed prim in aditi (that isn't somewhere where it will be auto-returned) and retrieve them after the inventory refresh?

My non-guaranteed guess would be early-mid July. All standard caveats apply =)

Of course! Thanks for the estimate.

It is costing me time, productive energy and money to not have the refresh. My time in SL is dropping to near zilch until it happens. There are projects I want to do, but which are just impossibly prohibitive to work on in the main grid, and my main tool has not been brought over in updated form. So the sooner the better. July? OKay, I'll come back to SL then, my land parcel is paid through the end of July.

Also...If you had a way of just refreshing a few people, count me in. Really desperate.

FYI:

According to Dante's post up in announcements today, yes!

"Aditi Inventory Refresh on Thursday
During the afternoon on Thursday, June 18th, 2009, we will begin enabling a setting that will refresh your Aditi inventory the next time you log into Aditi. This inventory refresh will only happen once, the first time you log in to Aditi after we make this change.

This means that if you've built anything on Aditi and you've got it in your inventory, it will be lost when you log in after we make the change on Thursday.

I'll update this post when we begin that work."

Thank you Dante and it will be interesting to see how this works. I am well aware of the high costs involved in a complete DB refresh. I think we would all be interested in a blog post on the nuts and bolts behind this new process if someone gets the time or inclination.

In the short term... YAY! WOO HOO! AWESOME SAUCE!!!

In the long term, this won't be the last snapshot for a while, will it? We will be able to update our inventories down the road?

This won't be the last one. Whether the next refresh will happen within a time period you like, well, that depends on your expectations =)

Thank You =D

It's not too complicated. The login process involves checking a per-user entry in the database for something we call transforms, which are triggers to do a variety of things. One of those things is to copy over inventory from another grid. So we can make an entry in the aditi database that says "when this user logs in, copy over their inventory from agni." It makes the next login take longer, but it keeps the grid up and only takes about half an hour to set up. A downside compared to a full database refresh is that it doesn't copy over new users.