You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
We have decided to deprecate the following NuGet packages:
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.
The text was updated successfully, but these errors were encountered: