Second Life Server

[Nika Talaj Member]

So, we will no longer be able to search JIRA to find out if something we observe is a new, already-reported problem.  Or comment or contribute information to issues other people report.

We CAN search issues that, as of this day, are visible. I suppose that will be useful the next time the head-up-your-behind bug surfaces.

The only way I can make sense of this is if LL intends to never roll out any more new features.

Is that what's happening?

[Qie Niangao Advisor]

I don't think it makes sense even if LL never intends to roll out new features. As long as the system is under maintenance, they need a public repository of defects. 

It does, however, make sense if they are getting ready to quit working defects altogether.

Assuming they're not also planning to pull the plug on the platform any time soon, your suggestion Across The Street to set up a shadow bug-tracker for SL, run by residents, would be essential for any of us hoping to stick around.

I wonder if Cristiano could be enticed.

[Innula Zenovka Recognized Helper]

Firestorm already have their own jira, of course.

The only way I can make sense of this (for certain values of "make sense"), in the light of Nalate's and Inara Pey's reports about a more integrated approach to supporting TPVs is that, as part of this, LL have decided they might as well let Firestorm take over running the public jira fo them.

[Perrie Juran Member]

---

Innula Zenovka wrote:

Firestorm already have their own jira, of course.

The only way I can make sense of this (for certain values of "make sense"), in the light of Nalate's and Inara Pey's reports about a more integrated approach to supporting TPVs is that, as part of this, LL have decided they might as well let Firestorm take over running the public jira fo them.

---

Regardless of Viewer, there would still need to be a central repository for bug reports.

I do understand the problem with determining the source of the problem.  When Mesh went live and my FPS took a nose dive, because I was using Firestorm, that is where I posted my JIRA.  First thing they did was ask me to see if the problem occurred with the Official Viewer. I hadn't so I did.   Actually, it was worse. 
So  I filed a JIRA with LL.

(sadly, my issue is still not resolved   )

[Nika Talaj Member]

But, Innula, what about server-side problems?  I just cannot envision something like Pathfinding being rolled out without users being able to search for known problems, and disseminating that information through the various inworld groups to which we belong.  Heck, pathfinding products have yet to hit the market - even that feature is not fully rolled out.

I would think that if we're all utterly blind as to whether some anomaly we've observed is a known bug, it will result in more support calls.  And more people simply giving up SL when confronted with what turns out to be a transient issue.

I can see how the customer chatter on JIRA may waste developers'  time, but it was LL's decision to merge the customer issues JIRA with the development team's JIRA.  To deny users any visibility into known issues is inane.

[Innula Zenovka Recognized Helper]

I agree it's insane.   All I can think of is that we're supposed to bug Oskar and Maestro with server-related problems here and in user groups.   It's not Oskar and Mastro who seem to have taken the decision, after all.

[Brenda Archer]

It doesn't make sense to not be able to add info when an issue is going on.  New users who try to find answers to their problems in LL official sources and fail will likely leave SL.  It is also a strongly chilling effect on anyone who might have been thinking of using SL to develop a new project.

[Pamela Galli Member]

---

Nika Talaj wrote:

I would think that if we're all utterly blind as to whether some anomaly we've observed is a known bug, it will result in more support calls.  And more people simply giving up SL when confronted with what turns out to be a transient issue.

---

I cannot begin to count how many times I found a workaround in the JIRA. Like, if I am told I can't rez on my own land, point the camera at my feet. Lindens did not discover this -- as with so many issues, a team of resident commenters did.

[Drongle McMahon Advisor]

"it was LL's decision to merge the customer issues JIRA with the development team's JIRA."

But as far as I could see, they always cloned issues into a private jira when they started work on them. So I can't see that as the explanation.

[Stickman Ingmann]

I would like to add in my voice to those who are confused as to how this can be anything but a bad idea.

Only thing I can think of is that LL didn't feel the Jira was reflecting well on their public image (too many open bugs, or old problems that were never fixed) and decided it was better to hide the system then fix the system. This turtling is also visible by how we used to get blog posts explaining what happened when an outage happened and what they're doing to fix it, while now they're just saying they had some "unschedule maintenance" with absolutely no details.

No news is only good news when the news doesn't actually exist, not when it's censored.