[Libreoffice-qa] Backport Requests: Example of regression that only affects older branch

Robinson Tryon bishop.robinson at gmail.com
Sun Jan 18 16:05:56 PST 2015

Hi all,

I just ran across a texbook example of a regression that only affected
an older (but still active) release branch:

Both QA and Developers run into bugs like this all the time, so I
figured it would be a good idea to share my workflow of triaging bug


In this particular case, Draw could be induced to crash with a 4.3
build, however it did not crash with a 4.2, 4.4, or 4.5 build. As a
result, I
- RESOLVED the bug as WORKSFORME (it's fixed in the latest build)
- Tagged it as a mab4.3 (it's a crasher)
- Keywords: regression
- Asked for a backport once the commit is found: Whiteboard ->
- Asked for a bibisect: Whiteboard -> bibisectRequest


While I was testing with the builds on my local system, I downloaded
the latest 4.3 build:

As it turns out, LO rc did *not* have this crash, which meant
that it was fixed in all of our active branches, and I could then
- Remove mab4.3
- Remove bibisectRequest and backportRequest:4.3

I also left a note telling the bug reporter that this fix would be
available in the upcoming 4.3.6 release, just in case the reporter (or
someone else reading the bug report) isn't familiar with our release


It's important for us to keep track of open backport requests. You can
find queries linked from the 'Useful Queries' page here:

For QA, we'll want to focus on backport requests that need to be
bibisected. For the Devs, you'll want to focus on backport requests
that do not.

As a quick reminder, if there's a good reason not to backport a fix,
change backportRequest:4.3 into backportDenied:4.3 and please leave a
short. explicative comment on the bug.

Questions/Comments? Let me know!


Robinson Tryon
QA Engineer - The Document Foundation
LibreOffice Community Outreach Herald
qubit at libreoffice.org

More information about the Libreoffice-qa mailing list