I cleaned up all of the stuff on phab, and Wikibase Release Strategy is the place for these to go now.
I'll wait for https://github.com/wmde/wikibase-release-pipeline/issues/191 to move to phab and then turn off the issue tracker on github etc.

I think there are at least two things entangled here:

1. How to trace, prioritize etc issues and feature requests related to WMDE internal tooling and process related to Wikibase releases (e.g. "wikibase release pipeline", "wikibase release strategy"). I'd think that non-WMDE staff, in particular Wikibase users of our releases packages have no much interest in these.
2. How to trace, prioritize etc issues and feature requests related to Wikibase suite packages. That could cover the wide spectrum of issues: content of the suite (what software/components are in), issues with installing, updating etc a Wikibase installed using X from version Y to Z, etc, bugs in software provided in Wikibase packages (i.e. less related to the packages themselves but more to the actual functionality of a software component)

For 2 currently used https://github.com/wmde/wikibase-release-pipeline/issues is clearly not well suited for those in my opinion.
For 1 if it is seen as primarily internal bug tracking, than that'd be at a liberty of a relevant WMDE team to decide.

I have my eyes on this because I'm very invested in seeing/building consensus that all formal issues should be tracked in Phabricator.

And since Phab is a difficult experience for people who are just asking questions, I hope we can agree that the place for simpler, FAQ-compatible questions is the FAQ talk page.

My personal opinion

1. track actual tickets/bugs in phabricator, anything serious or "formal" from issues moves to phabricator (Maybe we can spend some time to make that transformation easier)
2. keep issues open on github (this just serves as an entry for feedback which is good imo)
3. FAQ page https://www.mediawiki.org/wiki/Wikibase/FAQ looks great, but still don't see a reason to close down issues or why we would have to choose only one.