Adobe has released Premiere Pro version 13.1.1 which contains fixes to crashes and pressing issues regarding 13.1. Releasing a bug-fixed update is OK, but publishing an update full of fixed critical bug indicates on the impaired methodology of software development.

What is wrong with Adobe?

Let us educate you a bit regarding product management methodologies.

The software version is defined as a release candidate and must undergo a QA cycle (quality assurance) before released to the public. The QA process (which in the case of extremely complex software like NLE – Non-Linear Editing) must indicate on bugs and categories them to three types: minor (medium), major (high) and critical (immediate). Generally speaking, the release candidate can be pushed to the public with minor and major bugs. However, a release candidate suffers from critical bugs must not be released to users.

A release candidate suffers from critical bugs must not be released to users

Critical bugs

Critical bugs are defined as a priority-one bug. These are bugs to be fixed immediately within 24 hours. That generally occurs in cases when a complete functionality is blocked, and no testing can proceed as a result of this. Or in certain other cases if there are significant memory leaks, then generally the defect is classified as a priority -1 meaning the program/ feature is unusable in the current state. For any reason, if the application crashes or it becomes unusable / not able to proceed further, the defect could be classified under critical severity. For those who are interested in reading more, there is a helpful and straightforward article demonstrating further QA definition and process. 

For any reason, if the application crashes or it becomes unusable / not able to proceed further, the defect could be classified under critical severity

Premiere Pro 13.1.1

From reading the fixed issues on 13.1.1, we can conclude that this is a list of critical (severe) bugs, that cause Premiere Pro to crash. The fixed issues are (feel free to count how many times the “crash” word appears):

• Crash opening a project or working with a project on macOS
• Premiere Pro crashes on launch
• Premiere Pro crashes while rendering
• Premiere Pro crashes on launch on macOS because of issues with preferences in the Permissions folder
• Premiere Pro crashes on launch or while switching workspaces
• Opening Premiere Pro with missing font graphic in a project on Windows causes Premiere Pro to crash

The question arises why Adobe has released a version of Premiere Pro full of critical (severe) bugs. That indicates an impaired product management process and methodology, derived from ineffective QA cycles.

Premiere Pro 13.1 – A software version full of critical bugs

The question arises why Adobe has released a version of Premiere Pro full of critical (severe) bugs. That indicates an impaired product management process and methodology, derived from ineffective QA cycles. That’s not the way to go for a respected company like Adobe, especially when the target market is professionals who need the software for their business.

We’d appreciate your opinion on this. Comment below.