Dries opened a 9.x branch, but it's not possible to filter issues by 9.x, which makes it impossible to see which issues have been moved there. We need to be able to move issues to 9.x without them getting 'lost', and there's bound to be some, er, negotiation, of what exactly is and isn't too late to go into 8.x which usually involves a bit of version changing.

See the error on:


I have a feeling we need a dev release of 9.x in order to have this available in the filters? It seems a bit like a project bug that you can file issues against a version without being able to filter on them but leaving this against core for working around it.


webchick’s picture

Status:Active» Postponed (maintainer needs more info)
catch’s picture

Category:bug» support
Priority:Major» Normal
Status:Postponed (maintainer needs more info)» Fixed

Nothing, I was just trying to find a 9.x-issues filter instead of 9.x-dev. Doh.

webchick’s picture

Btw, there is a 9.x-dev release, but it's unpublished. I didn't actually expect the issue queue to work that way, but it magically did and so I just went with it. :) Since 9.x-dev will always be 100s of commits behind 8.x-dev, it seems like exposing it to end users is just asking for trouble.

Status:Fixed» Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.