From my standapoint there are still some outstanding issues that need to
be taken care of. The big one outstanding now is sorting out peered
cluster support. It's done with only some testing left. Other items:
Client side would really like:
Timouts (long/short) user specifies long one
Append Login tokens
Review Login flags
Make xrdcopy (new xrdcp) use blocking I/O
Envar reporting of appname and appinfo
Client support for bulk dirlist
Client support for combined stat/dirlist feature
Client support for new kXR_prepare and kXR_locate flags (note that
documentation is still outstanding on that)
Client side would be nice to have:
Client support to accept url for redirect (root plugin)
Server side would really like:
Throttle plugin
Peer cluster support
Ability to export log files
Ability to query cmsd status
Refresh flag for kXR_prepare requests
Server side would be nice to have:
XrdPosix with new client (Matevz is testing this)
Misc
Conversion doc for plugin writers
If we tag now as an "rc" then it's unlikely we could add the above as this
is pretty far removed from what's in git head now (i.e. we normally don't
expand an rc feature set). I suppose we could tag it as an "alpha" but we
have never done that before.
Andy
On Wed, 4 Sep 2013, Lukasz Janyst wrote:
> Hi Brian,
>
> from my side, I have around a week of work until we can release 4.0.0-rc1.
> I would prefer not to release any alpha because this would confuse people.
> Andy, do you have much left?
>
> Note, that there is a long weekend at CERN starting tomorrow and I am not
> around until Wednesday.
>
> Cheers,
> Lukasz
>
> On 03.09.2013 23:20, Brian Bockelman wrote:
>> Hi,
>>
>> There are quite a few upcoming Xrootd 4.x features I'd like to start
>> developing/testing against (particularly, XrdCl for proxies and IPv6).
>>
>> Is there any interest in tagging an alpha for xrootd 4.x meant for devs
>> integrating on top of the xrootd core? I can pick a SHA at random, but it
>> seems like it would be more useful if the AAA team coordinated around a
>> particular version.
>>
>> Brian
>> ########################################################################
>> Use REPLY-ALL to reply to list
>>
>> To unsubscribe from the XROOTD-DEV list, click the following link:
>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
>>
>
> ########################################################################
> Use REPLY-ALL to reply to list
>
> To unsubscribe from the XROOTD-DEV list, click the following link:
> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
>
########################################################################
Use REPLY-ALL to reply to list
To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1
|