Changes between Version 2 and Version 3 of developers-meeting-20181023


Ignore:
Timestamp:
10/23/18 16:41:42 (2 years ago)
Author:
jstarek
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • developers-meeting-20181023

    v2 v3  
    55= Participants = 
    66 
     7Al, Marina, Sibel, Olufemi, Vincent, Dmitry, Jürgen 
     8 
    79= Postcards = 
    810 
    9 About one minute (uninterrupted) per person where they can answer two questions: 
    10  *  What I did last week (since the last meeting), 
    11  *  What I plan to do in the next week. 
     11Al: several patches, further work (also conceptual) on introduction of observer role, cleaned up book section on billing,alarms, resilience and some others 
    1212 
    13 No questions until we get through everyone :) 
     13Marina: Documentation, Kafka configurations 
     14 
     15Sibel: New webpage coming up, workshop preparation 
     16 
     17Olufemi: Bugfixes, more flexible configuration for dCache-View. Moving QoS into a separate thread to improve performance. 
     18 
     19Vincent: Just got back from vacation. Started use of Elasticsearch in production. Support of migration to new admin interface by their local ops team. 
     20 
     21Dmitry: 4.2 update 
     22 
     23Jürgen: Releasing (See issue list below), XDC, documentation, 20% time for support of local ops team with port exhaustion issue 
     24 
     25 
    1426 
    1527= Special topics = 
    1628 
    17 Please list special topics you would like to bring up here *before* the meeting, and, if posssible, add a time estimate. We should try to limit this segment to 45 minutes, and that only in exceptional cases. 
    18  
    19 === Al: proposal to use a property (above, see Friday, October 19) concerning public visibility of transfers === 
    20  
     29none 
    2130 
    2231= Release news =  
    2332 
    24 Github issues prevent us from releasing on time. Everything's back to normal now, but Jürgen needs time to work on the backlog.  
     33Paul reports that the latest update at DESY revealed two urgent issues with our latest BouncyCastle patch and with the activation of Kafka. Getting out of the downtime in our instance has highest priority at the moment, followed by patching those issues. 
     34 
     35Jürgens report from the infrastructure side of things: 
     36 
     37Github issues prevent us from releasing on time. Everything's back to normal now, but Jürgen needs time to work on the backlog. Everyone can start submitting material as usual again. 
    2538 
    2639Stability issues on Jenkins hopefully solved by re-shuffling job assignments and giving the most busy machines more RAM. 
     
    3043There is (by far) not enough activity on docs. 
    3144 
     45 
    3246= Trunk activity = 
    3347 
    34 Progress with new features... 
     48Al points out the work on RB requests 11222-11224. 
    3549 
    3650= Issues from [FIXME: Add link to yesterday's Tier-1 meeting] =