Code Versioning - Release

Card Puncher Data Processing

About

A release is packaging your application under a version in a format that is suitable for the distribution channel.

If you publish your application to:

  • a package manager, you should create your application in the required directory structure
  • a website for easy download and install, you would wrapped it into an installer

Generally, every build produces at minimal your code in the form of an archive and you may add extra resources.

For instance:

  • for a library, you would need to create a descriptor file that describe the version, the description,…
  • for an application, you would add the documentation

A release implies several steps such as:

Lifecycle

wiki/Software_release_life_cycle

Stable

Stable release are periodic release of code that will not change continuously.

Development

While stable releases might be get a version with dotted numbers, development versions of a project often need to be tracked by:

  • revision
  • build number
  • or even build date.

Management

Audit

  • See Rat (Release Audit Tool) - audits license headers — the boilerplate text needed in most source files.
  • Whisker helps maintaining and verifying the LICENSE and NOTICE documents shipped (ie producing accurate licensing documentation)

Note

The log of the version control system can be used to generate release notes.

Tools:

Tools

Documentation / Reference





Discover More
Card Puncher Data Processing
Code Shipping - Acceptance Environment

An acceptance environment is a copy of the production and has several purposes, I think. Testing the release in a “near production environment”. Promoting a release on an already patched environment...
Card Puncher Data Processing
Code Shipping - Archive (Distribution)

In the context of code shipping, an archive: contains module (package) in the following form: compiled code or source or/and other resource files is versioned that are used to distribute...
Card Puncher Data Processing
Code Shipping - Binary Distribution

A binary distribution is the binary representation of the code in a archive format of a release. Compiled Code is generally packaged in archive that you can get via a package manager. The distribution...
Card Puncher Data Processing
Code Shipping - Build

Build tool are tools that takes your sources: compile it into a target format such as a compiled file for a language that is not interpreted an HTML or Word document for a markdown document ...
Card Puncher Data Processing
Code Shipping - Deployment

After the creation of release, the next step in a deployment pipeline is to deploy the code (ie archive). Generally, It implies: to run a deployment software with the release as parameter. the output...
Card Puncher Data Processing
Code Shipping - Source (Distribution|Archive)

A source distribution or source archive is a static snapshot representing a particular release of some source code in an archive format, like mypackage-X.X.X.zip.
Card Puncher Data Processing
Code Versioning

Versioning permits to tell which code is newer than another. Every versioning schema will then tell which version is newer than the other one. Code is: versioned by making commit to a repository....
Card Puncher Data Processing
Code design - (Connection|Session)

During the use of a product, a session or connection is a execution context that holds identification data (if any) and group actions (such as interaction or transaction) that take place within...
Docker Tag Syntax
Docker - Tag (Tag, push, and pull your image)

A tag is a string that identifies an image variant with a release version (1.0, 1.1) and/or other component (ie jdk11, jdk15, ...) In the case of the ubuntu image, there is multiple variants covering...
Git - Tag

This page is tagging in git Git has the ability to tag specific points in history as being important. Typically this functionality is used to mark release points (v1.0, and so on). Git uses two main...



Share this page:
Follow us:
Task Runner