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

proper version naming communication #591

Closed
d4e666 opened this Issue Apr 12, 2017 · 2 comments

Comments

Projects
None yet
3 participants
@d4e666

d4e666 commented Apr 12, 2017

how difficult can it be to use some proper versioning when placing it in communication.

you claim the latest version is 1.1 of the SDK but the real version is 1.0.1. WHY CAN'T UP KEEP THE VERSIONS IN SYNC??? IS IT THAT HARD TO ACT AS GROWN-UP DEVELOPERS AT MICROSOFT????

it's that kind of childish lazyness that makes .NET so fucking difficult. you need to use version X with component Y to be able to address the features of service version Z, which can then be extended by version A, .....

even angular consists of multiple independent libraries and still the manage to keep the same version numbers upon release. This is just a matter of using a global version file. EVEN I USE IT TO KEEP 2 LIBRARIES VERSION SYNCED so how hard can this be? you only need to do it once.

@joelharkes

This comment has been minimized.

Show comment
Hide comment
@joelharkes

joelharkes Apr 14, 2017

@d4e666 Or whatever your name might be.

The problem is not the version sync but its the bad naming of things that make it confusing.

the whole idea of versions is that you can depend on SemVer for you. An update is an update:

  • Major update potentially breaks things
  • Minor update adds features
  • Bugfix updates fixes bugs. (Although this could be a major update sometimes)

Thats why there is different versions for different packages and im happy we do. (otherwise everything had to be release at once, good luck with that)

joelharkes commented Apr 14, 2017

@d4e666 Or whatever your name might be.

The problem is not the version sync but its the bad naming of things that make it confusing.

the whole idea of versions is that you can depend on SemVer for you. An update is an update:

  • Major update potentially breaks things
  • Minor update adds features
  • Bugfix updates fixes bugs. (Although this could be a major update sometimes)

Thats why there is different versions for different packages and im happy we do. (otherwise everything had to be release at once, good luck with that)

@leecow

This comment has been minimized.

Show comment
Hide comment
@leecow

leecow Jun 5, 2017

Member

We're striving to ease the version story with .NET Core 2 so hopefully it will be a bit cleaner across the Core, SDK, ASP stack but divergences at some point would not be surprising. Have a look at these documents addressing some of this.

Member

leecow commented Jun 5, 2017

We're striving to ease the version story with .NET Core 2 so hopefully it will be a bit cleaner across the Core, SDK, ASP stack but divergences at some point would not be surprising. Have a look at these documents addressing some of this.

@leecow leecow closed this Jun 5, 2017

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