I've asked the Analytics team to take a look.

I'm pretty sure this is set for release tomorrow =)

This is good info, thanks =)I'd reiterate that somebody should post this as an idea and collect votes.

If this is something that you want, I'd suggest logging an idea for the enhancement, and then lobbying the community members to vote for it.  To be completely transparent, we probably wouldn't take it on without a bunch of community support for a couple reasons:  Currently all builds have the same s...

Backwards compatibility.  The structure of the package has changed over time.  In the environments that we host for you, these are symlinks to a single file, but in the archived builds, we put identical copies of the file in because symlinks are not supported on all systems where you might unpack th...

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...

I read the other thread, and I think they are different things.  I've responded on the other thread to get some clarifying details, but I think that Launch may already provide a way for you to do that.

The revisions themselves are set in stone at the time they are saved to a library and they are never edited again.  This is a system constraint so that you can always have a historical record of the thing that was published at any given time.When you say that you want to make it editable, can I desc...