So far I simply got to the Infra HipChat room and asked there.
Very successful most of the time, but not documented apart some messages I sent to this ML and bookmarks I kept on them for myself, like "[FYI] Let's
encrypt certificate renewal failed"
Note that with infra things are moving fast and the documentation, rarely used, can be deprecated in few years or even months. I did not say we should
not have ;)
Also, for simple things like lagging apps., you can't do much but asking on Infra HipChat room (not ML , they don't like) or even ask for service when
you must: https://issues.apache.org/jira/servicedesk/customer/portal/1/create/3
Jacques
Le 07/01/2018 à 16:56, Michael Brohl a écrit :
BTW, do we have documentation somewhere which explains who is responsible for these services, how they work, where to lokk what's wrong and who to
inform if there are issues?
To me this is not clear for some of the services (like publishing the website, fisheye, GitHub sync, ...) , but I admit that I did not try very hard
to find information about it.
Thanks,
Michael
Am 07.01.18 um 16:29 schrieb Pierre Smits:
It seems that is not the only service lagging in providing correct results.
The same applies to fisheye. See
https://fisheye.apache.org/browse/ofbiz/ofbiz-framework/trunk
Best regards,
Pierre Smits
V.P. Apache Trafodion
On Sun, Jan 7, 2018 at 3:47 PM, Taher Alkhateeb <slidingfilame...@gmail.com>
wrote:
Hey folks, it seems we still have this delay in our git account. Any
idea how to resolve this and why does it keep happening?
