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.

Sign up for GitHub

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

Jump to bottom

Release 3.0 planning #326

Closed
natemcmaster opened this issue Jan 2, 2020 · 3 comments
Closed

Release 3.0 planning #326

natemcmaster opened this issue Jan 2, 2020 · 3 comments
Assignees
@natemcmaster
Labels
planning
Milestone
3.0

Comments

@natemcmaster
Copy link
Owner

natemcmaster commented Jan 2, 2020 •
edited
Loading

Release 3.0 planning is now open for discussion.

I think it's time for a new major version. It should be 3.0 because I think there are some breaking changes worth making. Those are:

Any other breaking changes worth doing now?

I'm also open to doing some new features as well - such as #298 - but I haven't found anything super high priority yet. Please chime in if there is something you'd like to see addressed.

Schedule:

  • RC - March 15
  • Final - March 29
@natemcmaster natemcmaster mentioned this issue Jan 2, 2020
Closed
@natemcmaster natemcmaster pinned this issue Jan 2, 2020
@natemcmaster natemcmaster added this to the 3.0 milestone Jan 5, 2020
@natemcmaster natemcmaster mentioned this issue Jan 7, 2020
Merged
@natemcmaster natemcmaster self-assigned this Mar 9, 2020
@natemcmaster
Copy link
Owner Author

FYI - I released an early pre-release build (3.0 alpha) to nuget.org today. Please start testing and open issues if you find bugs.

@natemcmaster
Copy link
Owner Author

Updated timeline above.

@natemcmaster
Copy link
Owner Author

3.0 is done!

@natemcmaster natemcmaster unpinned this issue Mar 29, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@natemcmaster natemcmaster

Labels
planning
Projects
None yet
Milestone
3.0
Development

No branches or pull requests
1 participant
@natemcmaster