 |
 |
Thanks Andy, few weeks for 5.1.1 sounds good. I'm too biased toward HTTP-TPC functionality, because with non-XRootD storages we were able to move forward and drop SRM/gsiftp six months ago, but we are waiting for XRootD version that could be recommended for production HTTP-TPC usage. Anyway, because our XRootD storages are mostly in US the most important for us is the version that will be distributed by OSG. Petr On 2/24/21 12:16 PM, Andrew Hanushevsky 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 ######################################################################## 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