Print

Print
Hi guys,

It is exactly as Andy is saying, at some point we have to say we tag the release, it is unfortunate that
around the same time an important bugfix has been provided, but fear not, we will definitely have
a more dynamic schedule for 5.1.x bug fix releases.

The 5.1.0 was already quite delayed and we really had to cut it (probably in the future we should be
also more agile with feature releases).

The bottom line i,s if we would have cut another RC with the patch we would wait anyway for a week to tag the release.
In current situation we can have 5.1.1 within 1-2 weeks, so the community will have the patch approximately at the same
time.

Cheers,
Michal

On 24 Feb 2021, at 12:16, Andrew Hanushevsky <[log in to unmask]> wrote:

Hi Petr,

Let me try to instill a bit more appreciation to a release schedule here.

We recieve a huge number of patches in any given moment. For a release we have to decide which ones go in and which will not even when some patches claim they fix huge problems. We need to verify the claim before they can go in. Given that releases cannot be "just in time" given the verification requirements we need to close off new patches once the process starts. Patches submitted after we start a release cycle verification are not eligible. Developers are well aware of this and are not suprised when we don't include a patch in a particular release.

From an external observer's viewpoint it's audacious that we didn't include a particular patch. But, frankly, if we tried to include every patch submitted "just in time" we would not be able to release anything. I hope you appreciate the competing factors here.

All this means is that the patches you are looking for will be included in 5.1.1 which usually lags about 1-2 weeks. Of course, that also means we have to verify that those patches are relevant. So, it may take longer if we find problems with them. That should provide comfort as we are trying to fix real problems and exclude problematic solutions. In the case at hand, the solution was real but it arrived just too late.

Andy


On Wed, 24 Feb 2021, Petr Vokac wrote:

Without fix for HTTP-TPC?

https://github.com/xrootd/xrootd/pull/1409

When we can expect new release with this fix to be able to start moving
also XRootD storages away from GsiFTP?

Petr

On 2/24/21 11:01 AM, Michal Simon wrote:
Dear All,

    The XRootD 5.1.0 feature release has been tagged yesterday. Please
follow the link below for more details:
    http://xrootd.org/2021/02/23/announcement_5_1_0.html
<http://xrootd.org/2021/02/23/announcement_5_1_0.html>

Kind regards,
    Michal

------------------------------------------------------------------------

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1
<https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1>



########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1


Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-L&A=1