We should provide more concrete spec files for projects

- bug

We just made an investigation on all the public packages in openEuler to evaluate their formalization and stability. It seems that currently lots of spec files are not clear enough. We believe that it will bring much difficulty to fully understand the purpose of each patchset for contributors, especially for OS vendors to merge the picked patchsets.

Please let me take the project [httpd](https://gitee.com/src-openeuler/httpd) for elaboration.

1. The earliest changlog only tells us `Package init`
> Advice: It would be better if it could show more information about the baseline version of this package and where the package comes from, community or some other distros? A specific baseline version could be helpful when dealing with dependencies. In particular, it would be very helpful if many patches are already included in this first change (e.g. [lxc](https://gitee.com/src-openeuler/lxc/blob/master/lxc.spec))
2. There are 5 changlogs but only 4 git commits and git history seems meaningless
> Advice: The changlog, with corresponding git commits is very important for contributors to know what's changed. We'd better to keep them in solid relationship and provide substantial content for both.
3. The latest changlog only tells us `delete some patches`
> Advice: There are also several similar messages, e.g. `fix some bugs`, `adjust the spec`, `merge upstream patches`, `fix cves` and etc.
Although we may be able to see which patches are deleted from git commit, probably we should also provide why and how to **delete some patches**. How about provide the ID or URL for the bug/CVE/patch?

Any feedbacks are welcome. Thanks.

openEuler/community

内容风险标识

评论 (8)

openEuler/community .gitee-modal { width: 500px !important; }

内容风险标识