Python 3 porting Bugzilla guidance

[Troy Curtis Jr]

Do I surmise correctly that Bugzilla tickets are only to be created if
there is a packaging issue preventing python3 "compliance", and not if
 upstream needs to be updated first to support? If so, is there a different
resource that is used to track any research done into upstream that
identified the need for changes?  Or is the assumption that there would be
discussion on the upstream mailing list or an issue in their project
specific tracker and thus a Bugzilla entry would be redundant?

Thanks,
 Troy

[Iryna Shcherbina]

Hi Troy,

On 09/12/2017 02:36 AM, Troy Curtis Jr wrote:
> Do I surmise correctly that Bugzilla tickets are only to be created if 
> there is a packaging issue preventing python3 "compliance", and not if 
>  upstream needs to be updated first to support?

That is correct, we usually create Bugzilla tickets only for packages 
which already support Python 3 upstream but do not provide a Python 3 
version of the package for Fedora or if there are any issues with the 
Python 3 package.
> If so, is there a different resource that is used to track any 
> research done into upstream that identified the need for changes? Or 
> is the assumption that there would be discussion on the upstream 
> mailing list or an issue in their project specific tracker and thus a 
> Bugzilla entry would be redundant?

Yes, source code porting to Python 3 is usually discussed in e.g. GitHub 
issues of upstream projects or in upstream mailing lists.
> Thanks,
>  Troy
>
> python-devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

Kind regards,
Iryna Shcherbina

[Charalampos Stratakis]

We do have though a tracker for upstream projects, although no discussion is done there, it is mainly for people looking for some sort of a list, of various upstream projects that could be
potentially interested to work on.

You can check it at: https://bugzilla.redhat.com/show_bug.cgi?id=1322027

Regards,

Charalampos Stratakis
Software Engineer
Python Maintenance Team, Red Hat

----- Original Message -----
From: "Iryna Shcherbina" 
To: [e-mail]
Sent: Tuesday, September 12, 2017 11:08:31 AM
Subject: Re: Python 3 porting Bugzilla guidance

Hi Troy,

On 09/12/2017 02:36 AM, Troy Curtis Jr wrote:

Do I surmise correctly that Bugzilla tickets are only to be created if there is a packaging issue preventing python3 "compliance", and not if upstream needs to be updated first to support? That is correct, we usually create Bugzilla tickets only for packages which already support Python 3 upstream but do not provide a Python 3 version of the package for Fedora or if there are any issues with the Python 3 package.

If so, is there a different resource that is used to track any research done into upstream that identified the need for changes? Or is the assumption that there would be discussion on the upstream mailing list or an issue in their project specific tracker and thus a Bugzilla entry would be redundant? Yes, source code porting to Python 3 is usually discussed in e.g. GitHub issues of upstream projects or in upstream mailing lists.

Thanks, 
Troy

_______________________________________________
python-devel mailing list -- [e-mail] To unsubscribe send an email to [e-mail] 
Kind regards, 
Iryna Shcherbina

_______________________________________________
python-devel mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]

[Troy Curtis Jr]

On Wed, Sep 13, 2017 at 8:02 AM Charalampos Stratakis 
wrote:
> We do have though a tracker for upstream projects, although no discussion
> is done there, it is mainly for people looking for some sort of a list, of
> various upstream projects that could be
> potentially interested to work on.
>
> You can check it at: https://bugzilla.redhat.com/show_bug.cgi?id=1322027
>
> Regards,
>
> Charalampos Stratakis
> Software Engineer
> Python Maintenance Team, Red Hat

Thanks!

So something like this is appropriate?
https://bugzilla.redhat.com/show_bug.cgi?id=1492382

-- Troy

----- Original Message -----
> From: "Iryna Shcherbina" 
> To: [e-mail]
> Sent: Tuesday, September 12, 2017 11:08:31 AM
> Subject: Re: Python 3 porting Bugzilla guidance
>
> Hi Troy,
>
> On 09/12/2017 02:36 AM, Troy Curtis Jr wrote:
>
> Do I surmise correctly that Bugzilla tickets are only to be created if
> there is a packaging issue preventing python3 "compliance", and not if
> upstream needs to be updated first to support? That is correct, we usually
> create Bugzilla tickets only for packages which already support Python 3
> upstream but do not provide a Python 3 version of the package for Fedora or
> if there are any issues with the Python 3 package.
>
> If so, is there a different resource that is used to track any research
> done into upstream that identified the need for changes? Or is the
> assumption that there would be discussion on the upstream mailing list or
> an issue in their project specific tracker and thus a Bugzilla entry would
> be redundant? Yes, source code porting to Python 3 is usually discussed in
> e.g. GitHub issues of upstream projects or in upstream mailing lists.
>
> Thanks,
> Troy
>
> python-devel mailing list -- [e-mail] To
> unsubscribe send an email to [e-mail]
> Kind regards,
> Iryna Shcherbina
>
> python-devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> _______________________________________________
> python-devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

[Craig Rodrigues]

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

