Road to 2.0.0

[fschade]

Abstract

This issue lists all open and needed steps on the road to 2.0.0.
The roadmap could grow over time, no concrete release date so far.

Roadmap (1st [X] merged, 2nd [X] pr exists):

• 2.0.0-rc.1
  • [X] make client use modern apis for ocis
  • [X] add surf test
  • [X] add oc share-upload-rename test
  • [X] rely on k6 only, get rid of cdperf bash script
• 2.0.0-rc.2
  • [X] convert to mono repo
  • [X] add repo helper packages to build, lint, watch and setup tsconfig for the project more easy
  • [X] add test development toolkit package which abstracts away the client, utils and enpoints
  • [X] create dedicated tests package and ship the artifacts as part of it.
  • [X] add koko login test and depending apis
  • [X] add koko file tree navigation test and depending apis
  • [X] add koko upload delete test and depending apis
  • [X] add koko upload download test and depending apis
  • [X] add koko create and rename folder test and depending apis
  • [X] add showcase test to demonstrate tdk capabilities
  • [X] create readme for each test to provide information what the test does and how to use it
• 2.0.0-rc.3
  • [X] add koko user group search and share test and depending apis
  • [X] add koko create space test and depending apis
  • [X] add koko add remove user share test and depending apis
  • [X] add koko search for filename test and depending apis
• 2.0.0-rc.4
  • [X] cleanup tdk endpoints, the api's for oCis, occ and nc must be aligned
  • [X] cleanup tdk client, the api's for oCis, occ and nc must be aligned
  • [X] cleanup tdk utils
  • [X] cleanup tdk auth
  • [X] add basic tdk tests (vitest)
• 2.0.0-rc.5
  • [x] refactor auth adapters and add keycloak compatible adapter
    OIDC auth does not use /.well-known/openid-configuration #42
  • [x] automate doc gen (tsdoc, md, ...)
  • [x] introduce snipped's or workflow package (abstract away complex tasks like tag find or create, ...)
  • [x] review and cleanup written tests
  • [x] add ability to run k6 tests for only-office (websockets, ...)
    https://github.com/ONLYOFFICE/document-server-stress-testing/tree/develop/K6/7.3
  • add test to simulate ownCloud sync client
• later
  • [ ] automate changelog gen
  • [ ] find solution to not rely on polling to find out if a resource is ready to use or not (ocis search indexing, ocis async uploads)
  • [ ] add custom xk6 package to be able to share big binary data between vu's, similar like k6 sharedArray but for bin data
  • [ ] use TUS for ocis file uploads
    Upload should use the TUS protocol #43
  • ...

Appendix

not sure what else is needed since the testing starts in the near future and we have to see whats missing or not... roadmap could extend depending on the results.

[mmattel]

just some thinking, should we align the version number to ocis, means we have 3.0 on the horizon?

[fschade]

We could, but i see no relation between ocis and cdperf… i don’t care much about Version numbers as Long as we follow semver style