search

Particular / NServiceBus.Azure

Transports and storage for Windows Azure
https://docs.particular.net/nservicebus/azure/
Other
10 stars 15 forks source link

Review version policy WindowsAzure.Storage #299

Open yvesgoeleven opened 7 years ago

yvesgoeleven commented 7 years ago

Connects to https://github.com/Particular/NServiceBus.Azure/issues/318

Current: Fixed Major Range

Used in

yvesgoeleven commented 7 years ago

Suggestion, Fixed Major Range [7.0.0, 9.0.0) for all

SeanFeldman commented 7 years ago

For all? Including NServiceBus.Azure.Transports.WindowsAzureStorageQueues and NServiceBus.Persistence.AzureStorage that are currently have lower version as 8.0?

yvesgoeleven commented 7 years ago

yeah I would treat all the same, packages are used together if the rules vary customers will get into conflicts (e.g; newtonsoft support case from last week)

SeanFeldman commented 7 years ago

Sounds good.

Scooletz commented 7 years ago

As we know the API from the past and our usage of it: 👍

danielmarbach commented 7 years ago

Again too dangerous. A support case doesn't justify the risk we are exposing ourselves here. So 👎

yvesgoeleven commented 7 years ago

@danielmarbach what risk? we have been running with version 7 like forever, it's just the start of the range that moves back to a version that we are very familiar with

danielmarbach commented 7 years ago

For a generic thing like

NServiceBus.Hosting.Azure

I see now risk. But this issues states that we want [7.0.0, 9.0.0) for all the above-stated ones.

A transport or a persistence is likely to make usage of a specific feature of a major version of that library for optimization purpose or to expose some hook of whatever kind. As soon as you do things start to break. Which has severe and more consequences then us having to remember to release a minor from time to time.