On 09/17/2017 03:36 PM, Troy Curtis Jr wrote:
On Sat, Sep 16, 2017, 10:42 PM Craig Rodrigues <rodrigc@freebsd.org mailto:rodrigc@freebsd.org> wrote:
In the Python 3 porting FAD in 2015: https://fedoraproject.org/wiki/FAD_Python_3_Porting_2015 This database and web interface was used to keep track of upstream projects and their Python 3 status: http://fedora.portingdb.xyz/ Is that database no longer being used? -- Craig
I was actually just wondering if I should submit a ticket for that porting db to reference the new bug or if that was somehow automatic.
It's only automatic for Bugzilla. If upstream is not using the Fedora/RH bugzilla (which it shouldn't, really), a URL for the upstream discussion needs to be added manually. And of course you can open a portingdb ticket for that.
Nowadays I don't want portingdb to have too much info about upstream, because: - Upstream discussions for a projects are usually not hard to find. - Bugzilla is Fedora-specific, so people from other OSs won't look there. - portingdb is mainly used by the Fedora Python SIG; both upstreams and other Fedorans aren't likely to look there.
So I prefer portingdb having just an URL for the upstream discussion – and even that isn't needed if interested people can easily find that discussion.
Once there's a py3-compatible release upstream, it's enough to open a bugzilla for the Fedora package and link it to the tracking bug (see [Python 3 Bug Filing]). Then portingdb will eventually update.
[Python 3 Bug Filing]: https://fedoraproject.org/wiki/User:Pviktori/Python_3_Bug_Filing