Coordinates
250 East Wisconsin Avenue, 18th Floor
July 22: 12:30 - 17:00
July 23: 09:00 - 17:00
July 24: 09:00 - 12:00
Physics Building 13:00 - 17:00
Agenda
- Review 0.9.4 open tickets with intent to tag
- Review UX/UI priorities
- Scalability issues
- Set up demo instance with large data set for testing?
- 1.0.0 issue triage
- Identify blockers vs "nice to have"
- Target end of August
- Identify blockers vs "nice to have"
- Proxy IdP / Embedded Attribute Authority
- Reporting
- Requires reporting infrastructure
- Not 1.0.0
- Report request examples:
- CSV output of first name, last name, email, for a COU in CO – to send a report to COU admin
- Reports that operate over people, groups, cous
- Recommendations to deployers for setting up a QA tier
- Project QA and Release Planning strategy (CO-975)
- Release Candidates
- Script to follow when doing acceptance testing
- Selenium demonstration, choices
- JIRA management of bugfix releases (eg: 1.0.1)
- Strategy for managing different versions of documentation (wiki; ie: functionality for 0.9.3 vs 1.0.0)
- Notes / Assertions:
Will move to semantic versioning
Will move to release candidates - full releases depend on QA / acceptance testing
Version planning begins upon completion of current version and depends on funding sources and other constraints
Version documentation: label versions as appropriate (and with discipline); may be driven by outside documentation requirements
- See also: https://bugs.internet2.edu/jira/browse/CO-975
- Release Candidates
- August Albany f2f?
- TechEx logistics?
Action Items
- Scott to complete CO-1045 by Monday, July 27.
- 0.9.4 tag by Monday, July 27
- Heather to review and revise setting up a QA tier with an eye towards language suited for VOs that do not have as much operations experience as say an NREN data shop.