Add iOS release support.#2980
Conversation
Done, but with slug
This will go here, and let's wait until closer to release day:
Added commented out |
Thanks - the capitalisation in the slug was macOS autocorrect being helpful. I didn't notice it "fixed" the content for me.
👍 |
|
@hugovk what all from the release side needs to be done here? or cna i merge now? |
hugovk
left a comment
There was a problem hiding this comment.
This will go here, and let's wait until closer to release day:
I've just added this and it's now under the Downloads menu:
- Under Boxes/Boxes, add a link for
<a href="/downloads/ios/">iOS</a>to thedownload-banner.Added commented out
<!--<a href="/downloads/ios/">iOS</a>,-->for now:
And I've just uncommented this, and iOS is now visible at https://www.python.org/downloads/
And the linked https://www.python.org/downloads/ios/ shows 3.15 b1-b3 as expected.
@JacobCoffee This PR is just tests, so can be merged whenever, but is a good placeholder for getting the live changes done.
@freakboy3742 I think we're all good now for the live python.org changes?
I believe so - an actual release that had the code live was the only thing blocking this. |
The following changes will need to be made manually on the live python.org site prior to a release that includes iOS artefacts (hopefully 3.15.0b1):
iOS)downloads/ios)<a href="/downloads/ios/">iOS</a>to thedownload-banner.This PR adds fixtures that reflect the same changes, so that developers have a site that reflects what the live site will have.
The fixtures cheat a little bit, piggybacking off the fixtures added to support Android releases. There are no 3.14 releases for iOS; but the purpose of the fixtures is to demonstrate that rendering of the download page works, rather than being a canonical data source.
Refs python/cpython#140189