Industry notes

For software teams: the history behind each release

Ticket, review and release history captures how software actually gets built and fixed. You may leave out customer data and any client owned code.

Check my estimate

A common starting point

A team can look first at its issue tracker and review history, because those show how decisions are made and defended. Repos can come later, one product at a time, or never go in at all. Material linked to a client agreement is looked at separately before it can be in scope.

However the scope starts, the copy is made the same way. License Your Data works with approved material only, swaps in placeholders for names and identifiers, and needs your approval of a sample before anything leaves. Your originals stay in your systems all along.

Records that tend to come up

Your repos and the commits inside them
Pull requests with their review discussions
Tickets and bug reports
Build and test history
Design documents and notes for each release

What happens to client code and customer data

If you build for clients, some of your code may belong to them. Ownership gets mapped out at scoping, and your agreements and counsel decide whether client code is ever included.

It is common for logs, chats and tickets to refer to customers by name. The copy swaps people and companies for placeholders and strips account details. You can also exclude any repository, tool or period.

Common questions

Is a tickets only start possible?

Yes. You decide which systems go in, and you approve a sample before anything goes out.

What does it cost?

Nothing at all, and everything begins under NDA.

Will you need access to any system?

No. Nobody asks for credentials of any kind.

All industry notes

Building software does not change the number.

Start with three questions and see your indicative range.