On 2022/11/10 下午4:15, fanghao (A) wrote:
在 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.
Yes, but it maybe another story if we promise like two years' maintain.
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?
Sure, How about one month before Euler release?
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: ...
We can use this for UADK. For openssl-uadk, the testing combination maybe required.
I am not sure whether openssl-uadk can work with any version of UADK from now on. ie. the UADK interface keeps stable.
We found openssl-uadk can not work with some old version UADK before. openssl-uadk depend on UADK, we can add testing combination in openssl-uadk ReleaseNotes. UADK releasenotes may have no such issue.
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.
Since no lts branch, only description in ReleaseNotes can be check. Since one release half year, suppose there is no such issue, like a bug fix happens half year later.
Thanks
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
Acc mailing list -- acc@openeuler.org To unsubscribe send an email to acc-leave@openeuler.org
Help review https://github.com/Linaro/uadk/pull/530
https://github.com/Linaro/uadk_engine/pull/146
And we need provides contents for Features:
------------------ Original ------------------ From: "zhangfei.gao@foxmail.com" <zhangfei.gao@foxmail.com>; Date: Fri, Nov 11, 2022 09:56 AM To: "fanghao (A)"<fanghao11@huawei.com>;"acc"<acc@openeuler.org>;"acc"<acc@lists.linaro.org>; Cc: "Zhangfei Gao"<zhangfei.gao@foxmail.com>; Subject: Re: [Acc] Re: uadk branch & tag policy
On 2022/11/10 下午4:15, fanghao (A) wrote: > > > 在 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 >> >> 1. 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. Yes, but it maybe another story if we promise like two years' maintain. > >> but only the performance and new feautre, like support both >> accelerators and cpu instructions. >> >> >> 2. 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? Sure, How about one month before Euler release?
> >> 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 >> >> 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: > ... We can use this for UADK. For openssl-uadk, the testing combination maybe required.
I am not sure whether openssl-uadk can work with any version of UADK from now on. ie. the UADK interface keeps stable.
We found openssl-uadk can not work with some old version UADK before. openssl-uadk depend on UADK, we can add testing combination in openssl-uadk ReleaseNotes. UADK releasenotes may have no such issue.
> > > 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. Since no lts branch, only description in ReleaseNotes can be check. Since one release half year, suppose there is no such issue, like a bug fix happens half year later.
Thanks
> >> 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 > _______________________________________________ > Acc mailing list -- acc@openeuler.org > To unsubscribe send an email to acc-leave@openeuler.org
uadk_engine: https://github.com/gaozhangfei/uadk_engine/blob/releasenotes/docs/ReleaseNot... https://github.com/Linaro/uadk_engine/pull/148%C2%A0;
------------------ Original ------------------ From: "Zhangfei Gao" <zhangfei.gao@foxmail.com>; Date: Thu, Nov 24, 2022 10:26 AM To: "fanghao (A)"<fanghao11@huawei.com>;"acc"<acc@openeuler.org>;"acc"<acc@lists.linaro.org>;"songzhiqi1"<songzhiqi1@huawei.com>;
Subject: Re: [Acc] Re: uadk branch & tag policy
Help review https://github.com/Linaro/uadk/pull/530
https://github.com/Linaro/uadk_engine/pull/146
And we need provides contents for Features:
------------------ Original ------------------ From:"zhangfei.gao@foxmail.com"<zhangfei.gao@foxmail.com>; Date:Fri, Nov 11, 2022 09:56 AM To:"fanghao (A)"<fanghao11@huawei.com>;"acc"<acc@openeuler.org>;"acc"<acc@lists.linaro.org>; Cc:"Zhangfei Gao"<zhangfei.gao@foxmail.com>; Subject:Re: [Acc] Re: uadk branch & tag policy
On 2022/11/10 下午4:15, fanghao (A) wrote: > > > 在 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 >> >> 1. 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. Yes, but it maybe another story if we promise like two years' maintain. > >> but only the performance and new feautre, like support both >> accelerators and cpu instructions. >> >> >> 2. 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? Sure, How about one month before Euler release?
> >> 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 >> >> 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: > ... We can use this for UADK. For openssl-uadk, the testing combination maybe required.
I am not sure whether openssl-uadk can work with any version of UADK from now on. ie. the UADK interface keeps stable.
We found openssl-uadk can not work with some old version UADK before. openssl-uadk depend on UADK, we can add testing combination in openssl-uadk ReleaseNotes. UADK releasenotes may have no such issue.
> > > 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. Since no lts branch, only description in ReleaseNotes can be check. Since one release half year, suppose there is no such issue, like a bug fix happens half year later.
Thanks
> >> 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 > _______________________________________________ > Acc mailing list -- acc@openeuler.org > To unsubscribe send an email to acc-leave@openeuler.org
-
Zhangfei Gao -
zhangfei.gao＠foxmail.com