I'm obviously biased, but we're not an afterthought. I think the best way to explain things is that Bitbucket was a startup that Atlassian acquired; we had to independently solve many cloud-specific problems while the rest of the company was largely still focused on building server products; and as the company started investing in a platform, they prioritized onboarding Jira and Confluence first which are built on a completely different tech stack than Bitbucket Cloud.
The reality is that this migration is one of the clearest signals I can point to that the company is investing in Bitbucket. Our platform teams have been awesome and given us a ton of support, including features that didn't exist before (without going into too much detail... you can probably imagine that Jira and Confluence don't have nearly the same requirements around file system access that we do).
Yes, Bitbucket Cloud and Bitbucket DC are two different teams and code bases; but we work closely together and are talking a lot about both products' roadmaps and future vision. And we even have engineering teams working together on a shared project and may do more of that in the future.
Thanks for the reply. As unsolicited feedback, Atlassian should rip off the bandaid and pick one of the code bases and have that be the go-forward platform for both cloud and on-prem. Bitbucket's two biggest competitors have largely the same code base for cloud and on-prem. The market expects feature parity between cloud and on-prem products and to not have to re-write to a different API when moving from on-prem to cloud or vice versa.
Comments
I'm obviously biased, but we're not an afterthought. I think the best way to explain things is that Bitbucket was a startup that Atlassian acquired; we had to independently solve many cloud-specific problems while the rest of the company was largely still focused on building server products; and as the company started investing in a platform, they prioritized onboarding Jira and Confluence first which are built on a completely different tech stack than Bitbucket Cloud.
The reality is that this migration is one of the clearest signals I can point to that the company is investing in Bitbucket. Our platform teams have been awesome and given us a ton of support, including features that didn't exist before (without going into too much detail... you can probably imagine that Jira and Confluence don't have nearly the same requirements around file system access that we do).
Yes, Bitbucket Cloud and Bitbucket DC are two different teams and code bases; but we work closely together and are talking a lot about both products' roadmaps and future vision. And we even have engineering teams working together on a shared project and may do more of that in the future.
Thanks for the reply. As unsolicited feedback, Atlassian should rip off the bandaid and pick one of the code bases and have that be the go-forward platform for both cloud and on-prem. Bitbucket's two biggest competitors have largely the same code base for cloud and on-prem. The market expects feature parity between cloud and on-prem products and to not have to re-write to a different API when moving from on-prem to cloud or vice versa.