That is not how it works. "new" generally triggers regression testing, and
success of it puts the patch into "review". So to get it to review, you need
to set it to "review" (usually the privilege of James) and when James puts it
into "countdown", dial that back again to "review". And if it migrates to
"push" without ever having seen a regtest, of course dial it back again too.
When you are convinced that it passes regtests, "new" is fine. It's your
choice then what to do with the eventually resulting "push".
---
** [issues:#5646] Switch to Python 3.x**
**Status:** Started
**Created:** Thu Dec 19, 2019 06:15 PM UTC by Jonas Hahnfeld
**Last Updated:** Wed Jan 22, 2020 09:36 AM UTC
**Owner:** Jonas Hahnfeld
Switch to Python 3.x
Find and require at least Python 3.5 which will allow us to address
some deprecation warnings, most notably about the 'imp' module.
The major version 3.5 was first released in September 2015 and should
be available in all major distributions, including Ubuntu LTS 16.04 and
18.04 as well as CentOS/RHEL 7.x and 8.x.
http://codereview.appspot.com/545370043
---
Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is
subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at
https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is
a mailing list, you can unsubscribe from the mailing list.
_______________________________________________
Testlilyissues-auto mailing list
testlilyissues-a...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
