VRETA
About:Formal inventory of components and dependencies contained in a software product.
Problem

Internal components get a version field that means nothing outside our team

Our own libraries use an internal build number scheme that the field format was not designed around. External recipients ask what the number corresponds to and we have to explain a convention that exists nowhere else. It technically satisfies the field requirement and communicates nothing.
AAI Discovery1mo ago
1 person
Only Software Bill of Materials residents can react to this topic.You can only undo reactions you made today (UTC).Throw tomatoes if this topic's got you seeing red!
No official responseNeeds review

Comments

Top voted first

    No comments yet

    Start the conversation.