On Wed, May 28, 2014 at 10:37 AM, Christian Grobmeier
<grobme...@gmail.com> wrote:
> FYI: Ripple reported in May:
> http://wiki.apache.org/incubator/May2014
>
> We are also not included in the report-next-month section:
> http://incubator.apache.org/report-next-month.html#ripple
>
> This says next report is July:
> http://incubator.apache.org/report-groups.txt
>
> Any ideas what went wrong or what I could check?
To follow up when podlings miss reports, we've been adding "monthly"
attributes in podlings.xml and keeping them there until the podling comes
through.
This routine has been very successful at preventing podlings from falling
through the cracks. However, it trades away the possibility of hiding failure
for the possibility of a false notification if the "monthly" attribute doesn't
get removed in time.
Removal of "monthly" attributes is supposed to be done by the Report Manager.
Here's output from report_runbook.py:
##################################################################
# Prepare next month's wiki report template.
##################################################################
# Edit podlings.xml: remove the "monthly" attribute for podlings
# where it has expired. Commit any changes.
[... edit podlings.xml with your editor of choice ...]
svn ci -m "Remove expired 'monthly' attributes."
But it's easy to forget.
An automated solution would have to do stuff like scrape the report, edit
podlings.xml and svn commit. That seems like overkill and I think we should
just try to stay vigilant going forward. If it keeps happening, we can
revisit our approach.
Marvin Humphrey
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
