Release cycle
A software release cycle is the process through which software is developed, tested, and released to users. It ensures that software is delivered in a structured and reliable manner, involving planning, development, testing, and deployment. The cycle helps manage the progression of software from initial concept to final release, ensuring quality and functionality.
Release notes
A release note is a technical document that announces the updates to a product. It is published alongside new or updated software and details the technical features of the product. For every build releases, these release notes provide end-users with a brief summary of the product itself. Release notes are distributed with software products, sometimes when the product is still in the development or test state.
Software build release frequency
The frequency of updating release notes depends on product’s release cycle and the nature of the updates.
See the table below for release frequency:
Product |
Build Release Frequency |
Build Release Type |
Build Release Authority |
|
Internal Build |
Customer Build |
|||
Flux |
Weekly once |
Every monday |
7th of every month |
Arvind |
Praxis |
Weekly once |
Every tuesday |
Last tuesday of every month |
Rajesh Kumar |
Right Angle |
Monthly twice |
End of the month |
15th of every month |
Dinesh. S |
Vulcan |
Monthly once |
24th of every month |
Priyarathna. S |
|
Document request notification
The Product Owners selects and releases an effective build for the client. Based on the release notes of this build, the Product Owners then adds a 'DocUpdate' tag to the product cases in FogBugz to notify the documentation team.