At the risk of sounding philosophical, when you're building a cloud service that gets continuous delivery of features... when is that simply an iteration, versu

At the risk of sounding philosophical, when you're building a cloud service that gets continuous delivery of features... when is that simply an iteration, versus something new? Anyway, I'm not a philosopher. But I don't think that this is simply a "rebranding exercise", and it's been in the works for quite a while; it's not related to GitHub (which, for the record, we have not yet acquired). We've made a huge engineering effort into the individual components that make up Azure DevOps, and those deserve (in my opinion) to be recognized. So, now "Azure Pipelines" gets to shine on its own.