[Python-Dev] Proposed schedule for 3.4.2

2014-09-07 Thread Larry Hastings



Matthias asked me when I was going to release 3.4.2.  I propose the 
following schedule:


   Tag 3.4.2rc1 Friday Sep 12 2014
   Release 3.4.2rc1 Saturday Sep 13 2014
   Tag 3.4.2 final Saturday Sep 27 2014
   Release 3.4.2 final Sunday Sep 28 2014

Normally I want to tag on Saturdays and release on Sundays, however I 
propose moving rc1 a day earlier because I'll be unavailable that Sunday.


Any objections?  I will interpret silence as tacit approval.


//arry/
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Sad status of Python 3.x buildbots

2014-09-07 Thread Antonio Cavallo

Ok,

I've put everything under the tools directory of the build server for 
the project home:cavallo71:opt-python-interpreters:


https://build.opensuse.org/package/show/home:cavallo71:opt-python-interpreters/tools

To get started you need using the osc client (it uses the same 
subversion syntax, so is very simple):


   $> osc co home:cavallo71:opt-python-interpreters
   $> make -f tools/Makefile update (for the 2.7 branch)
   $> make -f tools/Makefile BRANCH=3 update (for the 3.x branch, I
   haven't fixed few issue with the build)

I don't think you'd bee able to use as it is because is still linked to 
my account (few hardcoded paths). But I can help in bootstrapping it if 
there's a general consensus on that (maybe having the python project 
official release build on susebuild?).


Then there's the testing bit (it's separate from the python binaries 
build to insulate the two). It's very similar and I'll post more details 
when ready.


I hope this helps,
Thnaks



Antonio Cavallo wrote:

Setting up a repo with the code and cleaning a bit here and there.
Over the weekend I can put something useable.



Nick Coghlan wrote:

On 4 September 2014 18:50, A. Cavallo wrote:

Yes there are "details" indeed. But not show stoppers. A prototype
can be
seen here: http://cclimited.webfactional.com
The nice bit is testing will be executed in a total fresh instance,
an added
bonus


Oh, very nice!

What is needed to get that up and running?

Regards,
Nick.


___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
https://mail.python.org/mailman/options/python-dev/a.cavallo%40cavallinux.eu


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


Re: [Python-Dev] Sad status of Python 3.x buildbots

2014-09-07 Thread Nick Coghlan
On 8 Sep 2014 04:51, "Antonio Cavallo"  wrote:
>
> Ok,
>
> I've put everything under the tools directory of the build server for the
project home:cavallo71:opt-python-interpreters:
>
>
https://build.opensuse.org/package/show/home:cavallo71:opt-python-interpreters/tools
>
> To get started you need using the osc client (it uses the same subversion
syntax, so is very simple):
>
>$> osc co home:cavallo71:opt-python-interpreters
>$> make -f tools/Makefile update (for the 2.7 branch)
>$> make -f tools/Makefile BRANCH=3 update (for the 3.x branch, I
>haven't fixed few issue with the build)

Thanks for posting this!

> I don't think you'd bee able to use as it is because is still linked to
my account (few hardcoded paths). But I can help in bootstrapping it if
there's a general consensus on that (maybe having the python project
official release build on susebuild?).

Integration into the release process will be up to the current release
managers (Larry Hastings for 3.4/3.5 and Benjamin Peterson for 2.7). That
may be worthwhile as a distro independent way of publishing "opt builds" of
Python for Linux platforms (I'd suggest using the softwarecollections.org
convention and put them under "/opt/psf/pythonXY").

Note that I think it's worth pursuing this as an integration testing tool,
regardless of whether or not we end up incorporating it into the release
process.

> Then there's the testing bit (it's separate from the python binaries
build to insulate the two). It's very similar and I'll post more details
when ready.

Thanks again!

Regards,
Nick.

>
> I hope this helps,
> Thnaks
>
>
>
> Antonio Cavallo wrote:
>>
>> Setting up a repo with the code and cleaning a bit here and there.
>> Over the weekend I can put something useable.
>>
>>
>>
>> Nick Coghlan wrote:
>>>
>>> On 4 September 2014 18:50, A. Cavallo wrote:

 Yes there are "details" indeed. But not show stoppers. A prototype
 can be
 seen here: http://cclimited.webfactional.com
 The nice bit is testing will be executed in a total fresh instance,
 an added
 bonus
>>>
>>>
>>> Oh, very nice!
>>>
>>> What is needed to get that up and running?
>>>
>>> Regards,
>>> Nick.
>>>
>> ___
>> Python-Dev mailing list
>> [email protected]
>> https://mail.python.org/mailman/listinfo/python-dev
>> Unsubscribe:
>>
https://mail.python.org/mailman/options/python-dev/a.cavallo%40cavallinux.eu
>>
> ___
> Python-Dev mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
https://mail.python.org/mailman/options/python-dev/ncoghlan%40gmail.com
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com


Re: [Python-Dev] Proposed schedule for 3.4.2

2014-09-07 Thread Ned Deily
In article <[email protected]>,
 Larry Hastings  wrote:
> Matthias asked me when I was going to release 3.4.2.  I propose the 
> following schedule:
> 
> Tag 3.4.2rc1 Friday Sep 12 2014
> Release 3.4.2rc1 Saturday Sep 13 2014
> Tag 3.4.2 final Saturday Sep 27 2014
> Release 3.4.2 final Sunday Sep 28 2014
> 
> Normally I want to tag on Saturdays and release on Sundays, however I 
> propose moving rc1 a day earlier because I'll be unavailable that Sunday.
> 
> Any objections?  I will interpret silence as tacit approval.

As I've already discussed with Larry, I think adding a week to the 
scheduled dates would be preferable.  The original dates give pretty 
short notice and there are a number of open issues that would be good to 
resolve now in 3.4.2.

-- 
 Ned Deily,
 [email protected]

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