This is promising news : Kelly Linden reported that he expects the fix to the C:SI kick bug to be deployed in the near future (or now, depending on the order of the rolling update, I guess), and has marked the Jira issue as [Resolved] and [Fixed] and deployed in the latest server-side code rollout V1.21 :
kelly linden - 29/Apr/08 11:31 AM
This issue should be fixed in the current simulator version (1.21)
I’m not able to verify this at the moment (durned work making me work), but I’d love it if anyone could verify this and let me know
[UPDATE]
False alarm
Kelly Linden said…
Resolution: (was: Fixed)
Status: Fix Pending (was: Resolved)Arg, oops!! This is NOT fixed in 1.21, but will be in 1.22 (the next version we release, I hope).
Sorry Robby! This got caught in some pjira clean up I was doing. I thought I re-read all the issues to only get the ones fixed in 1.21, but not well enough I guess.
Popularity: 35% [?]






Whats the difference between jira and pjira ?
I have no idea… I call it JIRA because that’s how I was originally introduced to it as a product (before I even found out about Second Life), but it could very well be that pjira is more correct.
or maybe pjira is just ‘public’ jira? It is, like so much of what the Lindens do and say, a mystery
I would guess pjira is just “public jira”. I guess there’s a “private jira” that the Lindens use internally. And then possibly a “protected jira” that is available to Lindens and any child companies of Linden Lab…ok, sorry, programming joke.
Colin’s latest blog post is : Monkey Karate
Then why is there no fjira (Friend jira or Final jira) or sjira (static jira) ???
Haha, final jira. That would be useful.
Colin’s latest blog post is : Monkey Karate
what about Fjira… Failed jira?
That might work too, haha. I can’t call it a complete and total failure, though, since we did convince them to look into and eventually fix a couple of things.
Having said that, it’s clearly not a great solution. I don’t know what else I’d suggest for The Lab to use, though. I’ve looked at an awfully large number of issue tracking systems over the years and even the very best ones have major failings. And on top of that, if the entire development team gets to cherry-pick their priorities (as is the case at The Lab), there’s not an issue tracking system in the world that can make it easier to get things done.
True but there is most deffanetly gotta be a better way to prioritize issues.