perfsonar-dev - Re: perfSONAR MDM 3.1 update status
Subject: perfsonar development work
List archive
- From: Antoine Delvaux <>
- To: Chris Welti <>
- Cc: Szymon Trocha <>, ,
- Subject: Re: perfSONAR MDM 3.1 update status
- Date: Tue, 24 Feb 2009 17:35:56 +0000
- Organization: eShango
>> I don't know if we can do something at packages level. I'd like to have
>> developers opinion here?
>>
> I'm sure there is a mechanism at packages level to properly indicate beta
> versions.
Yes, there is.
The RPM way is to use the 'Release' field of the SPEC file and have something
begining with '0.' in it. When the final package is done, this is bumped to
'1', and so any RC package will be upgraded.
In the SPEC file you'll have (for the first RC):
Version: 2.1
Release: 0.rc1.1
Second RC:
Version: 2.1
Release: 0.rc2.1
and for the final:
Version: 2.1
Release: 1.0
The Deb way, lacking a 'release' field, is to decrease the version number for
RC
and adding '+1' at the end.
In the debian/changelog file, you'll have (for the first RC):
package-name (2.0.99+1.rc1-1)
Second RC:
package-name (2.0.99+1.rc2-1)
and for the final:
package-name (2.1-1)
Cheers,
Antoine.
- Re: perfSONAR MDM 3.1 update status, Antoine Delvaux, 02/24/2009
- Re: [pS-dev] Re: perfSONAR MDM 3.1 update status, Szymon Trocha, 02/25/2009
Archive powered by MHonArc 2.6.16.