John, Dan and Peter
- Needs to update in CVS as soon as code is fixed - John
- All numbered builds (like 2.46) are checked in.
- Progress checkins also - a significant amount of work done, but not necessarily a working version; should compile.
- Bottom line a checkin every couple of days.
- Bug reports to Bugzilla
- Currently ~75 bugs and ~75 features. May be down to 40 now.
- We've agreed that John will enter any bug encountered that:
- He does not immediately (next several hours) plan to address.
- He will determine to the extent possible if the bug is in the ODC or in the incoming OPeNDAP
data stream. - Former goes onto ODC bug list.
- Latter goes onto a data set bug list.
- Release Candidate for ODC that's means something on page 1 of the OPeNDAP page - John with James and Dan
- Clean up the ODC download page so that it works like the Matlab client page - John with
James
- Move tutorial to OPeNDAP web pages. - John with James.
- Target user groups for the ODC.
- The ODC as an aid to installers of data servers.
- Packaging the ODC with server stuff - James
- Tutorial for how to use it in this mode - John
- Setting up examples on our machine.
- Entry in the READ.ME documentation that comes with the server.
- As a data discovery tool for Matlab
- Tutorial for how to use it with Matlab to get the data
- Packaging with loaddods
- Entry on the ODC web page
- Excel and Access
- Ferret
- Paper on the ODC with section(s) relevant to 6.
- Feedback separate tab on the top page next to help tab.
- Two tabs
- Bugs; i.e., a failure either of the program or in the aquisition of data
- Comments; i.e., program sucks, suggested new features,...
- Report goes to one of two different places in Bugzilla going to John and Peter.