Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current Restore this Version View Page History

« Previous Version 12 Next »

Release 6.3.0 Scope

  1. Simplify installation of inQuiry (as per of Sunbird ED)

  2. QuML Spec for the following attributes

    1. interactionTypes

    2. interactions

  3. Primary Category based configuration for attribute behaviour

  4. POC - Primary Category based configuration for attribute behaviour [1 day]

Release 6.2.0 Scope

  1. CSP changes [3 days - dev + testing]

  2. Error traceability [Finalise the strategy and during the testing cycle] [? days]

    1. Proper error codes and error messages

    2. Add request id

    3. Error Logging

  3. Backend unit test cases - Improving the coverage [1 week]

  4. Analyse [Editor, Player] - [Confirm on the pending tasks Sajesh Kayyath ]:

    1. Streamline BB code/ remove deprecated code etc.

  5. NPM package release automation (Needs DevOps support)

  6. Analyse how APIs errors are consumed by Editor & Player

    1. List down all the error messages

    2. Review & refactor the error messages

  7. Documentation updates [Needs clarity Sajesh Kayyath Gauraw Kumar ]

    1. Configurations of contributed features/properties

  8. Demystification of SB BB & documentation

Release 6.1.0 Scope

  1. Migration Script [2.5 weeks]

    1. Approach [1-2 days]

    2. QuML Migrator [1 week]

    3. Event generator [3 days]

    4. Re-publish [3 days]

  2. Backend unit test cases - Improving the coverage [1 week]

  3. POC - Primary Category based configuration for attribute behaviour [1 day]

  4. FTB Implementation

    1. Discuss in the working group connect

    2. Catchup with Mathew / other relevant folks.

  5. Analyse [Editor, Player] :

    1. Streamline BB code/ remove deprecated code etc. to ensure a clean offering that is fully understood by the team that owns it.

      1. Code review, remove unused code

        1. Check for any code inspection tool?

    2. Hard coding of content organisation and target frameworks in editors and other components to point to a specific framework has to be removed

  6. Web component to Editor & Player

  7. Documentation updates

    1. Configurations of contributed features/properties

  8. NPM package release automation (Needs DevOps support)

    1. Finalise the strategy

    2. Implementation design

  9. Analyse how APIs errors are consumed by Editor & Player

    1. Backend is sending API error and Editor & Player are displaying different error messeges

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

  1. QuML Compliance changes

  2. FTB Implementation

  3. Pending bugs

  4. Editor Web component

Release 5.6.0 Scope

  1. inQuiry MS > Schema deployment - documentation

    1. Update the steps in confluence for future reference

    2. What are the list configs, we need list in confluence/ microsite for reference

    3. How to deploy steps document. So, anyone from the team can deploy in the absence of core member.

    4. List Jira tickets, create Confluence pages, and update the microsite

  2. QuML Compliance

  3. FTB Design

  4. Question reusability: Create within a QueSet, use in another (Visibility private (P3), Old ECML (P3)). Review question lifecycle.

  5. Attach or record audio (across all question types)

  6. Functional Testing Automation: Today the coverage is x/total APIs and x%. We want to achieve >90% coverage across all APIs.

  7. Performance Testing & Benchmarking: Today we don’t know this. We want to achieve <5% error rate. Expected scale: 25k TPS.

  8. Health monitoring: Today there is no health monitoring, we want to provide monitor-ability.

  9. Debuggability: FAQs to help adopters to debug any issues.

  10. Installation