Document release process

[ferristocrat]

Motivation/Why?

We want to document the release process so we can make it consistent and repeatable.

What needs to be done?

Work with @andriikotko to understand how the release process has been executed in the past.

Acceptance Criteria

• Create an issue template with a tasklist-based checklist that outlines what needs to be done to complete the release process, including what tests need to be run and what documentation needs updating
• (optional) Identify opportunities for automation

[neo-cypher]

Tasks:

• [ ] Pull Request template
• [ ] Change log generation
• [x] Document deployment process
• [ ] Gap Analysis: Test Coverage
• [x] Basic Test Plan

[neo-cypher]

Basic Test Plan: Items Under Test (IUT)

• [x] Smoke Tests:
• • [x] check if upload works
• • [x] check if download works
• • [x] check if file preview works
• • [x] generate link and check if linksharing works
• • [ ] check linksharing links in all the places it might be generated and if it works
• • [x] check folder sharing- - [ ]
• • [x] check if user has no access to folders he wasn’t shared - e.g. create subfolder and give access to it demo/111/222 -> give access to 222 -> check has no access to root folder and data in it (with UI it technically possible)

[amwolff]

Any news on the PR with the template @neo-cypher? Do you need any help?

[neo-cypher]

Almost complete. Should be sending out a request for review here shortly.