Preparation for Release 2.1.0 (#93)

TROUBLESHOOTING.md

@@ -152,4 +152,4 @@ When opening the cloned repo in VS Code, you may see a pop up saying "Some proje
 
 When using OpenLineage `0.11.0` with Databricks Runtime `10.4` and executing a command like `df.write.mode("overwrite").saveAsTable("default.mytable")`, the driver crashes. This is due to a bug in OpenLineage which did not separate out certain commands for Spark 3.2 vs Spark 3.1.
 
-**Solution**: You can use `mode("append")` to add data to the table instead. Alternatively, you may explore using OpenLineage `0.12.0` which has resolved this issue. However, the Solution Accelerator is not fully tested on `0.12.0` and may have other issues in our supported use cases.
+**Solution**: Upgrade to OpenLineage `0.13.0` which has a fix for the issue.

deployment/infra/newdeploymenttemp.json

@@ -217,7 +217,7 @@
 						"[concat('Microsoft.Web/sites/', variables('functionAppName'))]"
 					],
 					"properties": {
-						"packageUri": "http://aka.ms/APFunctions2-0"
+						"packageUri": "http://aka.ms/APFunctions2-1"
 					}
 				}
 			]

docs/extending-source-support.md

@@ -68,7 +68,7 @@ The configuration format can be complex, so a command line verification tool ([Q
 dotnet build
 ```
 
-Modify the [config.json](../tests/tools/QualifiedNameConfigTester/config.json) file to include your new source configuration, and then run the utility from the bin directory specifying the build file path.  For example:
+Modify the [config.json](../function-app/adb-to-purview/tests/tools/QualifiedNameConfigTester/config.json) file to include your new source configuration, and then run the utility from the bin directory specifying the build file path.  For example:
 
 ```bash
 .\bin\Debug\net6.0\QualifiedNameConfigTester.exe

docs/release-checklist.md

@@ -1,10 +1,10 @@
 # Release Checklist
 
-* [ ] Update [deploy-base.md](../deploy-base.md) to reflect the newest version.
-* [ ] Update [deploy-demo.md](../deploy-demo.md) to reflect the newest version.
-* [ ] Create a new aka.ms url to point to the next release (e.g. )
+* [ ] Create a branch to prepare for release (e.g. `feature/prepareForReleaseX-Y`). Make the following changes on the newly created branch.
+* [ ] Create a new aka.ms url to point to the next release (e.g. aka.ms/APFunctions{MAJOR}-{MINOR} aka.ms/APFunctions2-1)
 * [ ] Update the [newdeploymenttemp.json](../deployment/infra/newdeploymenttemp.json) with the new aka.ms url.
-* [ ] Create a git tag with pattern X.Y.Z where X, Y, and Z follow the [semver pattern](https://semver.org/). Then push the tag to the origin git repo (github).
+* [ ] Perform the Pull Request from `feature/prepareForReleaseX-Y` into `main`
+* [ ] On `main` Create a git tag with pattern X.Y.Z where X, Y, and Z follow the [semver pattern](https://semver.org/). Then push the tag to the origin git repo (github).
     * ```bash
       git tag X.Y.Z
       git push origin --tags