Update SONiC FRR Upgrade Process

[eddieruan-alibaba]

Update this doc based on 0918's Routing WG's discussion. The meeting minutes could be found at

https://lists.sonicfoundation.dev/g/sonic-wg-routing/wiki/40585

[mssonicbld]

/azp run

[azure-pipelines]

No pipelines are associated with this pull request.

[eddieruan-alibaba]

https://github.com/eddieruan-alibaba/SONiC/blob/eruan-frrmaintainers/tsc/frr/sonic_frr_update_process.md

[mssonicbld]

/azp run

[azure-pipelines]

No pipelines are associated with this pull request.

[mssonicbld]

/azp run

[azure-pipelines]

No pipelines are associated with this pull request.

[mssonicbld]

/azp run

[azure-pipelines]

No pipelines are associated with this pull request.

[mssonicbld]

/azp run

[azure-pipelines]

No pipelines are associated with this pull request.

[mssonicbld]

/azp run

[azure-pipelines]

No pipelines are associated with this pull request.

[pbrisset]

Is there any plan to attribute SONiC points to FRR commits, review?
Is there any plan to attribute SONiC points to maintainers?

[eddieruan-alibaba]

Is there any plan to attribute SONiC points to FRR commits, review? Is there any plan to attribute SONiC points to maintainers?

I will bring this discussion to TSC as a separate topic.

[mssonicbld]

/azp run

[azure-pipelines]

No pipelines are associated with this pull request.

[venkit-nexthop]

I have a few questions. But overall, this new upgrade process looks good to me.
Thanks for putting it together and getting consensus with the community.

[mssonicbld]

/azp run

[azure-pipelines]

No pipelines are associated with this pull request.

[mssonicbld]

/azp run

[azure-pipelines]

No pipelines are associated with this pull request.

[mssonicbld]

/azp run

[azure-pipelines]

No pipelines are associated with this pull request.

[mssonicbld]

/azp run

[azure-pipelines]

No pipelines are associated with this pull request.

[mssonicbld]

/azp run

[azure-pipelines]

No pipelines are associated with this pull request.

[eddieruan-alibaba]

@StormLiangMS @dgsudharsan @venkatmahalingam can you help to review it? I have taken care current comments. Need the approval from Microsfot, Nvidia and Dell before I present it to TSC.

[StormLiangMS]

One thing I’d like to clarify: the release manager will review critical bug fixes from FRR on a monthly basis for the current release and the immediately preceding one, but not for all earlier releases, correct? I think that approach should be fine in most cases. However, considering the lifecycle of each SONiC release, should we consider extending it to cover the previous three releases? I agree this may not be as critical as the most recent one, and we can revisit it if the community feels it’s necessary. Everything else looks good to me — thanks a lot for driving this. @eddieruan-alibaba

[eddieruan-alibaba]

One thing I’d like to clarify: the release manager will review critical bug fixes from FRR on a monthly basis for the current release and the immediately preceding one, but not for all earlier releases, correct? I think that approach should be fine in most cases. However, considering the lifecycle of each SONiC release, should we consider extending it to cover the previous three releases? I agree this may not be as critical as the most recent one, and we can revisit it if the community feels it’s necessary. Everything else looks good to me — thanks a lot for driving this. @eddieruan-alibaba

Let's start with monitoring 2 releases. If we see the needs, we could update this doc in the future.

[eddieruan-alibaba]

@dgsudharsan I got approvals from 5 different organizations. Need your approval to represent NV.