[python-committers] [RELEASE] ACTION REQUIRED: Python 3.8.0b4 now available for testing

2019-08-30 Thread Łukasz Langa 
It's time for the last beta release of Python 3.8. Go find it at:

https://www.python.org/downloads/release/python-380b4/ 



This release is the last of four planned beta release previews. Beta release 
previews are intended to give the wider community the opportunity to test new 
features and bug fixes and to prepare their projects to support the new feature 
release. The next pre-release of Python 3.8 will be 3.8.0c1, the first release 
candidate, currently scheduled for 2019-09-30.

Call to action

We strongly encourage maintainers of third-party Python projects to test with 
3.8 during the beta phase and report issues found to the Python bug tracker as 
soon as possible. Please note this is the last beta release, there is not much 
time left to identify and fix issues before the release of 3.8.0. If you were 
hesitating trying it out before, now is the time.

While the release is planned to be feature complete entering the beta phase, it 
is possible that features may be modified or, in rare cases, deleted up until 
the start of the release candidate phase (2019-09-30). Our goal is have no ABI 
changes after beta 3 and no code changes after 3.8.0c1, the release candidate.

To achieve that, it will be extremely important to get as much exposure for 3.8 
as possible during the beta phase. That beta phase is coming to an end. Please 
test now.

Please keep in mind that this is a preview release and its use is not 
recommended for production environments.

Acknowledgments

Many developers worked hard for the past four weeks to squash remaining bugs, 
some requiring non-obvious decisions. Many thanks to the most active, namely 
Raymond Hettinger, Steve Dower, Victor Stinner, Terry Jan Reedy, Serhiy 
Storchaka, Pablo Galindo Salgado, Tal Einat, Zackery Spytz, Ronald Oussoren, 
Neil Schemenauer, Inada Naoki, Christian Heimes, and Andrew Svetlov.

3.8.0 would not reach the Last Beta without you. Thank you!


- Ł


signature.asc
Description: Message signed with OpenPGP
___
python-committers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/AP7O65CDZWNWGCLJBRYLW3AP5H4L3MRK/
Code of Conduct: https://www.python.org/psf/codeofconduct/

[python-committers] Re: PEP 581/588 RFC: Collecting feedback about GitHub Issues

2019-08-30 Thread Raymond Hettinger 


> On Aug 27, 2019, at 10:44 AM, Mariatta  wrote:
> 
> (cross posting to python-committers, python-dev, core-workflow)
> 
> PEP 581: Using GitHub Issues has been accepted by the steering council, but 
> PEP 588: GitHub Issues Migration plan is still in progress.
> 
> I'd like to hear from core developers as well as heavy b.p.o users, the 
> following:
> 
>   • what features do they find lacking from GitHub issues, or
>   • what are the things you can do in b.p.o but not in GitHub, or
>   • Other workflow that will be blocked if we were to switch to GitHub 
> today
> By understanding your needs, we can be better prepared for the migration, and 
> we can start looking for solutions.

One other bit of workflow that would be blocked if there was a switch to GitHub 
today:

* On the tracker, we have long running conversations, sometimes spanning years. 
  We need to be able to continue those conversations even though the original 
participants may not have Github accounts (also, if they do have a Github 
account, we'll need to be able to link to the corresponding BPO account).  

* I believe some of the accounts are anonymous or have pseudonyms.  Am not sure 
how those can be migrated, we know very little about the participant except for 
their recurring posts.


Raymond


___
python-committers mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/python-committers.python.org/
Message archived at 
https://mail.python.org/archives/list/[email protected]/message/MT2PJFS2CVDSWQKCCRUR3BCNXR4OSEKU/
Code of Conduct: https://www.python.org/psf/codeofconduct/