Hi,
On 2 November 2016 at 17:49, Carl Friedrich Bolz wrote:
> FWIW, there is this:
>
> https://bitbucket.org/okusche/bitbucket-curl-upload-to-repo-downloads
>
> Which I haven't tested, but the author says works.
I can continue to volunteer to download the nightly builds and
re-upload them to bit
FWIW, there is this:
https://bitbucket.org/okusche/bitbucket-curl-upload-to-repo-downloads
Which I haven't tested, but the author says works.
Carl Friedrich
On November 2, 2016 5:27:26 PM GMT+01:00, Matti Picus
wrote:
>On 02/11/16 17:42, Richard Plangger wrote:
>
>> Hi,
>>
>>> Would someone e
On 02/11/16 17:42, Richard Plangger wrote:
Hi,
Would someone else like to pair with me for the release so they could do
the next one?
Yes, I would like to help out here! In cape town I have done the same
release procedure for pypy3 (Python 3.3). It annoyed me :)
I think most of the steps cou
Hi,
> Would someone else like to pair with me for the release so they could do
> the next one?
Yes, I would like to help out here! In cape town I have done the same
release procedure for pypy3 (Python 3.3). It annoyed me :)
I think most of the steps could be done automatically (ideally a script
Matti,
On Wednesday 2016-11-02 17:11, Matti Picus wrote:
Are there outstanding branches that just have to be in this release or
issues that we consider blockers?
I want at some point in the near future push cling-support onto master. I
assume there are no objections (if there are, please speak
I am thinking of pushing out what I guess should be PyPy2.7-5.6.0, we
released PyPy2.7-v5.4.0 on Aug 31 and PyPy3.3-v5.5.0 on Oct 12.
Are there outstanding branches that just have to be in this release or
issues that we consider blockers?
Would someone else like to pair with me for the releas
