Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

What's the difference between a snapshot, release candidate and releases? [closed]

Can some one tell me a strategy to manage my repositories based on this concepts (snapshot, release candidate and releases). For example should I have a repository for each type or should I manage release candidates as a snapshot or a release?

like image 218
Carlos Nasser Avatar asked Feb 28 '17 14:02

Carlos Nasser


People also ask

What is difference between SNAPSHOT and release?

In maven a snapshot is defined as an artifact with a version ending in -SNAPSHOT. When deployed, the snapshot is turned into a timestamp. By definition, snapshots are mutable, releases are immutable.

What does release candidate means?

A release candidate (RC), also known as "going silver", is a beta version with potential to be a stable product, which is ready to release unless significant bugs emerge.

What is SNAPSHOT and release in Maven?

A Maven snapshot is a special version of a Maven package that refers to the latest production branch code. It is a development version that precedes the final release version. You can identify a snapshot version of a Maven package by the suffix SNAPSHOT that is appended to the package version.

What is the difference between SNAPSHOT and version?

The difference between a "real" version and a snapshot version is that snapshots might get updates. That means that downloading 1.0-SNAPSHOT today might give a different file than downloading it yesterday or tomorrow.


1 Answers

Snapshots They capture a work in progress and are used during development. A Snapshot artifact has both a version number such as “1.3.0” or “1.3” and a timestamp. For example, a snapshot artifact for commons-lang 1.3.0 might have the name commons-lang-1.3.0-20090314.182342-1.jar.

Release candidate. A release candidate (RC), also known as "going silver", is a beta version with potential to be a final product, which is ready to release unless significant bugs emerge. ... Beta testers, if privately selected, will often be credited for using the release candidate as though it were a finished product.

Release: These are specific, point-in-time releases. Released artifacts are considered to be solid, stable, and perpetual in order to guarantee that builds which depend upon them are repeatable over time. Released JAR artifacts are associated with PGP signatures and checksums verify both the authenticity and integrity of the binary software artifact.

like image 142
Devender Goyal Avatar answered Oct 09 '22 14:10

Devender Goyal