Re: [Python-Dev] 3.6.0 Beta Phase Development

2016-09-27 Thread Michael Felt



On 26/09/2016 17:41, Guido van Rossum wrote:

The issue tracker is your friend!

I shall remember this for future reference

As you probably noticed - new "issue" https://bugs.python.org/issue28290 
-- BETA report: Python-3.6 build messages to stderr: AIX and "not GCC"


___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] 3.6.0 Beta Phase Development

2016-09-26 Thread Guido van Rossum
The issue tracker is your friend!

On Mon, Sep 26, 2016 at 5:25 AM, Michael Felt  wrote:
>
> On 13/09/2016 02:15, Ned Deily wrote:
>>
>> the challenge is to put the finishing touches on the features and
>> documentation, squash bugs, and test test test.  The next preview release
>> will be 3.6.0b2
>
>
> Found one typo in Modules/_io/_iomodule.h on line 156 - #endif^L rather than
> #endif (posted as an issue, but I suppose just a note here would have been
> enough)
>
> I have a longish list of messages to stderr from the compiler (IBM xlc) on
> AIX. Rather than spam everyone with those - would opening an issue be the
> way forward, or just sending the file to a person - rather than the list.
> ___
> Python-Dev mailing list
> Python-Dev@python.org
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/guido%40python.org



-- 
--Guido van Rossum (python.org/~guido)
___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] 3.6.0 Beta Phase Development

2016-09-26 Thread Michael Felt


On 13/09/2016 02:15, Ned Deily wrote:

the challenge is to put the finishing touches on the features and 
documentation, squash bugs, and test test test.  The next preview release will 
be 3.6.0b2


Found one typo in Modules/_io/_iomodule.h on line 156 - #endif^L rather 
than #endif (posted as an issue, but I suppose just a note here would 
have been enough)


I have a longish list of messages to stderr from the compiler (IBM xlc) 
on AIX. Rather than spam everyone with those - would opening an issue be 
the way forward, or just sending the file to a person - rather than the 
list.

___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


[Python-Dev] 3.6.0 Beta Phase Development

2016-09-12 Thread Ned Deily
Wow!  What a busy and productive couple of weeks it has been leading up to 
3.6.0b1 and feature code freeze!  Congratulations and thanks to all of you 
who've contributed to the amazing number of PEPs, features, bug fixes, and doc 
changes that have gone into 3.6.0b1!  Now that feature development for 3.6 is 
over, the challenge is to put the finishing touches on the features and 
documentation, squash bugs, and test test test.  The next preview release will 
be 3.6.0b2 scheduled for 2016-10-03.

In the cpython repo, there is now a 3.6 branch.  Starting now, all changes for 
3.6.0 should get pushed to the 3.6 branch and then merged to default for 3.7.  
New features nay continue to be pushed to the default branch for release in 
3.7; no new features are now permitted in 3.6 (unless you have contacted me and 
we have agreed on an extension).  Bug fixes appropriate for 3.5.x should get 
pushed to the 3.5 branch and then merged to 3.6 and then to default.  I've 
updated the Developer's Guide to reflect the now current workflow.  Let me know 
if you find any bugs in it.  Likewise, please contact me if you have any 
questions about the workflow or about whether a change is appropriate for 3.6 
beta.

To recap:

2016-09-12 3.6 branch open for 3.6.0; 3.7.0 feature development begins

2016-09-12 to 2016-12-04: 3.6.0 beta phase (no new features)
- push code for 3.6.0 (bug/regression/doc fixes) to the new 3.6 branch
- push code for new features to the default branch for release in 3.7

2016-10-03: 3.6.0 beta 2

2016-12-04 3.6.0 release candidate 1 (3.6.0 code freeze)

2016-12-16 3.6.0 release (3.6.0rc1 plus, if necessary, any dire emergency fixes)

2018-06 3.7.0 release (3.6.0 release + 18 months, details TBD)


Thank you all again for your great efforts so far on 3.6!

--Ned

http://cpython-devguide.readthedocs.io/en/latest/

https://www.python.org/dev/peps/pep-0494/

--
  Ned Deily
  n...@python.org -- []

___
Python-Dev mailing list
Python-Dev@python.org
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com