{"id":47591,"date":"2020-03-12T08:15:07","date_gmt":"2020-03-12T06:15:07","guid":{"rendered":"https:\/\/mamchenkov.net\/wordpress\/?p=47591"},"modified":"2020-03-12T08:15:10","modified_gmt":"2020-03-12T06:15:10","slug":"tips-for-implementing-a-software-release-process","status":"publish","type":"post","link":"https:\/\/mamchenkov.net\/wordpress\/2020\/03\/12\/tips-for-implementing-a-software-release-process\/","title":{"rendered":"Tips for Implementing a Software Release Process"},"content":{"rendered":"\n\n

I came across this nice article<\/a> outlining some of the tips for implementing the software release process.<\/p>\n\n\n\n

Software Development process is not complete and mature without a well-defined release process for the software applications. Every software application needs to be delivered or deployed at some point in time and for agile projects, this is happening more often. Therefore, there is a need to maintain software quality across the application releases to avoid deploying untested or malicious code to production environments.<\/p>

Defining a release process for software applications helps in ensuring that software releases maintain a constant release quality. In addition, software changes and new features are traceable or can be correlated to specific releases easily. As a result, changelogs and release notes are easier for a generation.<\/p><\/blockquote>\n\n\n\n

I do agree with most of what is being suggested. And if there’s one thing to add to these suggestions, it’d be a clear versioning convention. Personally, I’m a big fan of the Semantic Versioning<\/a>.<\/p>\n\n","protected":false},"excerpt":{"rendered":"\n

I came across this nice article outlining some of the tips for implementing the software release process. Software Development process is not complete and mature without a well-defined release process for the software applications. Every software application needs to be delivered or deployed at some point in time and for agile projects, this is happening … Continue reading Tips for Implementing a Software Release Process<\/span><\/a><\/p>\n\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"Tips for Implementing a Software Release Process #WebDev #QA #productivity #VersionControl #ProjectManagement ","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","default_image_id":0,"font":"","enabled":false},"version":2},"jetpack_post_was_ever_published":false,"_links_to":"","_links_to_target":""},"categories":[1,18,62,1334],"tags":[3178,3074,1588,1330],"keyring_services":[],"class_list":["post-47591","post","type-post","status-publish","format-standard","hentry","category-general","category-programming","category-technology","category-web-work","tag-project-management","tag-quality-assurance","tag-version-control","tag-web-development"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t