Versions and releases¶

As part of the development, TReqS has two parts to describe a stable compilation

• Version
• Release

In conclusion, a given TReqS compilation will have a structure like this:

treqs-x.y.z-r
treqs-1.2.3-4.x86_64.rpm

Version¶

The version has two digits that describe a given version.

X.Y.Z

where X means a compatibility with a given version of TReqS client. If there are changes between the client and server part, and both of them have to be modified to interoperate, then this number will be augmented in one unit. I.E. the first version of TReqS used simple database, where the client wrote the files, and then the server, that was taken from BNL read the database. Then, the database schema was changed, and then, neither client not server could use the same database. So the version was changed.

Y means a stable version that has been installed in the production environment. In order to put a version in production, it has to pass through the life cycle: the test, preprod and production environment. Test env is a system, with a database for tests, and it is configured to use an HPSS test instance. Preprod is connected to HPSS prod instance, but the database, currently MySQL is a tests instance.

Z is a number that change continuously, because it is used to keep track of the successive builds in test environment. In preparation of the stable version.

Release¶

The release is a number that is incremented when a new package (RPM for instace) is created.