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 release so they could do the next one? FWIW, I tick off the boxes on http://pypy.readthedocs.io/en/latest/how-to-release.html, not too hard really. I started a release notice http://pypy.readthedocs.io/en/latest/release-pypy2.7-v5.6.0.html, edits are encouraged. It is a bit dry/formal, for what is quite a leap forward in terms of stdlib2.7.12, cpyext, OpenSSL, ... Matti
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 up :) ). What would be the most convenient time (need not be this release, in fact right after, to get maximum lead time for the next, is fine by me)? Best regards, Wim -- WLavrijsen@lbl.gov -- +1 (510) 486 6411 -- www.lavrijsen.net
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 that is started on a server and runs to completion there, passing through all steps from kicking buildbot, downloading, repackaging, uploading to bitbucket, generating checksums, ...). @mattip what do you think? Would that make sense to try to automate that?
I started a release notice http://pypy.readthedocs.io/en/latest/release-pypy2.7-v5.6.0.html, edits are encouraged.
I'll edit it as soon as my branch is merged! Cheers, Richard
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 could be done automatically (ideally a script that is started on a server and runs to completion there, passing through all steps from kicking buildbot, downloading, repackaging, uploading to bitbucket, generating checksums, ...). @mattip what do you think? Would that make sense to try to automate that?
There is are the force-builds.py and repackage.sh scripts in pypy/tool/release, I just edit repackage.sh by hand before running. AFAIK there is no API to bitbucket for uploading. We could maybe write something to automate the edit of pypy.org/source/download.txt I don't know about the trade-off of where automation maintenance becomes more expensive than just doing it by hand Everyone has their own break even point Matti
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 <matti.picus@gmail.com> wrote:
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 could be done automatically (ideally a script that is started on a server and runs to completion there, passing through all steps from kicking buildbot, downloading, repackaging, uploading to bitbucket, generating checksums, ...). @mattip what do you think? Would that make sense to try to automate that?
There is are the force-builds.py and repackage.sh scripts in pypy/tool/release, I just edit repackage.sh by hand before running. AFAIK there is no API to bitbucket for uploading. We could maybe write something to automate the edit of pypy.org/source/download.txt I don't know about the trade-off of where automation maintenance becomes more expensive than just doing it by hand Everyone has their own break even point Matti _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
Hi, On 2 November 2016 at 17:49, Carl Friedrich Bolz <cfbolz@gmx.de> 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 bitbucket manually (it's really one operation, not even file-by-file). Overall I agree with matti that trying to automate the whole process may be pointless and leads to more work trying to keep the scripts up-to-date, instead of just following the steps in a text file (as long as the number of steps is a small number). A bientôt, Armin.
participants (5)
-
Armin Rigo -
Carl Friedrich Bolz -
Matti Picus -
Richard Plangger -
wlavrijsen＠lbl.gov