On Wed, Jul 11, 2018 at 3:30 AM Andreas Tille <andr...@fam-tille.de> wrote:
> Hi Thiago,
> On Tue, Jul 10, 2018 at 09:39:12PM -0300, Thiago Franco Moraes wrote:
> > I think the easiest way to fix this bug is to package the git version.
> > Also, the git version is already working with Python3. What do you
> > think?
> I have no opinion about what code works better - that's perfectly your
> decision as upstream and probably active user. While we could even turn
> the debian/watch file to git mode which fetches the lastet Git commit
> I'm afraid that this is always in flux. What do you think about an
> early beta release and we use this tarball until there is a stable
> version of the next release? The thing is that also non-Debian users
> might stumble upon the issues. If you can refer those users to such a
> release that might have some users that have tested exactly this code
> and not a random Git commit this could have some advantages.
> What do you think about this suggestion?
I was thinking the second option. I'll create a new version tag,
something like 3.1.9997, then I'll have a tarball with this version.
Also, I'll package it using Python3.
> Kind regards