Snowstorm Daily Scrum Archive/11092010

Open Source Quick Links

• How To Propose A Viewer Feature
• How To Submit A Viewer Change
• Integration & Release Processes
• Feedback Portal
• Github

Tuesday, November 9, 2010

General Notes

---

• Merge Monkey of the Day: Oz
• If an issue is “In Progress” it should have a time estimate!
• Please remember - when merging your fixes into Beta, you must also pull them into viewer-development immediately after
• If you take a bug off any of the bug queues, please move it to the current sprint.

Team Status

---

Merov Linden

---

PAST

• STORM-105: Perf gathering: more Vadim comments and tweaks, committed changes to dev repo, waiting for LL internal team to review to push to viewer-development
• STORM-150: More reading, built all as is (works), extracted what we need for a simple port, thinking about a clean architecture so to make that easy to build for all
• Discussed named branches strategies with CG

FUTURE

• STORM-150: continue
• STORM-104 : kdu upgrade: commit the static linking changes to dev repo

IMPEDIMENTS

• None

Oz Linden

---

PAST

• Assorted wiki updates
• Pulled more issues from integration queue, and many back from beta
• Started working on library upgrade issue (STORM-312 and STORM-453)
• Reviewed autobuild for open source issues

FUTURE

• Continue merge monkey (nothing currently queued)
• Continue working on library upgrade issues

IMPEDIMENTS

• none

Q Linden

---

PAST

• Beta 3 monitoring
• Looking at Notifications prefs tab; why is it broken?
• Prefs discussions
• Display names discussions
• SH-412 monitoring
• STORM-102 comments
• Short day

FUTURE

• More Notifications prefs
• Beta 3
• Triage
• Planning
• Watchdog timer

IMPEDIMENTS

• none

Esbee Linden

---

PAST

• Triage
• Prefs subtasks being created
• Discussion around STORM-560, STORM-102
• Planning/coordination of Viewer 2.3 beta & release
• Worked on prim alignment tool design doc
• Display Names discussion

FUTURE

• Finish creating subtasks for Preferences cleanup
• Work on design doc for prim alignment
• VWR Triage
• Prioritize tickets for team and queue up more work
• Planning/coordination of Viewer 2.3 beta & release

IMPEDIMENTS

• none

Paul ProductEngine

---

PAST

• BUG STORM-535 PLEASE allow adjustable transparency of "Nearby Chat" window, Chat History and Chat "Toasts" in Viewer 2.0!
  • Fixed. Everything seems to work properly. Tomorrow will carefully test and send for a review. Estimate ~ 1 hour.

FUTURE

• Finish STORM-535 PLEASE allow adjustable transparency of "Nearby Chat" window, Chat History and Chat "Toasts" in Viewer 2.0!
• Other tickets by priority

IMPEDIMENTS

• none

Seth Productengine

---

PAST

• BUG (STORM-550) LLDir::getNextFileInDir fails for some complex wildcard combinations
  • WIP. Compiled LLDir unit tests with platform specific implementations. Waiting for tests by Oz to be merged into viewer-development to research test cases.
• BUG (STORM-559) [crashhunters] LLSideTray::showPanel(std::basic_string,std::allocator > const &,LLSD const &) [secondlife-bin llsidetray.cpp]
  • Fixed.
• BUG (STORM-577) Classifieds description limited to 64 characters
  • Fix needs to be discussed.

FUTURE

• BUG (STORM-574) [crashhunters] crash at LLView::handleVisibilityChange(int) [secondlife-bin llview.cpp]

IMPEDIMENTS

• none

Andrew Productengine

---

PAST

• Normal bug STORM-320 (Script Editor in Viewer 2.0+ "tabs" incorrectly)
  • Investigated further. Problem is with mLineInfoList vector, elements to which are added in LLtextbase::reflow(). It is called in every draw() of any textbox, so it is almost impossible to properly debug code there. I tried to reproduce the bug on other builds to find out the approximate range of revisions where it could appear. But I couldn't reproduce it anywhere except my latest development build. Even tester's build as fresh as my own doesn't seem to have this problem.
  • Estimate- if nothing is clear after a couple of hours, I suppose it may be better to put investigation results into ticket and switch to issues with higher priority, because this issue is almost unreproducible, and will be quite hard to fix. Vadim, if you agree on this, please assign some other Sprint 7 issue(s) on me.

FUTURE

• STORM-320

IMPEDIMENTS

• none

Vadim Productengine

---

PAST

• Task STORM-105 (Create a Performance Data Tracking system):


Completed review.

• STORM-52 (Hook up external script editor).

In progress. ETA: 2d.

FUTURE

• Story STORM-52 (Hook up external script editor).

IMPEDIMENTS

• none

Andrey Productengine

---

PAST

• done smoke and integrity tests against 2.3.0 Beta3 214088
• smoke tests have been failed by STORM-561

FUTURE

• re-run smoke & integrity on new beta build and proceed with regression testing (?)

IMPEDIMENTS

• none