SERVER_CHANGELOG.md has been added for v0.44.0

[drganjoo]

Motivation and Context

SERVER_CHANGELOG.md has been added (generated through the changelogger tool)

Description

Server side SDK has it's own SERVER_CHANGELOG.md that will have the server side changes carried out in a revision.

Testing

Checklist

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[github-actions]

A new generated diff is ready to view.

• AWS SDK (ignoring whitespace)
• No codegen difference in the Server Test
• No codegen difference in the Server Test Python

A new doc preview is ready to view.

[jdisanti]

Let's talk about how we should go about this. My initial impression is that this shouldn't be a separate .next.toml since we can make changes that affect both the client and the server, and we shouldn't have to copy/paste entries into both files to represent those. Also, GitHub can only have one set of notes for a release, so these really should be combined.

I think we can just add a property to the current changelog toml format that indicates the change is for client, server, or both. Then we can just modify how we render the changelog so that it breaks out separate client/server sections.

[drganjoo]

Let's talk about how we should go about this. My initial impression is that this shouldn't be a separate .next.toml since we can make changes that affect both the client and the server, and we shouldn't have to copy/paste entries into both files to represent those. Also, GitHub can only have one set of notes for a release, so these really should be combined.

I think we can just add a property to the current changelog toml format that indicates the change is for client, server, or both. Then we can just modify how we render the changelog so that it breaks out separate client/server sections.

Oh that would be great if we can have another field in meta tags to indicate whether the change is for client, server or both. Later on, if customers require that they should be able to view only server side changes, we can produce a separate .md file for them.

Thanks

[crisidev]

This PR is not related to Python, I think you made a mistake linking it. It should be #1403

On top of this, the wording of the description is not 100% correct as until #1476 is not merged, the Python system is not usable.

I would reword it like: Initial support to code-generate support to write the business logic in Python, executing on top of Rust. This PR introduce code-generation of operations and simple shapes (Structure and Enum) and add runtime support to start the Hyper server from Python, but does not generate an importable shared library yet.

[github-actions]

A new generated diff is ready to view.

• AWS SDK (ignoring whitespace)
• Server Test (ignoring whitespace)
• Server Test Python (ignoring whitespace)

A new doc preview is ready to view.

[github-actions]

A new generated diff is ready to view.

• AWS SDK (ignoring whitespace)
• Server Test (ignoring whitespace)
• Server Test Python (ignoring whitespace)

A new doc preview is ready to view.

[github-actions]

A new generated diff is ready to view.

• AWS SDK (ignoring whitespace)
• Server Test (ignoring whitespace)
• Server Test Python (ignoring whitespace)

A new doc preview is ready to view.

[crisidev]

Is this PR still relevant?

[drganjoo]

This PR is no longer needed as changelog tool has now been updated to include server SDK changes.