5.0.x release suggestions
Would be nice to have fixes for these in the patch release:
5.0.1
- [x] https://github.com/capstone-engine/capstone/issues/2066
- [x] https://github.com/capstone-engine/capstone/pull/2080
- [x] https://github.com/capstone-engine/capstone/pull/2086
- [x] https://github.com/capstone-engine/capstone/pull/2095
- [x] https://github.com/capstone-engine/capstone/pull/2096
- [x] https://github.com/capstone-engine/capstone/pull/2097
- [x] https://github.com/capstone-engine/capstone/pull/2088
- [x] https://github.com/capstone-engine/capstone/pull/2090
- [x] https://github.com/capstone-engine/capstone/pull/2100
- [x] https://github.com/capstone-engine/capstone/pull/2108
- [x] https://github.com/capstone-engine/capstone/pull/2134
5.0.2
- [ ] https://github.com/capstone-engine/capstone/issues/2154
- [x] https://github.com/capstone-engine/capstone/issues/2145
- [ ] https://github.com/capstone-engine/capstone/issues/2144
- [ ] https://github.com/capstone-engine/capstone/issues/2147
- [ ] https://github.com/capstone-engine/capstone/issues/2079
- [ ] https://github.com/capstone-engine/capstone/issues/2128
- [ ] https://github.com/capstone-engine/capstone/issues/2025
- [ ] https://github.com/capstone-engine/capstone/issues/2005
- [ ] https://github.com/capstone-engine/capstone/issues/1955 (if it still happens)
- [ ] https://github.com/capstone-engine/capstone/issues/1893
- [ ] https://github.com/capstone-engine/capstone/pull/2148
- [ ] https://github.com/capstone-engine/capstone/issues/2153
- [ ] Publish news on http://www.capstone-engine.org/ for the 5.0.2 release
After they are fixed in the next branch, fixes could be cherry-picked to the v5 branch one by one for the release.
There are also many PPC regressions found by @wargio but they will be fixed in the https://github.com/capstone-engine/capstone/pull/2013 so it doesn't make sense trying to fix them in the patch release.
@kabeor you need to cherry-pick corresponding commits from next to v5: https://github.com/capstone-engine/capstone/tree/v5
Well looks like there are some misunderstood. v5 should merge something only if we are ready to release a version. so I think we needn't cherry-pick.
@kabeor but you already cherry-picked some of these fixes - SH and ARM VFP fix. Idea is to cherry-pick these fixes and tag 5.0.1
@XVilka Aha @aquynh did this. I should talk with him about this tmw😂
Looks like only x86 regression and deprecated modules left in this list, the rest was merged
also the ppc regressions
@wargio there are way too many, not sure if it makes sense to devote time instead of investing time in auto-sync PPC
@kabeor Could we add a note to the 5.0.1 release, that the v6 release will bring some big changes (possibly linking to https://github.com/capstone-engine/capstone/pull/2124)? In this case people have the chance to decide if they might want to skip v5 altogether.
@Rot127 ok, it's a perfect time to announce that.
@kabeor Great! You can link to the WIP release text here or to the PR.
@kabeor Could you please also a line that everyone is welcome to give early feedback regarding v6. The whole auto-sync thing still misses more eyes from the outside. And new releases have definitely more impact than issues.
@kabeor @aquynh I suggest to cherry-pick already existing fixes and tag 5.0.1 Not everything was fixed but some most annoying things were fixed already - the rest could land in 5.0.2 or something like that.
@kabeor @aquynh ping
@kabeor @aquynh ping
#2141
Thank you, @kabeor!
@kabeor looks like some assets missing from the release?
@XVilka I see. Reference to Docs: Workflows are not triggered for the created, edited, or deleted activity types for draft releases.. Maybe published field will fix this. Will test on next release.
@gerph added your issues here. Worth carving a quick 5.0.2 bugfix release when fixes are available.
@gerph added your issues here. Worth carving a quick 5.0.2 bugfix release when fixes are available.
Thanks :-)
There's no ticket for it, but it probably should apply to all the releases... a reminder to update the cs_version so that each release could be differentiated, would be good.
@XVilka Could you add https://github.com/capstone-engine/capstone/issues/2177 and https://github.com/capstone-engine/capstone/issues/2174 to the list?
@XVilka This small problem can also be fixed issues: #2177
@kabeor for 5.0.2 please cherry-pick https://github.com/capstone-engine/capstone/pull/2221 then.
Close this because we now track issues with milestones, see: https://github.com/capstone-engine/capstone/milestone/4