Hidden Backport Tickets
We try to test code in at least one alpha release before backporting it.
Here are the tickets that are hidden from [the current backports table]:
Release-Based Tags
consider-backport-after-0433
lower-risk changes merged into 0.4.3 after 0.4.3.1 was released, but before 0.4.3.2 was released
[[TicketQuery(status!=closed,keywords~=consider-backport-after-0433,group=milestone,format=table,order=changetime,desc=true,col=id|summary|status|owner|reviewer|priority|severity|changetime|sponsor,max=100)]]
consider-backport-after-0434
lower-risk changes merged into 0.4.3 after 0.4.3.2 was released, but before 0.4.3.3 was released
[[TicketQuery(status!=closed,keywords~=consider-backport-after-0434,group=milestone,format=table,order=changetime,desc=true,col=id|summary|status|owner|reviewer|priority|severity|changetime|sponsor,max=100)]]
consider-backport-after-043-stable
higher-risk changes marked for backport while 0.4.3 is in alpha
[[TicketQuery(status!=closed,keywords~=consider-backport-after-043-stable,group=milestone,format=table,order=changetime,desc=true,col=id|summary|status|owner|reviewer|priority|severity|changetime|sponsor,max=100)]]
Testing-Based Tags
The following keyword are not hidden, they need to be checked manually:
consider-backport-after-authority-test
lower-risk changes that affect authorities: these changes are usually tested by arma on moria
[[TicketQuery(status!=closed,keywords~=consider-backport-after-authority-test,group=milestone,format=table,order=changetime,desc=true,col=id|summary|status|owner|reviewer|priority|severity|changetime|sponsor,max=100)]]
consider-backport-after-sbws-bwauth-test
lower-risk changes that affect bandwidth authorities running sbws: these changes should be tested on a sbws bwauth
[[TicketQuery(status!=closed,keywords~=consider-backport-after-sbws-bwauth-test,group=milestone,format=table,order=changetime,desc=true,col=id|summary|status|owner|reviewer|priority|severity|changetime|sponsor,max=100)]]
Information-Based Tags
The following keyword are hidden:
consider-backport-if-needed
Changes that we aren't sure if we need to backport. But we would be willing to backport them, if the bug they fix has a big enough impact on users.
[[TicketQuery(status!=closed,keywords~=consider-backport-if-needed,group=milestone,format=table,order=changetime,desc=true,col=id|summary|status|owner|reviewer|priority|severity|changetime|sponsor,max=100)]]