Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Document release process #7673

Merged
merged 15 commits into from
Nov 26, 2023
Merged

Document release process #7673

merged 15 commits into from
Nov 26, 2023

Conversation

Dreamsorcerer
Copy link
Member

@webknjaz We really need to document this somewhere. Is this an acceptable place?

@Dreamsorcerer Dreamsorcerer added the bot:chronographer:skip This PR does not need to include a change note label Oct 7, 2023
@webknjaz
Copy link
Member

webknjaz commented Oct 7, 2023

Best put it under docs/ and include somewhere via MyST.

@Dreamsorcerer
Copy link
Member Author

Best put it under docs/ and include somewhere via MyST.

We don't really want it on the main website, right? It's only relevant to aiohttp-admins, so being accessible only in the codebase makes more sense to me.

@webknjaz
Copy link
Member

webknjaz commented Oct 7, 2023

Honestly, I've seen people having this in a separate docs section, somewhere close to the contributing guides so I typically prefer it. It's not something secret. We document how to add changelog fragments there too, which is kinda related.

@webknjaz
Copy link
Member

webknjaz commented Oct 7, 2023

I also know that some people dislike polluting the repo root with many files, which is sometimes a source of complaints..

@Dreamsorcerer Dreamsorcerer changed the title Create RELEASE_PROCESS.md Document release process Oct 8, 2023
@codecov
Copy link

codecov bot commented Oct 8, 2023

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (9af20ac) 97.36% compared to head (a69f206) 97.41%.
Report is 136 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #7673      +/-   ##
==========================================
+ Coverage   97.36%   97.41%   +0.04%     
==========================================
  Files         106      107       +1     
  Lines       31630    32263     +633     
  Branches     3619     3750     +131     
==========================================
+ Hits        30797    31428     +631     
- Misses        630      632       +2     
  Partials      203      203              
Flag Coverage Δ
CI-GHA 97.32% <ø> (+0.04%) ⬆️
OS-Linux 96.99% <ø> (+0.04%) ⬆️
OS-Windows 95.49% <ø> (+0.06%) ⬆️
OS-macOS 96.80% <ø> (+0.18%) ⬆️
Py-3.10.11 95.41% <ø> (+0.05%) ⬆️
Py-3.10.13 96.80% <ø> (-0.02%) ⬇️
Py-3.11.5 ?
Py-3.11.6 96.53% <ø> (?)
Py-3.12.0 96.60% <ø> (?)
Py-3.8.10 95.38% <ø> (+0.05%) ⬆️
Py-3.8.18 96.73% <ø> (-0.02%) ⬇️
Py-3.9.13 95.38% <ø> (+0.06%) ⬆️
Py-3.9.18 96.77% <ø> (-0.01%) ⬇️
Py-pypy7.3.11 ?
Py-pypy7.3.13 96.23% <ø> (?)
VM-macos 96.80% <ø> (+0.18%) ⬆️
VM-ubuntu 96.99% <ø> (+0.04%) ⬆️
VM-windows 95.49% <ø> (+0.06%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Comment on lines +1 to +2
:orphan:

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Apparently, the meaning of orphan is just that it is not included it a toctree, not that it is undiscoverable (something which is confusing, as most users expect orphan to mean the latter)...

I'm not really sure we want to include it in a toctree? The sidebar has a link directly to contributing, I'm not sure it makes sense to include another link from the sidebar for something almost nobody needs to see. And I don't really see any other toctrees to use.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.


#. Start on the branch for the release you are planning (e.g. ``3.8`` for v3.8.6): ``git checkout 3.8 && git pull``
#. Update the version number in ``__init__.py``.
#. Run ``towncrier``.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No args?

Copy link
Member Author

@Dreamsorcerer Dreamsorcerer Oct 11, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't use any. Do you have any arguments when you run it? I was just guessing.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Dreamsorcerer I think I was testing with --draft and always passing --version. Though, I suppose Towncrier has some ability to import the version from a Python module. That doesn't always work, not for C-extension based codebases, anyway.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Right, I was wondering where it kept getting the version from. I just corrected it in the file manually.

Copy link
Member

@webknjaz webknjaz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Dreamsorcerer I left some notes. They are not mandatory and can be fixed in follow-ups. That's up to you.

@Dreamsorcerer
Copy link
Member Author

@webknjaz Would it be fine to delete some of the oldest 3.x branches? Not sure if there's a reason they've been kept around, but they just seem so old now that they are not useful, and it's a bit of a nuisance that I now have to scroll to select the correct branch in a backport PR (all upto 3.8 are selectable without scrolling).

@Dreamsorcerer Dreamsorcerer added backport-3.9 Trigger automatic backporting to the 3.9 release branch by Patchback robot backport-3.10 Trigger automatic backporting to the 3.10 release branch by Patchback robot labels Nov 26, 2023
@Dreamsorcerer Dreamsorcerer merged commit aa7d1a8 into master Nov 26, 2023
32 of 34 checks passed
@Dreamsorcerer Dreamsorcerer deleted the Dreamsorcerer-patch-5 branch November 26, 2023 15:36
Copy link
Contributor

patchback bot commented Nov 26, 2023

Backport to 3.9: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.9/aa7d1a8fcad4ac4f1f0eae577f4c1947ebc1acf3/pr-7673

Backported as #7909

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

patchback bot pushed a commit that referenced this pull request Nov 26, 2023
(cherry picked from commit aa7d1a8)
Copy link
Contributor

patchback bot commented Nov 26, 2023

Backport to 3.10: 💚 backport PR created

✅ Backport PR branch: patchback/backports/3.10/aa7d1a8fcad4ac4f1f0eae577f4c1947ebc1acf3/pr-7673

Backported as #7910

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

patchback bot pushed a commit that referenced this pull request Nov 26, 2023
(cherry picked from commit aa7d1a8)
Dreamsorcerer added a commit that referenced this pull request Nov 26, 2023
**This is a backport of PR #7673 as merged into master
(aa7d1a8).**

Co-authored-by: Sam Bull <git@sambull.org>
Dreamsorcerer added a commit that referenced this pull request Nov 26, 2023
**This is a backport of PR #7673 as merged into master
(aa7d1a8).**

Co-authored-by: Sam Bull <git@sambull.org>
@webknjaz
Copy link
Member

@webknjaz Would it be fine to delete some of the oldest 3.x branches? Not sure if there's a reason they've been kept around, but they just seem so old now that they are not useful, and it's a bit of a nuisance that I now have to scroll to select the correct branch in a backport PR (all upto 3.8 are selectable without scrolling).

@Dreamsorcerer I think it's fine for as long as there are tags on the tops of those branches.

@@ -0,0 +1,57 @@
:orphan:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Dreamsorcerer also, since you put a link to this doc from another doc, Sphinx won't consider it orphan anymore. So it's not really needed either way.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I mentioned above, that's not what orphan means to Sphinx. It literally just means that it is not in a toctree, not that it is unreachable. So, it is needed in its current state.

xiangxli pushed a commit to xiangxli/aiohttp that referenced this pull request Dec 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-3.9 Trigger automatic backporting to the 3.9 release branch by Patchback robot backport-3.10 Trigger automatic backporting to the 3.10 release branch by Patchback robot bot:chronographer:skip This PR does not need to include a change note
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants