Release 6.2.0 Scope
Error traceability
Proper error codes and error messages
Error Logging
Simplify installation of inQuiry (as per of Sunbird ED)
QuML Spec for the following attributes
interactionTypes
interactions
Primary Category based configuration for attribute behaviour
Release 6.1.0 Scope
Migration Script [2.5 weeks]
Approach [1-2 days]
QuML Migrator [1 week]
Event generator [3 days]
Re-publish [3 days]
Backend unit test cases - Improving the coverage [1 week]
POC - Primary Category based configuration for attribute behaviour [1 day]
FTB Implementation
Discuss in the working group connect
Catchup with Mathew / other relevant folks.
Analyse [Editor, Player] :
Streamline BB code/ remove deprecated code etc. to ensure a clean offering that is fully understood by the team that owns it.
Code review, remove unused code
Check for any code inspection tool?
Hard coding of content organisation and target frameworks in editors and other components to point to a specific framework has to be removed
Web component to Editor & PlayerDocumentation updates
Configurations of contributed features/properties
NPM package release automation (Needs DevOps support)
Finalise the strategy
Pending Discussion
Ed Team
Request traceability - Expectation / priority / proposed design ?
Simplify inQuiry Installation
Feature parity b/w ECML & QuML
DC
Finalise the strategy for NPM package release automation
Release 5.7.0 Scope
QuML Compliance changes
FTB Implementation
Pending bugs
Editor Web component
Release 5.6.0 Scope
inQuiry MS > Schema deployment - documentation
Update the steps in confluence for future reference
What are the list configs, we need list in confluence/ microsite for reference
How to deploy steps document. So, anyone from the team can deploy in the absence of core member.
List Jira tickets, create Confluence pages, and update the microsite
QuML Compliance
FTB Design
Question reusability: Create within a QueSet, use in another (Visibility private (P3), Old ECML (P3)). Review question lifecycle.
Attach or record audio (across all question types)
Functional Testing Automation: Today the coverage is x/total APIs and x%. We want to achieve >90% coverage across all APIs.
Performance Testing & Benchmarking: Today we don’t know this. We want to achieve <5% error rate. Expected scale: 25k TPS.
Health monitoring: Today there is no health monitoring, we want to provide monitor-ability.
Debuggability: FAQs to help adopters to debug any issues.
Installation
Add Comment