Rot127

> As, I guess, Capstone is still stabilizing it makes sense to clean up this stuff now.  Yes, the stabilizing part is the whole reason we changed it. I know...

@kabeor > I am really do my best to push the whole contribution process. We do very much appreciate this! > The answer is more closer code review. [...] But...

@kabeor @aquynh Any news in this matter?

Regarding point 3: Labels could be something like: - `LLVM-module-files` (`inc` and translated), - `CS-module-files` (`ARCHModule.*`, `ARCHMapping.*` etc.) - `CS-core-files` (`cs_priv.h`, `cstool.c` etc.) - `LLVM-core-files` (`MCInst.*`, `MCInstrDesc.*` etc.) - `auto-sync-files`...

@AngelDev06 Any objections against this (https://github.com/capstone-engine/capstone/pull/2231/commits/cff87a38061edb2a8968ef37cef6e0642bef6332) naming convention?

Closed due to: https://github.com/capstone-engine/capstone/pull/2045#issuecomment-2068848678

@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...

@kabeor Great! You can link to the WIP release text [here](https://github.com/Rot127/capstone/blob/v6-release-guide/docs/cs_v6_release_guide.md) 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...

@XVilka Could you add https://github.com/capstone-engine/capstone/issues/2177 and https://github.com/capstone-engine/capstone/issues/2174 to the list?