Sprint Wrap Up
Attendees
General
- Indicates who took minutes -
- Google-hangout at:
Agenda
- Meta analysis of sprint process
- Summarize final state
- Walk through in-process and unstarted tickets
- Teeing up for next sprint
Minutes
Adam
- Would have liked to have Chris more involved
- Difficult to make estimates, but regular commits helped
- HTTP integration tests need help
- Only checking for non-null
- It would be good to create specific tickets for integration tests
- Helpful to write expectations on wiki: basing integration tests on this
- Document API in detail on wiki, with examples
- We could do better at developing a framework for testing
- Testing apparatus that can be expected would be useful
- Example, inspecting RDF responses
- Process
- Consensus on testing patterns
- Document test patterns on wiki
- End up with good examples in code
Frank
- Blocked by admins at SCC cluster
- Learned a bit about AWS
- AWS exceptions happen everytime with ELB over cluster
- No errors from localhost on single node
- Process has not made enough progress to make suggestions moving forward
Greg
- Scott discovered a delete issue
- Deleting children needs to be iterated
- Will be creating tickets for deletes
- Enjoyed working with Scott, new person on the team writing tests
- If you care enough about F4, acceptance testing is a minimum
- Would be helpful to inform local team of need for focus on sprint
Osman
- Finishing javadoc ticket
- Useful to have an "overview.html" to top-level modules
- Working on cluster tests in the background
- Would be good to document scripts/tests for automated cluster tests
- Frank's benchtool is helpful
- Wiki pages with specific results is helpful
- Having standing cluster for test would be helpful
- Institutional distractions are becoming less
Scott
- Finished delete tests
- Documentation is wrapped up
- Will be continuing performance testing tasks
- Spent beginning of sprint getting up to speed
- Worked on 3.7 patch
- Sprint reflection
- Did not get involved in coding until ~2pm
- Would use the mornings to ramp on documentation, research, etc
- Sprints are somewhat exhausting
- Felt reluctant to ping others for Java tips
- IRC can be distracting
- Integration test documentation and tooling would be helpful
- Standups may could be more trim (every other day?)
- The role of documenting and fielding questions would be useful
Actions
{"serverDuration": 78, "requestCorrelationId": "5b63679c17298137"}