Skip to main content
added 6 characters in body
Source Link
lucasgcb
  • 375
  • 4
  • 12

I've been working on an open source project recently and have been checking out Core Infrastructure's best practices checklist.

One of the items pertaining the "Change Control" checklist is as follows:

To enable collaborative review, the project's source repository MUST include interim versions for review between releases; it MUST NOT include only final releases.

This confused me as to what "interim versions" are, objectively. Looking up "interim version" in different contexts never yielded me anything besides a broad term of "intervention", which makes sense but foundreturned no real examples of.

Does the classic git workflow where we have automated checks, PRs, code reviews and a development branch count as a form of interim? Or are they something else, that need to be tagged in version control as their own version?

I've been working on an open source project recently and have been checking out Core Infrastructure's best practices checklist.

One of the items pertaining the "Change Control" checklist is as follows:

To enable collaborative review, the project's source repository MUST include interim versions for review between releases; it MUST NOT include only final releases.

This confused me as to what "interim versions" are, objectively. Looking up "interim version" in different contexts never yielded me anything besides a broad term of "intervention", which makes sense but found real examples of.

Does the classic git workflow where we have automated checks, PRs, code reviews and a development branch count as a form of interim? Or are they something else, that need to be tagged in version control as their own version?

I've been working on an open source project recently and have been checking out Core Infrastructure's best practices checklist.

One of the items pertaining the "Change Control" checklist is as follows:

To enable collaborative review, the project's source repository MUST include interim versions for review between releases; it MUST NOT include only final releases.

This confused me as to what "interim versions" are, objectively. Looking up "interim version" in different contexts never yielded me anything besides a broad term of "intervention", which makes sense but returned no real examples of.

Does the classic git workflow where we have automated checks, PRs, code reviews and a development branch count as a form of interim? Or are they something else, that need to be tagged in version control as their own version?

Source Link
lucasgcb
  • 375
  • 4
  • 12

What is an interim version in Source Control?

I've been working on an open source project recently and have been checking out Core Infrastructure's best practices checklist.

One of the items pertaining the "Change Control" checklist is as follows:

To enable collaborative review, the project's source repository MUST include interim versions for review between releases; it MUST NOT include only final releases.

This confused me as to what "interim versions" are, objectively. Looking up "interim version" in different contexts never yielded me anything besides a broad term of "intervention", which makes sense but found real examples of.

Does the classic git workflow where we have automated checks, PRs, code reviews and a development branch count as a form of interim? Or are they something else, that need to be tagged in version control as their own version?