Issue Tracker migration

[Cantor, Scott]

>    1. JIRA account: can I get access to my old one again?  I'm the reporter

I can't just get you access to an account, it's not our account system anymore. I can update reporters if I know them and if I know what Atlassian account to attach them to. Basically, only you can create and manage the account. Once you do, if it's not the one we have, I can update things to a point.

>    2. Some of the patches in the Debian package would be suitable for
>       upstream in my opinion.  If you'd rather review them not at
>       please state your preferred place.

Our Jira, obviously.

>    3. GCC 11 defaults to C++17 which does not allow dynamic exception
>       specifications, breaking
>       the build of the SP stack.  GCC 11 isn't the default compiler in
>       Debian yet, but probably will be by next year, so I'd like to know
>       where you stand.

I don't know the impact, but anything huge is just not going to happen, when the focus needs to be on dumping all of this code entirely. It's particularly a problem if it isn't even our code that would need to change. We have not made a decision about the C++ baseline in the future, but once there are no dependencies, we would be likely to get more aggressive.

-- Scott