If you have specific enhancements you'd like to see to the feature, suggestions are always welcome. You can to submit them in the ideas exchange and lobby your fellow users to vote for them or hit us up in one of many Slack channels.Launch enables publish libraries in a bunch of different ways. Thi...
We released this capability in the API on 10/15 (see API release notes and API docs). UI work is in the final stages now. We have limited release windows during the holiday season, but we hope to release it next week. If we miss that window, the next release window is in early December.
We've just discussed this in the last couple weeks. We are planning to add a created_at field as well as a last_updated_by field to most (all?) API resources. Certainly all the revisable resources would be included, we're evaluating if there's value in having it on all fields.
Notes are available now within the Launch API. UI implementation is in progress. If you're interested in using Notes in the API, you can check out https://developer.adobelaunch.com/api/reference/1.0/notes/.
Thanks for taking the time to write it all out. I think I understand, and if I do, it sounds like what you're really wanting is to treat a Library (or a Working Library) more like a true branch (or more like the way that workspaces behave in GTM) where different libraries/workspaces maintain their ...
You are right that when two people are making edits at the same time, and adding them to libraries, you could end up in a scenario where the sequential revision history doesn't look like it makes any sense. From what we have seen so far, that doesn't happen a ton in practice (at least we haven't se...
With Launch, we deliberately shied away from branching. You should think of all your resources as existing within a single branch. Each time you save a resource and add it to a library, an individual commit to each individual resource is made. And a library is not a different branch, it's more li...