List view

• RC 2

  1. All concerns closed 2. Rigorous stress testing

  No due date
  0% complete0 open0 closed

• RC 1

  Release Candidate 1 should include 1. All bugs closed 2. Tested to be stable against many simultaneous requests from many connected clients at once 3. Functioning CRUD enabled Web based UI

  No due date
  0% complete0 open0 closed

• Beta 2

  Beta 2 should include 1. Rest API 2. All Commands completed 3. Connection pool manager smoothened out 4. Has at least a proof of concept connector 5. Unit Tests 6. Integration Tests

  No due date
  0% complete0 open0 closed

• Beta 1

  The first beta includes 1. The core binary connection port 2. All essential commands 3. Docker deliverable 4. Binary deliverable 5. Development flow streamlined 6. DevOps pipelines for CI/CD 7. GitHub Pages microsite 8. Stable ordinary execution

  No due date

  •14/14 issues closed
  100% complete0 open14 closed

• MVP

  The road to the minimum viable product is simple: the thing should be usable by someone. To accomplish this, Echo needs to have all core commands built and executable without exception or crash, and the results are accomplished in an expected manner. Once this has been accomplished, a cli connector of some kind can be written to interact with the server instead of relying on netcat for testing

  No due date

  •0/1 issues closed
  0% complete1 open0 closed