We're happy to announce that on September 15th, 2020, we will begin gradually enabling a new traffic acceleration improvement for all Bitbucket Cloud users (Free, Standard, and Premium) when accessing Bitbucket.org for Web- or Git-based (ssh/https) operations. This new improvement leverages AWS Global Accelerator to route traffic to and from Bitbucket Cloud via 83 Points of Presence in 73 cities across 38 countries, potentially dramatically speeding up transaction times.

Today Bitbucket is releasing a new labs feature, "Pending Merges", which allows for automatic merging of pull requests when builds pass. This means no more continually checking back in on your pull request, just waiting and waiting for your builds to pass before you can finally merge it. You will no longer be forced to begrudgingly fix that one-character whitespace typo in your comment that you really should fix, but that means you're in for another 30-60 minutes of watching your builds.

High productivity. Low turnover. Satisfied workers. Less stress. A larger talent pool. Fewer office expenses. ADA compliance. And better work-life balance. When you list the benefits of remote work, there’s a lot to love – for both businesses and the people they employ – which is a huge reason why more and more companies are starting to embrace a remote workforce.

When the entire company is working from home, pair programming is not only possible but even more valuable. If you were practicing it face to face, why not continue remote? If you weren’t, why not try? My team did a series of remote pair programming sessions in during the last month or so, and I want to share a few tips from that experience. If you’ve never tried pair programming before, here’s a good primer.

Cloud is no longer a differentiator – it’s a strategic requirement for long-term success. So says Forrester’s Benchmark Your Enterprise Cloud Adoption report, and so say our customers, 90 percent of whom choose our cloud products over hosting Server or Data Center versions on-premise (on-prem). Ten years ago, moving to the cloud was about staying ahead of the curve – no longer.

This blog is part of our series on how to use Atlassian features, automations, and integrations to take time back to ship better code, faster. Click here for the full list of 12+ new features or follow us on Twitter to stay up-to-date! Picture this: you've landed in a Development team that practices DevOps religiously (or maybe you're even leading one!). But despite spending hours integrating your tools and reading your edition of the Phoenix Project, you still feel like there's something missing.

When the Coronavirus pandemic hit and the world went into lockdown, as many as one-half to one-third of workers in the United States began working from home full-time. Some people have loved it, but others have felt lonely, unproductive, and stressed while working from home with kids. As we’ve learned more about the virus and states have published reopening plans, many knowledge workers in the U.S. are ready (or being asked) to return to work.

Last night I dreamt I was back in the office for the first time. Our long communal tables in the kitchen were gone. My desk was surrounded on all sides by plexiglass – including overhead, which, for a guy my height, means stooped shoulders and a future riddled with chiropractic appointments. Nobody talked to each other except over Slack. The smell of disinfectant was inescapable. I couldn’t wait to go back home. Or at least, wake up.

The uncertainty fatigue is real. Those “how we’re handling COVID” emails from every business we’ve ever patronized have died down and many of us have settled into something resembling a routine, but most of us are still isolated from friends and family. We’re gearing up for a long summer of, yes, more uncertainty, with only the dim hope of an ambiguous return to “normal life” to cling to.

Remember that movie Groundhog Day? Where Bill Murray experiences the same day over and over and over and heartwarming hilarity ensues? Working from home can feel like a lot like that (minus the heartwarming hilarity). The hours meld together because there’s no natural divider to separate work time from personal time.