Jump to content

Deploys for the week of 2014-08-25 (Updated @ 2014-08-27 10:00PDT)


Maestro Linden
 Share

You are about to reply to a thread that has been inactive for 3490 days.

Please take a moment to consider if this thread is worth bumping.

Recommended Posts

  • Lindens

Update: due to an infrastructure issue, the RC rolls for this week have been rescheduled for Thursday morning.

 

Second Life Server (main channel)

The main channel is getting the maintenance project which was introduced to all three RC channels last week. This project contains a single crash fix.

https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Server/14#14.08.12.292832

Scheduled Tuesday 2014-08-26 03:00-09:00 PDT

 

Second Life RC BlueSteel:

BlueSteel is getting a new server maintenance project.  This project fixes some crash modes and some other miscellaneous bugs.

https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_BlueSteel/14#14.08.22.293247

Scheduled Thursday 2014-08-28 07:00-10:30 PDT

 

Second Life RC LeTigre:

LeTigre is getting the same server maintenance project as BlueSteel.

https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_LeTigre/14#14.08.22.293247

Scheduled Thursday 2014-08-28 07:00-10:30 PDT

 

Second Life RC Magnum:

Magnum is getting the same update as BlueSteel and LeTigre.

https://wiki.secondlife.com/wiki/Release_Notes/Second_Life_RC_Magnum/14#14.08.22.293247

Scheduled Thursday 2014-08-28 07:00-10:30 PDT

 

We will be monitoring this thread as the code gets released, so feel free to note any observations you have about the server updates.  If you have a specific bug you'd like to report, please file a Jira.

Link to comment
Share on other sites

Hmmm... Isn't Project Interesting a shiny? I think the Lab did a great job with it, really, and I keep getting amazed with the viewer's perfomance — Firestorm, that is — loading scenes. Also, what's the point of getting new shinies if existing bugs are not fixed?

Link to comment
Share on other sites

Sadly "Project Interesting" has its own tranche of bugs, some of which appear not to have even been considered until the Firestorm devs merged the code into their viewer.

Yes, PI is good and is definitely a "shiny" but it is also like so many other Linden "shinies"...half-complete.  FIRE-14394, FIRE-14396 and an associated Linden BUG.  It'd be nice if they'd (Linden Lab) issue things without such obvious flaws.

Shame really, Simon did a lot of work on this feature but was clearly not allowed to finish it.

Link to comment
Share on other sites

Bug fixes are of course welcome, but I don't consider those "shineys".

I also don't consider infrastructure changes or improvements as "shineys" either.

 

When I say "shineys" I mean user explicit usable features.Things that allow users do and experience new things they never were able to until now.

 

This year has been the slowest year for such features as we've only had three of them become available.

- Group bans via the viewer (several bugs still persist in the UI/server).

- Materials updating by LSL.

- Experience Tools (still in beta, still incomplete LSL/UI/infrastructure wise).

 

I have a feeling SL2 has now become the boardroom focus for all future feature consideration and implementation...

Link to comment
Share on other sites

MBeatrix:

http://jira.phoenixviewer.com/browse/FIRE-14394 is the main Firestorm JIRA re state change issues.

: https://jira.secondlife.com/browse/BUG-7084 is the LL BUG/MAINT entry.

http://jira.phoenixviewer.com/browse/FIRE - 14396 is the other.  Dunno why the Firestorm ones won't copy the link, but if you enter the url into your browser it should get you there.

 

Edit: OK 14396 doesn't apear to exist, I have it wrong then...I will try to find the number.

Link to comment
Share on other sites

You won't see much in the way of shinny new things for awhile. The Lindens are rebuilding the tools that are used to build the viewer and server software. Think weeks.

They are also testing a CDN system the has the promise of providing a BIG performance improvement. CDN = Content Deleivery Network. The system will make downloading textures much faster, especially for those outside the USA. Depending on timing, we may see the HTTP Pipelining come online at the same time thus provising a double bang in performance.

I am guessing while these do not fit your defintion of shinny's they are big improvements. People always complain about lag. So, the Lab does what it can to reduce it. Many demand the Lab stop adding stuff and fix problems. Others like you want new stuff.

I suspect ideas on performance from HyFy are making it to the peeps at LL. Plus they have ideas of how to improve SL too. And the open source community is adding things too.

Geenz that was a key contributor in adding Materials is working on better reflections. Plus adding a way to have Matterials without having to enable ALM.

But for new things you can poke... not much happening this week.

Link to comment
Share on other sites


Nalates Urriah wrote:

 

They are also testing a CDN system the has the promise of providing a BIG performance improvement. CDN = Content Deleivery Network. The system will make downloading textures much faster, especially for those outside the USA. Depending on timing, we may see the HTTP Pipelining come online at the same time thus provising a double bang in performance.


Sounds like a BIG shiny to me:smileyhappy:

Link to comment
Share on other sites

Cincia

It is quite likely that the number of watchers on the "state change" script bug will be small because a lot of users won't realise what is causing the bug.  I didn't at first until Antony Fairport explained it in the Firestorm Support chat!

That said it IS a bug that needs to be fixed and the fact that the LL BUG report mutated into a MAINT code suggests they are taking it seriously and it will be fixed sooner rather than giving it to Roundtuit Linden.

There are few folk that would not prefer PI as it is warts'n' all, I think we are all agreed on that.:smileyhappy:

Link to comment
Share on other sites

You are about to reply to a thread that has been inactive for 3490 days.

Please take a moment to consider if this thread is worth bumping.

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...