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
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.
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: