Repository navigation
Replies: 22 comments 30 replies
|
@Chocobo1, @thalieht, @xavier2k6, @stalkerok Due to the critical lack of free time for the maintainer of the project, we have problems making releases in a reasonable time.In this regard, I recently had another conversation with him about optimizing the release preparation process and the possible involvement that team members could take in this. |
|
To begin with, the stumbling block (as it turned out) is often the preparation of a Changelog.
Steps 2. and 3. can be done partially and completed after the draft is published (during discussion process). If someone could prepare a Changelog draft soon, please let us know. |
|
We could also take on another routine, such as synchronizing translations with Transifex. If so, @sledgehammer999 could provide us with instructions on how to do it. |
|
And the most important thing is that @sledgehammer999 seems to have generally agreed on the need to automate the release builds. But, as I believe, someone who is familiar with this topic (e.g. how it is implemented in other OSS projects) should provide him with some roadmap explaining what and how we need to do. |
Had a quick look: |
|
Here's a list. I didn't check if they are backported. Changelog?Both gui and webui but not a feature or a bugfix? Swap add file/link buttons on toolbar (lemantisee) |
This comment has been hidden.
This comment has been hidden.
|
@glassez @thalieht @Chocobo1 @stalkerok
I'll take this task on, will post here (in separate posts) following the outlined stages below:
|
5.2 milestone - PR's closed/merged 5.2 milestone - Full list of current PR's (288)Add option to toggle speed indicator in dock #23972 (Actual Backport of #23133) |
5.2 milestone - Filtered out/Excluded PR'sAdd option to toggle speed indicator in dock #23972 (Actual Backport of #23133) 5.2 milestone - Potential PR's to be included in DRAFT ChangelogWebUI: fix applying color scheme in framed windows #23958 |
PLACEHOLDER |
|
I've written a simple Python script that extracts a list of PRs using GitHub API. Maybe it will be useful. import requests
owner = "qbittorrent"
repo = "qBittorrent"
total = 0
page = 1
while True:
url = f"https://api.github.com/repos/{owner}/{repo}/pulls?state=closed&per_page=100&page={page}"
response = requests.get(url)
if response.status_code != 200:
print(f"Failed to fetch pull requests. Status code: {response.status_code}.")
exit()
pull_requests = response.json()
for pr in pull_requests:
milestone = pr['milestone']
if milestone is None or not milestone['title'] == '5.2':
continue
is_merged = pr['merged_at'] is not None
if not is_merged:
continue
labels = [label['name'] for label in pr['labels']]
discarded_labels = ['Hotfix', 'Code cleanup', 'Backport']
if all(not label in labels for label in discarded_labels):
print(f"{pr['title']} ({pr['user']['login']}) #{pr['number']}")
total += 1
link_header = response.headers['link']
if not 'rel="next"' in link_header:
break
page += 1
print()
print(f'TOTAL: {total}')Here is an example of its result: ChangelogFix About dialog text cutoff on macOS (M-Hassan-Raza) #23906 |
|
I suggest taking one of the PR lists above as a basis and working with it. |
|
I have used the Hopefully, my approach has given you ideas to integrate on your own workflow. I know that mine isn't perfect. In new major releases I also utilize the |
|
Another important thing in my opinion is that we should not treat the produced Changelog as something immutable. If any mistake is found in it after publication, we should be able to fix it. What do you think? |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
More lists using this method #23967 (comment) Changelog
Unsure changelog entries
Rejected changelog entries
Concatenated
|
I always collapse translations to one entry in the form of: Finally, I think most of the NSIS translations have been backported already. |
|
A general suggestion for the future workflow: For work regarding next major release: Frequent contributors should include a Changelog entry with their PR. Non-frequent contributors should be asked to do so during review. For both this shouldn't be a hard requirement for PR merging. For work regarding next minor release: The person doing the backports should add Changelog entries. Realistically minor versions have few user-facing changes. Also it can be a collaboration effort. Once person A opens a PR, other people of the team (even bug triagers), can actually push a commit to that PR's branch. Even if that branch belongs to person's A repo. It requires one to be comfortable using git though. So person A decides the backports and person B(or C etc) does the Changelog. |
|
FYI, I've improved my python script: import requests
import datetime as dt
owner = "qbittorrent"
repo = "qBittorrent"
token = None # You can paste your GitHub fine-grained token instead
headers = {"Authorization": f"Bearer {token}"} if token is not None else None
merged_since = dt.datetime.fromisoformat("2026-04-19T00:00:00Z")
total = 0
page = 1
done = False
while not done:
url = f"https://api.github.com/repos/{owner}/{repo}/pulls?state=closed&sort=updated&direction=desc&per_page=100&page={page}"
response = requests.get(url, headers=headers)
if response.status_code != 200:
print(f"Failed to fetch pull requests. Status code: {response.status_code}.")
exit()
pull_requests = response.json()
for pr in pull_requests:
milestone = pr['milestone']
if milestone is None or not milestone['title'] == '5.3':
continue
is_merged = pr['merged_at'] is not None
if not is_merged:
continue
merged_at = dt.datetime.fromisoformat(pr['merged_at'])
if merged_at < merged_since:
done = True
break
labels = [label['name'] for label in pr['labels']]
discarded_labels = ['Hotfix', 'Code cleanup', 'Backport']
if all(not label in labels for label in discarded_labels):
print(f"{pr['title']} ({pr['user']['login']}) #{pr['number']}")
total += 1
if not done:
link_header = response.headers['link']
if not 'rel="next"' in link_header:
break
page += 1
print()
print(f'TOTAL: {total}') |

Uh oh!
There was an error while loading. Please reload this page.
Note that this discussion is primarily for project members.
All reactions