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.
Adobe itself has a bug and its called H1B. Have you seen their product showcases lately? Half of the product mangers are foreigners. God knows how many programmers back at HQ are Indians who are not good, just cheap. Doesnt Adobe make enough money? Why put your company at risk by importing incompetent foreign workers just to save a buck? Its forcing Abobe to embarrassingly have to issue patch after patch to fix their buggered up software. There are 1000s of highly skilled experienced veteran American programmers (that they fired) looking for a job. Rehire them and send the Indians back home. Thats the solution.
Good QA costs money. But that’s a crucial part of the entire product management cycle. Adobe must invest more on QA.
[…] is stable and bugs free. A useful reference for this caution is Premiere Pro 13.1 version, which contained a list of critical bugs that blocked functionality of Premiere. Users who updated to this version suffered from crashes and […]
[…] has happened to Premiere Pro? Adobe released a PP version with critical bugs (a No-Go strategy in product management methodology). Users are complaining about tons of crashes. […]