On 6/4/2015 10:24 AM, Jim Popovitch wrote:
On Thu, Jun 4, 2015 at 8:08 AM, Kevin A. McGrail <kmcgr...@pccc.com> wrote:
Updates were broken by two issues. 1st, there is a bug in svn with files
with spaces with mod svn. I introduced a file with a space while preparing
the 3.4.1 release.
Forgive me if this sounds incendiary, it's not meant to be. At what
point did someone realize updates were broken? Is the catalyst for
investigation/monitoring inquiries on this list? If not, would it be
possible to send this list an email at the point when it is determined
updates are broken and may take days/weeks to resolve?
-Jim P.
No, this list is not the catalyst for investigating the issue. It's
been researched for quite a bit longer than that (at least a week).
I realized updates where broken from emails (and a lack of emails) on
the dev@ list which combined with the ruleqa@ list is the place where
the updates are monitored. This outage was longer than most due to a
comedy of errors including mailing list moderation problems caused by
ASF infrastructure changes
(https://issues.apache.org/jira/browse/INFRA-9744) and my inability to
read a SunOS 5 df output properly... ;-)
But beyond that, please realize that this is a volunteer driven project
where a lot of people donate a lot of time & resources to make things
happen. And while I do monitor users@ for issues, a lack of updates
does not present a user issue. It is my opinion that if an admin is
concerned about rules updates, they should be monitoring dev@ and/or
ruleqa@.
We also always welcome volunteers and the monitoring script could use
improvement. See https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7121
Regards,
KAM
