The Release Management Wiki, supported by Electric Cloud, is a compilation of thousands of online resources on Release Management - a process whereby software is taken from requirements, through development and testing, until deployment and delivery of finished software to users.
New: The Top Brands in Release Management
We've created the first global ranking of brands in the release management space, using data from over 4,000 articles curated on our Release Management Wiki, and external data sources such as social and link metrics.
» Who are the Top 20 Vendors in Release Management?
» Who are the Top 20 Websites in Release Management?
The report covers the requirements that CIOs and Architects should be thinking about when selecting an Application Release Automation solution, with Gartner's recommendations about the best solutions to manage releases in a scalable and predictable way. Electric Cloud has been named a leader in the ARA Magic Quadrant.
Read the article on electric-cloud.com »
So am I really going to write a blog calling DevOps a big hoax? Well, not exactly, but as a follow-up to my previous blog on the difference between DevOps and Continuous Delivery, I want to alert you to a few key facts.
Read the article on devops.com »
The range of opportunities for automation in DevOps, along with the choice of tools that you can use, can seem complex, especially for smaller teams with limited time and resources. You might already be doing some automation today, but how do you prioritize what to focus on next? If you're beginning a new DevOps project from scratch, where do you start?
Read the article on techbeacon.com »
At last year's SQL in the City, I played the part of a manual DBA making changes and deploying those from development to test, staging, and production environments. Actually, I don't think we went to production because I didn't have time. My co-worker, Tom Austin, showcased the automated process using SQL Source Control and other Redgate tools. As much as I believe in using tools, and despite the fact I regularly use them, even I was impressed by how much less work the automated process took.
Read the article on voiceofthedba.com »
The DevOps mind-set of incremental, continuous integration and delivery is familiar to consumers, but faces challenges when it comes to application testing and training in enterprise settings. The business has to move to a continuous delivery mind-set with an entire DevOps tools list for support: Small changes delivered rapidly and effectively on a regular basis are easier for the help desk and end users to adopt.
Read the article on techtarget.com »
Release Management Process
Enterprise Release Management encompasses aligning the necessary non-production or test environments to support the coordinated release strategy. What defines the Enterprise Release Management process is the coordinated promotion of new functionality into existing production environments on a specified date.
Read the article on plutora.com »
Your customers expect valuable services — and they expect them without disruption. That makes it critical that every single release be built, tested, and delivered following a rigorous process that ensures quality and minimizes risk. ITIL's Release and Deployment Management phase is designed for exactly that: ensuring that your releases are deployed into production efficiently and effectively.
Read the article on bmc.com »
The business impact of not being able to bring people, processes, and systems
together across development and operations teams is evident when applications that are the mainstay of a business falter due to failed deployments and releases. So how do you improve the quality and increase the speed of your releases and deployments without compromising environmental stability and control? And how do you streamline processes that span your development and operations teams?
Read the article on info.serena.com »
Deployment Process and Planning
At the recent Agile 2016 conference InfoQ spoke to Dennis Ehle, vice president of DevOps strategy for VersionOne about the evolution of DevOps both as a way of thinking and the toolsets that support the practices, and the importance of having visibility into how value is delivered over the DevOps pipeline.
Read the article on infoq.com »
The amount of time spent on setup, deployment and manually testing code is often ignored by technology teams and managers. Manual server configuration and code quality tests are not only error prone, but they ultimately result wasted time and money.
Read the article on networkworld.com »
The coverage gap around measurement and metrics is driven primarily by the fact that the DevOps space is new and there are few standards around which to build an easily documented metrics structure. That leaves practitioners with the challenge of creating something they can use pragmatically within their own organizations. This article discusses how to close the gap on some key continuous delivery metrics.
Read the article on devops.com »
Knowledge and information management system deployments are commonly delayed in a quest for perfection. Releasing too early will yield a "so what effect," where your end users don't see sufficient value. Releasing too late delays your business value and often creates a situation where meaningful analytics and feedback are lacking from your design and development cycle. The "just right" release date requires an understanding of the system, users, and organizational culture.
Read the article on http://enterprise-knowledge.com »
A product release is the launch of a new product or a combination of features that will provide value to customers or users. Digging deeper, a release is much more to both your customers and internal teams. For your customers, it's a promise of new value they can look forward to embedding in their everyday work and activities.
Read the article on huffingtonpost.com »
This list contains items that need to be completed before software can be released. Each team must customize this list as appropriate for your specific project. Some of the items below may not apply to your team and you may need to add other important items. Fill in the "person responsible" column with the name of the actual person on your team.
Read the article on users.csc.calpoly.edu »
Release Communication and Training
Why are good release notes so hard to come by? Why are they so rare that I take a screenshot when I do come by one that manages to be readable and fun? Possibly because not everyone has caught onto the hidden value of writing really great release notes. But you don't have to make your release notes a work of art to take advantage of a great engagement opportunity.
Just write better release notes.
Read the article on www.prodpad.com »
One of the major functions of any open source project is releasing software, with the goal of reaching as many users as possible. We've crafted a set of guidelines for coordinating release announcements to ensure that your excellent work doesn't get lost in the shuffle.
Read the article on community.redhat.com »
For some businesses, release notes are the only way product enhancements are communicated to customers. For others, they're a sideline, developed entirely separately from user communications. But if you want to do more with less - if you want to improve customer retention communications without having to do a stack more work - your release notes could be an unexpected, but valuable answer.
Read the article on sitepoint.com »
The Top Vendors in Release Management
The Release Management Wiki's editors analyzed over 4,000 release-related articles published by hundreds of authoritative sources, as well as external metrics such as social shares and backlinks, to identify the most influential vendors offering products and knowledge which is of value to the release management community. Click the links for a comprehensive listing of resources on each product in the context of release management.
The Top Websites in Release Management
Prolific score: number of web pages published on release management subjects on the website over the past year.
Popular score: average Facebook shares, Google +1s and LinkedIn shares for release management articles published on the website.
Cited score: number of backlinks to the website on release-management-related subjects, based on the Majestic backlink database.
Quality: Editorial score of the value of the content for the release management community - based on content published on our wiki or submitted to us by the publishers.
Top Website Score: normalized weighted average of the above four scores.
Want More? See All the Topics in Our Release Management Wiki