[CHORE] Prepare 0.3.3 release (#161)

CHANGELOG.md

@@ -12,23 +12,22 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased] - YYYY-MM-DD
 
-### Fixed
-
-- Issue with resolving path on win platforms
-- CI pipeline on win platform
-
 ----
 > Unreleased changes must be tracked above this line.
 > When releasing, Copy the changelog to below this line, with proper version and date.
 > And empty the **[Unreleased]** section above.
 ----
 
-## [0.3.3] - 2022-02-03
+## [0.3.3] - 2022-02-08
 
 ### Fixed
 
-- Provided bugfix for path resolution on Win systems
+- path resolution on win platforms
+- Provided bugfix for non-DBFS based mlflow artifact locations
 
+### Added
+
+- CI pipeline on win platform
 
 ## [0.3.2] - 2022-01-31
 

PULL_REQUEST_TEMPLATE.md

@@ -12,15 +12,6 @@ _Put an `x` in the boxes that apply_
 - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
 - [ ] Documentation Update (if none of the other choices apply)
 
-## 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 code._
-
-- [ ] Lint and unit tests pass locally with my changes
-- [ ] I have added tests that prove my fix is effective or that my feature works
-- [ ] I have added necessary documentation (if appropriate)
-- [ ] Any dependent changes have been merged and published in downstream modules
-
 ## Further comments
 
 If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...