A series of blogs are released that discuss branch versioning in ArcGIS Pro / ArcGIS Enterprise. This discussion is for questions that are directly related to content/concepts included in these blogs.
Branch versioning blogs:
Hi. I would really like a blog about using branch version with the apps for the field. It is not clear to me if a feature service publishes from a branch version would be supported by existing field apps like Collector or Survey123 or web applications like Web App Builder.Melissa Jarman
Thanks for the suggestion Hector - perhaps in the future there will be blogs about workflows with using branch versioning with some of our apps.
While not in a blog format, there was a thread that discussed this on geonet:
It would be nice to have the blog though. Details about how multiple editors or sync operations would lock the default version or if it would scale better than traditional versioning. Just an official response from Esri if branch versioning is adequate for field collection and web editing workflows or if there is still some development to be done before we can start migrating some of our traditional versioning workflows.
Ditto what Hector said. It would be great to see examples of each of the edits listed at the first link, "Data published and versioned through the ArcGIS Enterprise portal allows for edits to be contributed from smartphones, web applications, third-party apps, and even automated scripts using the REST API."- An Introduction to Branch Versioning
I would also like to see a blog on how to manage branch versioning in a distributed editing environment. How do you control which users can edit a branch service? Do you need to create a separate non editing service for other users to view the data? Can different people create services, then be able to post only versions created from their service? Can a service ownership be transferred and that new user be able to control the version management?
Does Esri have plans to support Topology and Network Datasets with Branch Versioning? If so, when? My organisation would like to migrate our data editing systems to Branch Versioning but we can't do so until this functionality is made available.
Our teams worked hard to add support for branch versioned topology this release. This work was done by the geodatabase and feature service teams to support a new topology layer for web feature layers and enabling many of the validation workflows through the gp tool and error inspector via services.
We currently don't have near term plans for implementing branch versioning for network datasets.
Here is a new blog with some highlights of new geodatabase functionality for 2.6/10.8.1 -