Sean Feldman

> Azure app services will automatically create and destroy instances of the app service behind the scenes. New instances are created with a random name. Whenever an instance is created,...

> This could be solved by infrastructure, but it would involve a script that runs periodically to detect and remove unused/idle queues. However, detecting queue idleness is not trivial. My...

> Some cases where this might not work would be if the app service had an ungraceful shutdown or if the asynchronous delete queue operation didn't complete in the time...

> It could be problematic if NServiceBus changed any of those settings or the naming convention of the queues. The transport does **not** modify the queue settings if a queue...

The legacy ASB had this behaviour, but arguably, it was the way it was. For the new transport, endpoints should be able to just publish. Wherever there's a topic or...

Fix for this issue will require a breaking change. Therefore we will introduce it in the next **major** release rather than right away as there are viable workarounds. As well...

> but AFAIK message sessions are only providing ordering for a specific sender. That's incorrect. Different senders can contribute messages for a given session. > For example, sessions are useful...

Support this suggestion. It will allow a fine tuning for release notes w/o loosing milestones or proper labels we have to do now. In addition to that, PBot will stop...

Looks like this thread became dormant with no actual action items. The issue I'm facing is when we have a hotfix for example, and there was a bug introduced _and_...

Fair point @danielmarbach. I'm good with a label as well, as long as we don't have to tweak the auto-generated release notes.