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,
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,
v1.3 September 2022
v1.2 February 2022
v1.1 October 2021
v1.0 April 2021
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?
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:
Release status: Unreleased & tag (like v1.3 September 2022)
-Unreleased
+v1.3 September 2022
Meeting minutes:
1. UADK branch maintaince
Conclusion:
Using ReleaseNotes + tag, no LTS branch
ReleaseNotes is updated by patch submitter, and change state from
"Unreleased" to "tag release" when release.
No LTS branch considering resources requirement,
May consider other develop branch when interface change a lot, like
openssl 1.1 to openssl 3.0
Todo
tag policy: how to decide when using new tag.
2. vsva
vsva
Nvida has done a lot of works for nested mode, still not verify
qemu:
https://github.com/yiliu1765/qemu/commits/qemu-iommufd-6.0-rc3
kernel:
https://github.com/yiliu1765/iommufd/commits/iommufd-v6.0-rc2-nesting
3. acc(a)lists.linaro.org
register via email to acc-subscribe(a)lists.linaro.org
Discussing uadk developing, code review still use github, other things
can use acc(a)lists.linaro.org.
Thanks
On 2022/11/8 下午7:24, openEuler conference wrote:
> 您好！
>
> sig-AccLib SIG 邀请您参加 2022-11-09 11:00 召开的Zoom会议
>
> 会议主题：AccLib sig 双周例会
>
> 会议内容：
> zoom会议，ID: 91879279131
> 固定的会议链接：https://linaro-org.zoom.us/j/91879279131
> 1.进展讨论 2.自由讨论
>
> 会议链接：https://us06web.zoom.us/j/88249285062?pwd=Y2JnVW9GUkNzMWp2cW1QNHFGbE1RZz09
>
> 会议纪要：https://etherpad.openeuler.org/p/sig-AccLib-meetings
>
> 温馨提醒：建议接入会议后修改参会人的姓名，也可以使用您在gitee.com的ID
>
> 更多资讯尽在：https://openeuler.org/zh/
>
>
>
>
> Hello!
>
> openEuler sig-AccLib SIG invites you to attend the Zoom conference will be held at 2022-11-09 11:00,
>
> The subject of the conference is AccLib sig 双周例会,
>
> Summary:
> zoom会议，ID: 91879279131
> 固定的会议链接：https://linaro-org.zoom.us/j/91879279131
> 1.进展讨论 2.自由讨论
>
> You can join the meeting at https://us06web.zoom.us/j/88249285062?pwd=Y2JnVW9GUkNzMWp2cW1QNHFGbE1RZz09.
>
> Add topics at https://etherpad.openeuler.org/p/sig-AccLib-meetings.
>
> Note: You are advised to change the participant name after joining the conference or use your ID at gitee.com.
>
> More information: https://openeuler.org/en/
>
>
> _______________________________________________
> Acc mailing list -- acc(a)openeuler.org
> To unsubscribe send an email to acc-leave(a)openeuler.org
