Release 1.1.0

[adeacetis]

Overview

This Pull Request marks a significant milestone in our project's version control history. Up until now, our team has not been following versioning best practices correctly, leading to a situation where the initial commit version serves as our baseline. This update represents a concerted effort to catch up and establish a proper versioning system for our project.

Changes

• Version Bump:
  We have incrementally updated the project version to bring it in line with where it should be based on the work that has been done since the initial commit.

• Revised Versioning Strategy:
  Going forward, we are instituting a more structured versioning strategy to ensure that our project versions accurately reflect the progress and changes made over time. This strategy will encompass semantic versioning (SemVer) principles to better convey the nature of changes.

• Documentation and Changelog Updates (in progress):
  The changelog and documentation have been updated to reflect the historical changes that were previously unaccounted for.

• Code Clean-Up: We've taken this opportunity to address some code quality issues that have accumulated since the initial commit, making our codebase more maintainable and robust.

Why This Matters

1. Clarity: Proper versioning is essential for providing clarity and context about the state and history of the project. This clarity is crucial for both our team and any collaborators or users.

2. Maintenance: Structured versioning simplifies maintenance, as it allows us to identify which features were added, modified, or deprecated in each release.

3. Collaboration: With a reliable versioning system, collaboration with external developers, third-party integrations, and other stakeholders becomes more efficient and less error-prone.

Let's use this as a turning point in our project's version control history to maintain transparency, enhance collaboration, and continue delivering value to our users.