Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate old common libaries #2456

Closed
marcovisserFurore opened this issue May 12, 2023 · 1 comment
Closed

Deprecate old common libaries #2456

marcovisserFurore opened this issue May 12, 2023 · 1 comment
Assignees
Labels
idea Something to think about

Comments

@marcovisserFurore
Copy link
Member

We have decided to deprecate the following NuGet packages:

  • Hl7.FhirPath
  • Hl7.Fhir.ElementModel
  • Hl7.Fhir.Serialization
  • Hl7.Fhir.Support.Poco
  • Hl7.Fhir.Support

To ensure a smooth deprecation process, we will consider the following aspects:

Versioning: We will increment the patch number of these libraries to create a new version, such as 4.3.1, and mark this new version as deprecated. By incrementing the patch number, users can easily identify that the package is deprecated while maintaining compatibility with existing dependencies.

Metapackage: Instead of creating individual deprecated packages for each library, we will explore the option of creating a metapackage. This metapackage will contain minimal content, such as a README file and an icon file, to inform users about the deprecation and provide guidance on migrating to alternative solutions.

Deprecation Timing: We will carefully plan the moment to deprecate these packages. It is important to provide sufficient notice to users, allowing them ample time to adjust their projects and migrate to alternative packages. We will consider factors such as the release schedule, the impact on existing users, and any dependencies on the deprecated packages before determining the deprecation timeline.

By addressing these considerations, we aim to deprecate the specified NuGet packages in a manner that minimizes disruption for users and provides clear guidance for transitioning to alternative solutions.

@marcovisserFurore marcovisserFurore added the idea Something to think about label May 12, 2023
@marcovisserFurore marcovisserFurore self-assigned this May 16, 2023
@marcovisserFurore
Copy link
Member Author

During the 2023-05-17 standup meeting, the decision was made to close this issue. The effort required to address the problem is disproportionate to the expected outcome given the relatively small impact of the problem. Furthermore, we have already communicated the transition from SDK 4 to SDK 5 to end users through our documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
idea Something to think about
Projects
None yet
Development

No branches or pull requests

1 participant