Page History

...

Sprint planning

Tuesday 2013-10-22

1. Eric
   
   • created tickets
2. Frank
   
   • Went to dentist
   • Post exception on IRC gist
   • SCC benchmark ticket is broad-scope
     + create new ticket for benchmarking
3. Greg
   
   • Working roles
     xx + move content into Futures
4. Osman
   
   • Scripted integration tests
   • Adding waits seems to help
   • Working with wait between 5 and 2.5 seconds
   • Ran Frank's benchmarks
     xx + add ticket for Osman to update wiki, results of benchmarks
5. Scott
   
   • Created roles/permissions matrix
   • Updating wiki documentation
   • Will be working on integration tests
   • Worked with Ben on F3 patch
   • Will finish review of F3 today
6. Adam
   
   • Waiting for code review to complete
     xx + Push Adam's update (2 branches)
   • Jena datasets are prevalent
   • Adding triples to models does not throw exceptions
     
     • problems are owe RDF branch
   • New iterator
     
     • You can pull on it until error is hit
     • You can pull all of the triples, and errors are set on another iterator
     • Agreed: Or iterator can throw ex but still be available
     • Permissions exceptions will be logged
   
   
   1. Implementation discussion
      
      • The RDF source will produce triples. If it throws an exception, it's up to the client to decide what to do about that. The iterator will continue to work and produce triples until it is genuinely exhausted. We didn't finalize what to do at the HTTP layer, because Frank, Scott, and Greg discovered some subtleties and different possibilities for useful behavior there.

...