Release management

Estimated reading: 1 minute 417 views

Release management is our process to introduce new versions of Cellosign. Typical release include:

We are releasing approximately 6 new versions of Cellosign every year. That is every other month.

What a release cycle looks like?

Each release includes the following steps and thresholds. Each cycle is a two months lapse time starting from step 2 to step 7.

Step#	Step	Description	Lapse time
1	Assemble	Collect and prioritize release requirements. Bugs and security issues prioritized higher
2	Documentation	Build supporting documentation for development and testing	1 week
3	Requirements freeze	A stage we are not receiving new requirements to release unless it’s a critical bug or security related	0
4	Development	Development of release content	3 weeks
5	Internal test cycles	Including: Regression, Automated and manual tests for bug and new features, security, compliance and vulnerabilities test	3 weeks
6	Beta release	Releasing beta version to cloud pre-production environment were our clients may also conduct acceptance testing and report us findings.	1 week
7	Production	Releasing version to shared cloud production environment	0