On Wed, Sep 13, 2017 at 6:02 AM, Charalampos Stratakis 
wrote:
> We do have though a tracker for upstream projects, although no discussion
> is done there, it is mainly for people looking for some sort of a list, of
> various upstream projects that could be
> potentially interested to work on.
>
> You can check it at: https://bugzilla.redhat.com/show_bug.cgi?id=1322027
>
> Regards,
>
> Charalampos Stratakis
> Software Engineer
> Python Maintenance Team, Red Hat
>
> ----- Original Message -----
> From: "Iryna Shcherbina" 
> To: [e-mail]
> Sent: Tuesday, September 12, 2017 11:08:31 AM
> Subject: Re: Python 3 porting Bugzilla guidance
>
> Hi Troy,
>
> On 09/12/2017 02:36 AM, Troy Curtis Jr wrote:
>
> Do I surmise correctly that Bugzilla tickets are only to be created if
> there is a packaging issue preventing python3 "compliance", and not if
> upstream needs to be updated first to support? That is correct, we usually
> create Bugzilla tickets only for packages which already support Python 3
> upstream but do not provide a Python 3 version of the package for Fedora or
> if there are any issues with the Python 3 package.
>
> If so, is there a different resource that is used to track any research
> done into upstream that identified the need for changes? Or is the
> assumption that there would be discussion on the upstream mailing list or
> an issue in their project specific tracker and thus a Bugzilla entry would
> be redundant? Yes, source code porting to Python 3 is usually discussed in
> e.g. GitHub issues of upstream projects or in upstream mailing lists.
>
> Thanks,
> Troy
>
> python-devel mailing list -- [e-mail] To
> unsubscribe send an email to [e-mail]
> Kind regards,
> Iryna Shcherbina
>
> python-devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> _______________________________________________
> python-devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

[Troy Curtis Jr]

On Sat, Sep 16, 2017, 10:42 PM Craig Rodrigues  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.

--
Troy
> On Wed, Sep 13, 2017 at 6:02 AM, Charalampos Stratakis <
> [e-mail]> wrote:
> > We do have though a tracker for upstream projects, although no discussion
> > is done there, it is mainly for people looking for some sort of a list, of
> > various upstream projects that could be
> > potentially interested to work on.
> >
> > You can check it at: https://bugzilla.redhat.com/show_bug.cgi?id=1322027
> >
> > Regards,
> >
> > Charalampos Stratakis
> > Software Engineer
> > Python Maintenance Team, Red Hat
> >
> > ----- Original Message -----
> > From: "Iryna Shcherbina" 
> > To: [e-mail]
> > Sent: Tuesday, September 12, 2017 11:08:31 AM
> > Subject: Re: Python 3 porting Bugzilla guidance
> >
> > Hi Troy,
> >
> > On 09/12/2017 02:36 AM, Troy Curtis Jr wrote:
> >
> > Do I surmise correctly that Bugzilla tickets are only to be created if
> > there is a packaging issue preventing python3 "compliance", and not if
> > upstream needs to be updated first to support? That is correct, we usually
> > create Bugzilla tickets only for packages which already support Python 3
> > upstream but do not provide a Python 3 version of the package for Fedora or
> > if there are any issues with the Python 3 package.
> >
> > If so, is there a different resource that is used to track any research
> > done into upstream that identified the need for changes? Or is the
> > assumption that there would be discussion on the upstream mailing list or
> > an issue in their project specific tracker and thus a Bugzilla entry would
> > be redundant? Yes, source code porting to Python 3 is usually discussed in
> > e.g. GitHub issues of upstream projects or in upstream mailing lists.
> >
> > Thanks,
> > Troy
> >
> > python-devel mailing list -- [e-mail] To
> > unsubscribe send an email to [e-mail]
> > Kind regards,
> > Iryna Shcherbina
> >
> > python-devel mailing list -- [e-mail]
> > To unsubscribe send an email to
> > [e-mail]
> > _______________________________________________
> > python-devel mailing list -- [e-mail]
> > To unsubscribe send an email to
> > [e-mail]
>
> python-devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]

[Petr Viktorin]

On 09/17/2017 03:36 PM, Troy Curtis Jr wrote:
> On Sat, Sep 16, 2017, 10:42 PM Craig Rodrigues <[e-mail] 
> > 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

[Troy Curtis Jr]

On Mon, Sep 18, 2017 at 7:01 AM Petr Viktorin  wrote:
> 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.

So if there are pending issues, patches, or merge requests upstream related
to the python3 porting effort there should be a portingdb ticket created
requesting a link to the upstream discussion/status be added? And I should
*not* create a bugzilla ticket blocking
https://bugzilla.redhat.com/show_bug.cgi?id=1322027 like I did with
https://bugzilla.redhat.com/show_bug.cgi?id=1492382 ?  Or perhaps both
should/could be done as perhaps they are used by separate teams tracking
different status?  Just trying to get a handle on the preferred route.

Thanks,
Troy
> 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.
>
> --
> Petr Viktorin

[Miro Hrončok]

On 28.9.2017 06:12, Troy Curtis Jr wrote:
> On Mon, Sep 18, 2017 at 7:01 AM Petr Viktorin <[e-mail] 
> > wrote:
> 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.
>
>
> So if there are pending issues, patches, or merge requests upstream 
> related to the python3 porting effort there should be a portingdb ticket 
> created requesting a link to the upstream discussion/status be added?

Preferably a Pull Request, but yes.
> And I should *not* create a bugzilla ticket blocking 
> https://bugzilla.redhat.com/show_bug.cgi?id=1322027 like I did with 
> https://bugzilla.redhat.com/show_bug.cgi?id=1492382 ?

You could (but I personally don't see it very useful).
> Or perhaps both 
> should/could be done as perhaps they are used by separate teams tracking 
> different status?  Just trying to get a handle on the preferred route.
>
> Thanks,
> Troy
> 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
>
> --
> Petr Viktorin
>
>
>
> python-devel mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]