Date: Monday 12th Nov 2012
Time: 14:00-15:00 CET, 13:00-14:00 GMT
Who's there?: Sara, Sion, Jerry, Patrik, Jakob, Rick, Nick, Matthijs
Project action points
|Sara||Plan resourcing on 2.0 and how we tackle the regression testing backlog.||IN PROGRESS||...|
|Sara/Jerry||Work on initial draft for benchmarking setups based on feedback from developer workshop and board.||OPEN||...|
|Sara||Take a pass through JIRA to tidy up duplicates/unassigned issues. Send changes for review if required. Split the future release into a backlog and an icebox. Make sure all features have subtasks to track developer testing and documentation.||OPEN||...|
|Jerry||Look at opening up the OpenDNSSEC project up to all users if we can restrict the privileges for 'external' users correctly. Then we could stop using the SUPPORT project. Need a test environment to work on this.||OPEN||...|
|Sara||Follow up with SURFNet on hosting of Sun servers. Roland is investigating||IN PROGRESS||...|
Nothing changed here.
|Matthijs||Work on DNS Adapter tests. (OPENDNSSEC-172). Work on IXFR stress tests using Sion's scripts.|
Matthijs is working on a test, Jenkins daily test case style. First with few updates, hasn't got that working. Working on that tomorrow, hoping to finish it then.
No change in DNS Adapter requirement test coverage, still need to do IXFR out. Maybe can be finished this week, otherwise next week.
Sara asks Nick for knowledge on validns to do testing with an external tool. Nick has some knowledge, because SIDN is using the tool.
Action Point Sara and Nick and Matthijs: chat on Wednesday, 10:15
|Sion||Check sightings of duplicate RR sigs.|
Action Point Sion: going to test the fix from Matthijs.
|Matthijs||OPENDNSSEC-346: BIND interop test.|
Matthijs is working on this, assigning action to Matthijs.
|Sara||Write a page to capture the workflow of how to use Jenkins. Test case policy (check list for adding new tests) Testing - details build schedule (e.g. smoke/daily/weekly).|
Sara has been working on this and there will be something sent out to review soon to the developer list.
|Sara||Correct statement on the wiki page. Compose an email to propose this (and ask feedback) from developers and architecture board; possibly raise it on the user's list as well. Also consider the versioning convention currently used. Sara has done the wiki page, but still has to send an e-mail.||IN PROGRESS||...|