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

Establish Plan for 1.0 release #318

Open
RichardWarburton opened this issue Dec 13, 2019 · 3 comments
Open

Establish Plan for 1.0 release #318

RichardWarburton opened this issue Dec 13, 2019 · 3 comments
Assignees
@RichardWarburton

Comments

@RichardWarburton
Copy link
Contributor

Artio should release a 1.0 version and move to semantic versioning after that point. Recently we've made small but breaking API changes regularly. Ideally this would end. This issue includes:

  • Risk Assessment of recent releases to identify API changes and figure out how to avoid them. (Eg: introducing parameter objects like Aeron's Header that avoids breaking changes)
  • Potentially marking parts of the API experimental to avoid commitment to an API that we expect to change soon or aren't convinced is stable.
@RichardWarburton RichardWarburton self-assigned this Dec 13, 2019
@RichardWarburton
Copy link
Contributor Author

The idea has been mooted to do an RC or a beta version before full 1.0 release.

@mjpt777
Copy link
Contributor

mjpt777 commented Jan 14, 2020

RC version makes sense.

@RichardWarburton
Copy link
Contributor Author

RichardWarburton commented Jan 21, 2020 •
edited
Loading

This is blocked on having an info object in the callbacks for SessionHandler.onMessage and SessionExistsHandler.

Deprecated enums should also be removed before 1.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@RichardWarburton RichardWarburton

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@RichardWarburton @mjpt777