On Oct 10, 2011, at 8:54 AM, Lukasz Janyst wrote:
> Hi Brian,
>
> what is the difference in the release numbers?
>
We had one more in the pre-release series based on a git revision. We have the difference for continuity for testers.
Actually, I think you guys are using the version/release wrong. The release is supposed to be reserved solely for the use of the packager, not the project.
Each time you get a distinct set of code from the xrootd project, you want to bump the version number. Each time the packager makes a change to the packaging for the same code base, you bump the release number. This split allows xrootd.org to control one number and re-packagers to control another.
Probably something worth cleaning up for 3.2. It's definitely maintainable right now, just a touch confusing.
> BTW. A new critical bug was found and fixed. RC3 will come soon.
>
No problem.
> Lukasz
>
> 2011/10/10 Brian Bockelman <[log in to unmask]>:
>> For those of you testing the OSG stack, the rebuild is here:
>> https://koji-hub.batlab.org/koji/buildinfo?buildID=652
>> I'm happy to state that, modulo release numbers, the OSG RPM is identical to
>> the upstream one Lukasz mentions below.
>> Brian
>> On Oct 10, 2011, at 7:47 AM, Lukasz Janyst wrote:
>>
>> Dear All,
>>
>> the XRootD 3.1.0 release candidate 2 has been tagged. You can
>> download the source here:
>>
>> http://xrootd.cern.ch/cgi-bin/cgit.cgi/xrootd/snapshot/xrootd-3.1.0-rc2.tar.bz2
>>
>> and the RPMs here:
>>
>> http://xrootd.cern.ch/sw/releases/3.1.0-rc2/rpms/
>>
>> the XRootD-testing yum repository has been updated as well:
>>
>> http://xrootd.org/binaries/xrootd-testing-slc5.repo
>> http://xrootd.org/binaries/xrootd-testing-slc6.repo
>>
>> Please have a look if you wish to help with testing and debugging.
>>
>> Best regards,
>> Lukasz
>>
>>
|