在 2022/11/10 10:54, Zhangfei Gao 写道:
Here is discussion about uadk branch & tag policy
By now, I saw the best example https://github.com/intel/intel-ipsec-mb
- no lts branch, only use tag + ReleaseNotes.txt
Lts branch will cost too much resources, it is hard for a small team like us. For example it is difficult to git am current patch to any tag half year ago.
Unlike OS, it is little meaning for UADK to keep a stable version. We can not attract customer only by maintaining a stable version,
mainly for LTS OS easy to catch the bugfix update for which version that have been intergrated.
but only the performance and new feautre, like support both accelerators and cpu instructions.
- Tag policy
Refer https://github.com/intel/intel-ipsec-mb/blob/main/ReleaseNotes.txt
Basically two releases each year,
looks good to me.
v1.3 September 2022 v1.2 February 2022 v1.1 October 2021 v1.0 April 2021
The time node is not fixed. Do we need fixed time?
No small tag, since uadk is stable enough. is it too simple, suitable? What's the minor tag used for? Other component (openssl-uadk) need refer these tag accordingly.
We may consider minor tag for bug fix? like 1.3.1 for a big bug fix?
looks good to me.
intel-ipsec-mb$ $ git tag v1.0 v1.1 v1.2 v1.3
- ReleaseNotes Contents:
General: Working combination, uadk xxx & openssl-uadk xxx & dpdk xxx
Main change: Like support cpu instructions api change?
Library New algoirthm:
Test Applications:
Fixes:
Can be simplified like this?
Features： ...
Fixes: ...
But how to kown the bugfix for which tag? For example: new tag 2.3.1 for bugfix,how to kown this fix for which version.maybe fix for 2.1 just not for 2.3.
Release status: Unreleased & tag (like v1.3 September 2022) -Unreleased +v1.3 September 2022
Acc mailing list -- acc@openeuler.org To unsubscribe send an email to acc-leave@openeuler.org