Release Management

Release management is the process of managing, planning, scheduling and controlling a software build through different stages and environments; including testing and deploying software releases.

For example, an e-commerce company named XYZ may be adding a new web page to sell bikes online. Once the development team at XYZ writes the code for the new web page, it may need to be tested by multiple test teams and across different environments, before it is finally deployed in Production for usage by end users or customers. The company XYZ might be hosting their e-portal on Amazon EC2 Cloud servers. The release process will ensure that the code written by the development team is built using some build tool (such as MS Build by Microsoft, Ant scripts etc.,) which are compatible with Amazon EC2 and are unit tested. Once the testing of the built packet is completed and passed, it can be deployed in environments for testing or live usage.

Therefore, in a way, the Release Management process is a critical bridge between Development and Testing/Production. It is an intermediate step to ensure the integrity of the code and to guarantee that the deployed code will work as per the expectations of stakeholders.

The main activities involved in release management are:

The release management concepts the following scenario will be applied.

  • Team Lead
  • Tester
  • Document Writer
  • Release Manager

Team Lead:

A team leader is responsible for guiding a group of employees as they complete a project. They are responsible for implementing a timeline their team will use to reach its end goal. Some of the ways team leaders ensure they reach their goals is by delegating tasks to their members, including themselves.

If you are in Team Lead role you should be in the cidaas release management groups with role of LEAD until you cannot able to access release management.

Tester:

The roles and responsibilities for a usability software tester are as follows: A Software Tester is responsible for designing testing scenarios for usability testing. He is responsible for conducting the testing, thereafter analyze the results and then submit his observations to the development team.

If you are in Tester role you should be in the cidaas release management groups with role of TESTER. until you cannot able to access release management.

Document Writer:

Release notes is a document, which is released as part of the final build that contains new enhancements that went in as part of that release and also the known issues of that build.

Release Notes are usually written by technical writers which are communication documents shared with clients.

If you are in Document Writer role you should be in the cidaas release management groups with role of DOCUMENT_WRITER. until you cannot able to access release management.

Release Manager:

Release management is the process of managing, planning, scheduling and controlling a software build through different stages and environments; including testing and deploying software releases.

If you are in Release Manager role you should be in the cidaas release management groups with role of RELEASE_MANAGER. until you cannot able to access release management.

If all the development process done and ready for production state the team lead should schedule release using through the release management

Go to cidaas release management dashboard -> Release Management

Create New Release:

The team leads only to initiate new release logs for the clients.

Release Name: The release name through to find out which release go for the clients.

Release Version: developer and client can easy to find out the release logs.

Release Types: The release type we can setup in three ways.

  • Consent

    If your setup release type consent means if any release, go to client they will get consent for allow the bug fixes and new features to your business.

    We can mentioned postpone period of the release date within 10 days

  • Force

  • Background

Release Notes: Here what are the changes bugfixes and features are release to the clients those kinds of information we should describe in the release notes.

Tenants:

Which client we are going to release the above features and bugfixes based on the tenant. Here will list out who are all our clients list out in the dropdown box we can give release to multiple clients.

Select Tags:

A changelog is a log or record of all notable changes made to a project.

  • Bug fixes One of the most common applications of bug fixes is a technical protocol that is used to identify several types of bugs, so they may be effectively resolved.

  • Breaking Changes A change in one part of a software system that potentially causes other components to fail; occurs most often in shared libraries of code used by multiple applications Not possible to fix old entries without a breaking change, so remap old to new in import lib.

Target Side:

Which side we are going to be release to the client whether the UI (User Interface) side or Service side

Note Type: We can specify the note type as two ways

  • Public

    If you select public in the sense these releases can view test/production which mean any one can view your changes and features

  • Internal

    If you select internal means these releases can view your changes and features only the internal developer and tester.

The + Plus button refer we can specify multiple release notes to the single release for example in this release I am given new features and bugfixes. In that time, we can have maintained release notes for separate using the Plus button.

If any we already create testing steps on the wiki page those links here we need to update. Its help full for tester can test very efficiently.

Testing Steps:

Resource Compatibility Version:

We can mention resource compatibility for SDK version for this release support.

After that click create release button now successfully create release logs.

Once it is done that create status will be changed into submitted now successfully logs enable to tester for testing our code.

Note: when team lead review the release after that only will go for testing.

View Release Status:

Release Manager and tester and team lead, and document writer can able to find out the release status from this below table.

Release Name:

The release name through find out which release on going to be release in production.

Version:

Which version going to be release and developer and client they can easy to predict whats new and bug fixed in this release.

Release Types:

The release types are categories into three types

  1. Consent
  2. Background
  3. Force If you enabled this release type in this release that time, ask to your client these releases are you going to accept or not.

Release Date:

Which date we are going release to the clients.

Requested By:

A team lead is responsible for guiding a group of employees as they complete a project and request to ready for test.

Tested By:

He is responsible for conducting the testing, thereafter analyze the results and then submit his observations to the development team.

Released By:

Release manager is responsible for releasing, managing, planning, scheduling and controlling a software build through various stages and environments.

Reviewed By:

Release notes is a document, which is released as part of the final build that contains new enhancements that went in as part of that release and the known issues of that build.

Status:

We can find out the status of releases from the below mentioned state.

1 . Submitted: development team and test team and optionally document writer for checking release logs after confirming every think it’s ready for moving production means release manager accept those release changes and features that time consider as submitted.

2 . Created: When team lead after complete project now ready for testing to go for production that time create on release.

3 . Accepted: Once accept that tester for my releases for further move to production that time comes like accepted.

4 . Released: Before going production, the release manager to give request to document writer for reviewing the release logs.

5 . Review: If document writer verified release logs every think fine means again send to release manager for review release logs notification. that time consider label as review

Just click review text on the table that will redirect to submit our release that time only further release step will be move on to next stage

If I have tester role in my account (TESTER) accept team lead given release request. Once he accepts release the status will comes under review.

Here the tester can click that review text that will open team lead created release notes and some release related information are showed here.

After tester test our code for ready to clients means before how many percentage tests completed we should specified on the percentage slider bar. They can able to allow give comment for the testing. if any bugs on code tester can also reject release response and automatically send back to team lead and team lead check the issues and correct it and again send submit release request to tester again tester test the code if everythink working properly tester accept the release request will send to release manager.

Release Manager responsible for release the changes and new features to the client after approved tester and document writer.

Here release manager can check the testing coverage and release logs ,which release whether internal or public if any changes on the release logs release manager can also able to change or otherwise release manager can send back to document writer.

Document writer verify and correct the release notes again send back to release manager again finalize and release to the client.

The release manager again need to update verify the relesae notes if everythink ok approved to release those features and changes to the particular client.

Notes: check the Status RELEASED which means successfully released on the particular mentioned client environmnet.

After that client will get notification on their admin dashboard. For more information update management page.

results matching ""

    No results matching ""