search for: monthstamp

...se at least) says: > > "Numbering > > CentOS 7.0-1406 introduces a new numbering scheme that we want to > further develop into the life of CentOS-7. The 0 component maps to the > upstream realease, whose code this release is built from. The 1406 > component indicates the monthstamp of the code included in the release > ( in this case, June 2014 ). By using a monthstamp we are able to > respin and reissue updated media for things like container and cloud > images, that are regularly refreshed, while still retaining a > connection to the base distro version." &...

...the convention (for the 7.0 release at least) says: "Numbering CentOS 7.0-1406 introduces a new numbering scheme that we want to further develop into the life of CentOS-7. The 0 component maps to the upstream realease, whose code this release is built from. The 1406 component indicates the monthstamp of the code included in the release ( in this case, June 2014 ). By using a monthstamp we are able to respin and reissue updated media for things like container and cloud images, that are regularly refreshed, while still retaining a connection to the base distro version." I would have assumed...

...; >> "Numbering >> >> CentOS 7.0-1406 introduces a new numbering scheme that we want to >> further develop into the life of CentOS-7. The 0 component maps to the >> upstream realease, whose code this release is built from. The 1406 >> component indicates the monthstamp of the code included in the release >> ( in this case, June 2014 ). By using a monthstamp we are able to >> respin and reissue updated media for things like container and cloud >> images, that are regularly refreshed, while still retaining a >> connection to the base distro...

....html That numbering concept (for 7.0 at least) makes sense: "CentOS 7.0-1406 introduces a new numbering scheme that we want to further develop into the life of CentOS-7. The 0 component maps to the upstream realease, whose code this release is built from. The 1406 component indicates the monthstamp of the code included in the release ( in this case, June 2014 ). By using a monthstamp we are able to respin and reissue updated media for things like container and cloud images, that are regularly refreshed, while still retaining a connection to the base distro version." Those who care a...

Am 03.12.2015 um 11:39 schrieb Greg Lindahl <lindahl at pbm.com>: > On Thu, Dec 03, 2015 at 11:28:10AM +0100, Leon Fauster wrote: >> Am 03.12.2015 um 11:08 schrieb Greg Lindahl <lindahl at pbm.com>: >>> I wanted to help you by making sure that you were on the most recent >>> version, but, looking at the Centos.org website I was unable to figure >>>

...OS-5 and CentOS-6 builds into the same system. - ---------- Numbering CentOS 7.0-1406 introduces a new numbering scheme that we want to further develop into the life of CentOS-7. The 0 component maps to the upstream realease, whose code this release is built from. The 1406 component indicates the monthstamp of the code included in the release ( in this case, June 2014 ). By using a monthstamp we are able to respin and reissue updated media for things like container and cloud images, that are regularly refreshed, while still retaining a connection to the base distro version. In order to facilitate Spe...

...OS-5 and CentOS-6 builds into the same system. - ---------- Numbering CentOS 7.0-1406 introduces a new numbering scheme that we want to further develop into the life of CentOS-7. The 0 component maps to the upstream realease, whose code this release is built from. The 1406 component indicates the monthstamp of the code included in the release ( in this case, June 2014 ). By using a monthstamp we are able to respin and reissue updated media for things like container and cloud images, that are regularly refreshed, while still retaining a connection to the base distro version. In order to facilitate Spe...

As a CentOs newbie, I'm not sure, will we still have CentOS 7.1 which derive from RHEL 7.1? or this is the new naming conversion for CentOS 7. Thanks! -Ryan > On Apr 1, 2015, at 12:30 AM, Karanbir Singh <kbsingh at centos.org> wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > We would like to announce the general availability of CentOS Linux 7

...OS-5 and CentOS-6 builds into the same system. - ---------- Numbering CentOS 7.0-1406 introduces a new numbering scheme that we want to further develop into the life of CentOS-7. The 0 component maps to the upstream realease, whose code this release is built from. The 1406 component indicates the monthstamp of the code included in the release ( in this case, June 2014 ). By using a monthstamp we are able to respin and reissue updated media for things like container and cloud images, that are regularly refreshed, while still retaining a connection to the base distro version. In order to facilitate Spe...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We would like to announce the general availability of CentOS Linux 7 (1503) for 64 bit x86 compatible machines. This is the second major release for CentOS-7 and is tagged as 1503. This build is derived from Red Hat Enterprise Linux 7.1 As always, read through the Release Notes at : http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7 - these notes

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We would like to announce the general availability of CentOS Linux 7 (1503) for 64 bit x86 compatible machines. This is the second major release for CentOS-7 and is tagged as 1503. This build is derived from Red Hat Enterprise Linux 7.1 As always, read through the Release Notes at : http://wiki.centos.org/Manuals/ReleaseNotes/CentOS7 - these notes