feat: release 2.10.3

[bzp2010]

What this PR does / why we need it:

Update rockspec and CHANGELOG for version 2.10.3. And updates related to version code and documentation will be provided in the PR of release/2.10 to prevent affecting the master branch.

Pre-submission checklist:

• Did you explain what problem does this PR solve? Or what new features have been added?
• Have you added corresponding test cases?
• Have you modified the corresponding document?
• Is this PR backward compatible? If it is not backward compatible, please discuss on the mailing list first

[juzhiyuan]

Hi @bzp2010, do we need this? #5958

[bzp2010]

Hi @bzp2010, do we need this? #5958

@juzhiyuan They will be pushed to a different branch. The use of this PR for pushing to master branch can be found in the following PR. In this release, some of the changes involved in the following PR [1] will be split into two parts to prevent affecting the master branch code.

[1] #5508

[spacewander]

Merge this changelog will confuse the user about the timeline. Those fixes are in 2.10.3 but not in 2.11.0. Also, when we release 2.12.0, we have to mention some of those fixes again.

And this PR doesn't update the Chinese version of CHANGELOG.

[bzp2010]

Merge this changelog will confuse the user about the timeline. Those fixes are in 2.10.3 but not in 2.11.0. Also, when we release 2.12.0, we have to mention some of those fixes again.

And this PR doesn't update the Chinese version of CHANGELOG.

Hi, @spacewander.

I understand what you said, which may cause confusion to users.

I added a partial description of what PRs were merged into this "LTS maintenance release" for version 2.10.3 as shown below, does this ease the confusion? Or do I need to remove CHANGELOG and make it provide only in the 2.10 branch. (But a CHANGELOG in the master branch is also need? How should I do it?)

Also, I have added the Chinese version of CHANGELOG.

[spacewander]

@bzp2010
Your solution doesn't solve the problem I mention...

[spacewander]

Maybe we don't need to archive this rockspec? We don't merge the code into the default branch.

[bzp2010]

@spacewander Here it is marked for installation using the 2.10.3 git tag, as far as I know this could potentially be used when packaging various container images?

https://github.com/apache/apisix-docker/blob/5d3c4c63d21f0c40655d005fdb9cb3746f2e4af3/alpine/Dockerfile#L22

So, IMO, we need it.

[bzp2010]

Hi, @spacewander. Do I need to make changes for this?

[spacewander]

I see.