Notes for 4/14/09
- Summary of Issues
- How we were testing
- Built in GWT browser which has Tomcat built in and deploys
- Deployment
- Include instructions about GWT
- Project
- Few things are not stored
- Need plug-in and GWT Library
- How to Use instructions will be more throughout
- Could be combined into one set of instructions
- If you have war file go to step blah, otherwise continue
- For release 2 give it to someone not familiar with project and make sure they can use the system.
- How are we tracking which use case goes into which release?
- Our original structure did not involve UI
- We had focused on Erika’s email to decide which use cases were in the scope of Release 2.
- We are still on track to finish Release 2.
- Locking
- Functionality is there, just not used there
- Release 2
- Conditionals
- Fixing broken Use cases
- D-12
- If no root file it used to throw and error
- Also if no xml file it will throw an error
- Easy fix, but have not had time to change
- Java Docs are in the Java Docs folder
- J-Unit
- Two result in errors
- This is a pathname problem
- Are we going to have a proof?
- Can we still get IE 6
- Try oldversion.com
- Downloads.com
- What bout IE tab in fire fox
- Can result in new unique problems
- If we can not get IE 6
- Test in fire fox 3 and IE 7
- Decisions
- For future send out problems and communicate early and give out more notice when we know
- Change Deployment instructions
- Add information about locking.
- Primary version they use is 6
- Action Items (w/ person responsible and dues dates)
- Poster close to finalized on Friday
- Try and get IE 6
- New deployment instructions for next release
- Update documentation
- Update schedule
- Start Technical Report