We just were notified this morning that our ability to continue licensing BitBucket Server ends this month. This is highly problematic.
We think this is, bluntly, a bad decision by Atlassian, leaving us with no choice but to move to another Enterprise Git provider unless the decision is reversed.
Sincerely,
Randall
Thanks. Your notice on the website about discontinuing did not mention BitBucket Data Centre. We are glad that this is the case. Please try to be clear with your communication to avoid panicking major users who are not in the infrastructure departments.
It's not me! I'm not an Atlassian!
I think they messed up the announcement a bit personally. I had one client ring us in a panic first thing in the morning because he didn't see anything about "or move to DC" anywhere in the announcements he'd read, followed by a fortnight of similar, but not quite so panic'y calls with more.
Here is some additional information about migration to Data Center: https://www.atlassian.com/migration/data-center/self-guided/plan-your-migration#build-your-team
It is disappointing to hear bitbucket is going to discontinue
Bitbucket Server only. Bitbucket Cloud and Bitbucket Data Centre are staying with us.
It is Bitbucket Server not Bitbucket Data Centre or Cloud that we are using extensively. I still have not seen the official announcement. Moving to the Cloud is not an option for all but a small few of our projects.
In my opinion BitBucket Data Centre is one of the easier products to migrate to given they offer lower user tiers compared to Jira and Confluence.
If you were a licence holder, technical contact, or subscribed, you were notified about https://www.atlassian.com/blog/announcements/journey-to-cloud last October.
There's more information, based on incoming questions, at https://www.atlassian.com/migration/faqs
The short story is that you've got a couple of years to move to Cloud, DC or off Atlassian (unless you're happy to continue with unsupported software - for what it's worth, I picked up a client today who is still on Jira 3.3, working fine, but unsupported for well over a decade if memory serves)