Azure-sdk-for-go: Stop releasing as "-beta"

Created on 31 Oct 2016 · 7Comments · Source: Azure/azure-sdk-for-go

Is there a plan to stop using suffix -beta in release names/tags? I know we still make a ton of breaking changes but that does not make it a -beta really.

Many products and customers are using Go SDK in production for quite a while, as well as some of the new internal services that are ramping up nowadays. We feel confident using it just fine. And it's in top 3 in terms of requests sent to the ARM FrontDoor. I'm thinking maybe it's not a -beta anymore?

question

Source

ahmetb

🎉3

Most helpful comment

@eduardkoller out of interest - are the criteria that you refer to publicly available?

tombuildsstuff on 7 Nov 2016

👍2

All 7 comments

:D
Our plan is to release a non beta version in spring

mcardosos on 4 Nov 2016

Spring 2017? That means that the SDK will have been in beta for well over a year - why is this the case?

stack72 on 7 Nov 2016

We have a set of internal criteria for lifting the beta tag. Once the criteria are met, we will release without the 'beta'.

eduardkoller on 7 Nov 2016

@eduardkoller out of interest - are the criteria that you refer to publicly available?

tombuildsstuff on 7 Nov 2016

👍2

+1 for being open about the exit criteria for moving from beta to stable.

colemickens on 9 Nov 2016

👍1

@eduardkoller is there any update on this?

tombuildsstuff on 23 Nov 2016

I've just opened up issue #517 which I hope, at least when resolved, answers this question.

For now, I'm going to close this issue, because I hope that the conversation I just mentioned addresses the community's concern about both release status and transparency. Feel free to re-open or start a new thread if you do not feel this has been properly addressed.