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

2.0 final breaking changes: Final call (until 3.x) #166

Closed
Deadpikle opened this issue Mar 7, 2021 · 0 comments
Closed

2.0 final breaking changes: Final call (until 3.x) #166

Deadpikle opened this issue Mar 7, 2021 · 0 comments
Milestone

Comments

@Deadpikle
Copy link
Collaborator

Deadpikle commented Mar 7, 2021

Things are ready to go for 2.0. All I have to do is deprecate the old things (see #61) and create the newer, final NetSparkleUpdater.Core feed.

This is the last call for any breaking changes before 2.0's release. Any renames, API changes, etc. need to happen ASAP before 2.0 happens. Please list any suggestions here in this thread.

If I hear nothing within a bit of time (week minimum, max 4 weeks or so), I will assume the 2.0 API (names, etc.) is good to go and can be pushed live.

2.0 will probably be the last version that supports .NET Framework. This is undecided, of course. Maybe 2.0 will be the last .NET 4.5 version, and a breaking change will be bumping up to .NET 4.8 or something.

@Deadpikle Deadpikle added this to the 2.0.0 milestone Mar 7, 2021
@Deadpikle Deadpikle pinned this issue Mar 7, 2021
@Deadpikle Deadpikle unpinned this issue Apr 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant