Should You Create a New Tag for a .NET Framework 4 to .NET Core Port? Factors to Consider

When considering whether to create a new tag for a NuGet package that is a port from .NET Framework 4 to .NET Core, there are a few factors to consider. Ultimately, the decision will depend on the specific circumstances and goals of your project or community. Here are some considerations to help you make an informed decision:

1. Significance of the changes: Evaluate the extent of the changes made during the porting process. If the port involves substantial modifications, bug fixes, or new features, it might be appropriate to create a new tag to indicate the significant differences between the original package and the ported version.

2. Compatibility and usage: Assess the compatibility between the original package and the ported version. If the ported package maintains a high level of compatibility with the original package, it might not be necessary to create a new tag. However, if the ported version introduces breaking changes or requires different usage patterns, a new tag could be useful to distinguish between the two versions.

3. User expectations: Consider the expectations of the users who will be consuming the NuGet package. If users benefited from being able to specifically identify and search for the ported version, a new tag can provide them with a clear distinction. This can be particularly helpful for those who are specifically looking for packages targeting .NET Core.

4. Community and maintenance: Evaluate the impact on the package's community and maintenance efforts. If the package has an active user base and contributors, creating a new tag could help facilitate discussions, documentation, and issue tracking specific to the ported version. It can also make it easier for maintainers to manage and support both versions separately.

5. NuGet package naming conventions: Consider any existing conventions or guidelines within the NuGet ecosystem regarding package naming and versioning. It's worth checking if there are established practices for handling ported packages or major framework version updates, as this can provide guidance on whether to create a new tag or use a different approach to indicate the changes.

By considering these factors, you can make an informed decision on whether creating a new tag for the ported NuGet package is appropriate in your specific context. It's important to communicate any changes clearly to users and provide documentation to guide them in migrating from the original package to the ported version, if necessary.