1 / 11

Software Configuration Management Guidelines for Release Man

VIETTEL Corporation. Software Configuration Management Guidelines for Release Man. Revision History. Contents. Preparing before software release Checking out and compiling Basic Test Merge to trunk Make a release note Announce to everyone. Preparing before software release.

gella
Download Presentation

Software Configuration Management Guidelines for Release Man

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. VIETTEL Corporation Software Configuration Management Guidelines for Release Man

  2. Revision History

  3. Contents Preparing before software release Checking out and compiling Basic Test Merge to trunk Make a release note Announce to everyone

  4. Preparing before software release • Send reminder e-mail to developer to let him know the target of the next release one day before • Ask him to send check-in e-mail to you to describe his changing (the template as following) Check-in mail template(PJ member -> Build administrator) Reporter: Your name (Developer Name) Revision: r1024 Bug number (or new features):‏ Description:

  5. Check out and compile • Check out source code from the “working” folder on our server svn co http://server:8080/svn/VT1000/braches/working • Turn on DEBUG mode in the <build_id>.cmd file by set the value of USE_NO_DEBUG=no • Execute commands to compile source code • Open command windows • Execute RVCT221P593ECMake.bat • Execute <build_id>.cmd • Flash new image to the phone

  6. Basic Test • Execute all the test cases that mentioned in the release plan document (not only test cases for the current release but also all test cases that belongs to previous releases) • In case, all test cases are pass. You can go straight to the next step (Merge to trunk) • In case, some test cases are fail. You must talk to developer to make sure all his source code are available on server. If the problem can not be solved, you must remove related features (or bugs) out of the current release.

  7. Merge to trunk • After all test cases are pass. You can merge new source to trunk (You must do this step carefully because it can raise a lot of problem) • Merge all new sources code into trunk folder. • Update software version in AMSS • Open services\task\mobile.c • Set NOTICE_TYPE mob_sw_rev[] = “RELEASE_ID”

  8. Make a release note • Create new release note file in the RELEASE_NOTE folder which is named as Release ID. • The file contest is as below • Add a new line to the RELESE_HISTORY file (master file) to talk about which has done in this release VT1000 Release Note --------------------------------------- Software Version (2) Component version (3) Release man (4) Fixes (5) Build command (6) Tests

  9. Tagging • Make new tag in the tags folder (the tag name is same as Release ID) • Copy all image files (binary files, configuration files, mbn files…etc) to this tag folder. • Commit all new source code at Trunk & Tags to server. (Do not forget to let a comment with [Command] is [RELEASE]).

  10. Announce to everyone • After a few hours, if everything is OK. You can complete to make new release. • E-mail to everyone to let them know about new release (of course, ask them to use it). The e-mail template is as below Release date: DD-MM-YYYY Tag name: Tag name Release note:

  11. Thanks • I am writing build script that can be reduce workload of release man and it can be run automatically on release server (if we have ) • If you have any question, please come to my desk or e-mail to me truongnh4@viettel.com.vn

More Related