pre-release: 3.0.0 date stamp + metainfo + post-#846 changelog wave - #848
Merged
mrjimenez merged 2 commits intoJun 8, 2026
Merged
Conversation
Two small pre-flight edits ahead of the 3.0.0 tag push on 2026-06-08: - docs/CHANGELOG.md: replace the `2026-MM-DD` placeholder on the "Version 3.0.0 -- alive again" entry with the agreed release date. - org.amule.aMule.metainfo.xml: populate the empty `<releases></releases>` element with a single `<release version="3.0.0" date="2026-06-08"/>` entry. AppStream metadata validators (and Flatpak / KDE Discover / GNOME Software) reject component metadata without at least one release entry; without this the Flatpak build either warns at validation time or ships missing the release-history pane in the software-centre UI. No code change, no behaviour change -- pure metadata.
13 tasks
…ule-project#912) Extends existing categories (preferring extensions over new lines): - Performance/Upload: amule-project#898 SlotAllocation default raised. - Networking & Discovery: wire-parser hardening list extended with amule-project#879/amule-project#882/amule-project#890/amule-project#886; new amuleweb security hardening bullet consolidating ngosang's amule-project#869-amule-project#874 triage (all landed in amule-project#875); amulegui list extended with amule-project#857; shared-folder watcher extended with amule-project#858. - Packaging: Windows installer i18n line extended with amule-project#899. - Internals & Refactoring: new docs-polish + code-quality bullets covering amule-project#851/amule-project#855/amule-project#862/amule-project#888/amule-project#900/amule-project#866/amule-project#867/amule-project#895 and amule-project#909/amule-project#910/amule-project#912. - Translations: new pre-release final-wave bullet covering amule-project#847/amule-project#856/ amule-project#891/amule-project#908/amule-project#860/amule-project#904/amule-project#859/amule-project#863/amule-project#861/amule-project#880/amule-project#911/amule-project#901/amule-project#902/amule-project#889/amule-project#868/amule-project#853. - Bug Fixes & Stability: amule-project#850/amule-project#854/amule-project#878/amule-project#906. - CI: ccache wiring (amule-project#892, amule-project#903) + CodeQL binutils-dev (amule-project#907). Contributors footer gains mifritscher and nguyenhoangminhhieu2004-gif (both first-time contributors). PR index extended through amule-project#912.
got3nks
changed the title
Contributor
Author
|
Added a follow-up commit to extend the changelog with the post-#846 wave — 43 PRs through #912, mapped into existing categories where possible (only two new bullets added: amuleweb security hardening for the #869–#874 triage, and a late-cycle docs-polish bullet). Updated the PR title to reflect the broader scope. |
mrjimenez
pushed a commit
to mrjimenez/amule
that referenced
this pull request
Aug 8, 2026
Continues the wxListCtrl -> wxDataViewCtrl migration (amule-project#180, amule-project#801), porting CDownloadListCtrl onto the CMuleBarRenderer bridge from amule-project#842. The Progress cell is composite rather than a plain chunk bar, so CDownloadBarRenderer draws the base bar and adds the completed-progress strip and percentage on top; CBarFillSpec carries the row's item-data pointer so a renderer subclass can reach its own domain type. The per-row cached wxBitmap is not carried forward: CBarShader::Draw() costs microseconds at this cell size, and a cache keyed by a raw CPartFile* would collide with a freed-and-reused address. FileCtrlItem_Struct is gone -- item data is CPartFile* directly, matching CSharedFilesCtrl -- and m_ListItems becomes a plain std::set, having never backed a real hierarchy. muuli_wdr.cpp drops wxLC_REPORT|wxSUNKEN_BORDER for Downloads, matching 71bdb1a for the lists ported earlier.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two small pre-flight edits ahead of the 3.0.0 tag push on 2026-06-08:
docs/CHANGELOG.md: replace the2026-MM-DDplaceholder on the "Version 3.0.0 — alive again" entry with the agreed release date.org.amule.aMule.metainfo.xml: populate the empty<releases></releases>element with a single<release version="3.0.0" date="2026-06-08"/>entry. AppStream validators (and Flatpak / KDE Discover / GNOME Software) reject component metadata without at least one release entry; without this the Flatpak build either warns at validation time or ships missing the release-history pane in the software-centre UI.No code change, no behaviour change — pure metadata.
Refs
Pre-flight for the 3.0.0 release (cf. ngosang's release planning on amule-org/amule-org.github.io#4).