updated pr template to check backward compatibility

[shreyapandit]

Issue #, if available:

Description of changes:
Update PR template to add checks for backward incompatibility

Testing done:

Merge Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.

General

• I have read the CONTRIBUTING doc
• I used the commit message format described in CONTRIBUTING
• I have passed the region in to all S3 and STS clients that I've initialized as part of this change.
• I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have checked that my tests are not configured for a specific region or account (if appropriate)
• I have used unique_name_from_base to create resource names in integ tests (if appropriate)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[sreedes]

Sounds good. It will be good to come up with a guideline page and have more explanations on what constitutes backward (in)compatible code and point it to that in the future, so that contributors can declare this confidently.

[sagemaker-bot]

AWS CodeBuild CI Report

• CodeBuild project: sagemaker-python-sdk-unit-tests
• Commit ID: e3f4f4a
• Result: SUCCEEDED
• Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

[shreyapandit]

Sounds good. It will be good to come up with a guideline page and have more explanations on what constitutes backward (in)compatible code and point it to that in the future, so that contributors can declare this confidently.

Sure!