Closed Bug 274404 Opened 21 years ago Closed 20 years ago

There are no docs for Whining

Categories

(Bugzilla :: Documentation, defect)

2.19.1
defect
Not set
major

Tracking

()

RESOLVED FIXED
Bugzilla 2.20

People

(Reporter: justdave, Assigned: karl)

Details

(Whiteboard: [wanted for 2.20])

Attachments

(2 files, 2 obsolete files)

There appear to be no docs at all for Whining, either how to configure it (adding the cron job, putting people in the group) or how to use it. This is currently a "documentation?" flag on bug 185090, but I'm separating it out so I can make it a release blocker. This is one of our advertised major new features, we can't release without having docs for it. :)
Flags: blocking2.20+
Target Milestone: --- → Bugzilla 2.20
Whew, 2.20 You had me worried that this was another crunch item for 2.18 :).
"If it's not a regression from 2.18 and it's not a critical problem with something that's already landed, let's push it off." - Dave
Flags: blocking2.20+
Whiteboard: [wanted for 2.20]
Flags: blocking2.20-
I'd count this as a critical problem with something that's already landed. Although the editwhines page is pretty decent at self-documentation. However, I'd say that this is probably the most important doc bug for 2.20, at the moment.
Flags: blocking2.20- → blocking2.20?
Erik, are you going to have time to document whining before 2.20 (final)?
Attached patch Whining docs, draft 1 (obsolete) — Splinter Review
I hope nobody minds; I went ahead and threw together some whining documentation! This includes both a section on how to use whining, and a section (under "optional configuration") on how to set up Cron to run the whining script. I'm requesting review from documentation, for obvious reasons and not-so-obvious reasons (I don't have a working docbook installation, and can't completely check everything).
Attachment #187097 - Flags: review?(documentation)
Comment on attachment 187097 [details] [diff] [review] Whining docs, draft 1 I'm also requesting review from erik. He's listed as the reviewer for editwhines.cgi, so I assume that he would know the most about the new Whining system, and will be able to point out errors and omissions.
Attachment #187097 - Flags: review?(erik)
Comment on attachment 187097 [details] [diff] [review] Whining docs, draft 1 >Index: installation.xml >+ <section id="installation-whining"> >+ <title>Whining</title> >+ >+ <para> >+ As of Bugzilla 2.20, users can configure Bugzilla to regularly annoy >+ them at regular intervals, by having Bugzilla execute saved searches >+ at certain times and emailing the results to the user. This is known >+ as "Whining". The process of configuring Whining is described >+ in <xref linkend="whining">, but for it to work a Perl script must be Missing / on the xref tag. >+ executed at regular intervals. >+ </para> >+ >+ <para> >+ This can be done by adding the following command as a daily >+ crontab entry, in the same manner as explained above for bug >+ graphs. This example runs it every 15 minutes. >+ </para> >+ >+ <programlisting>0-59/15 * * * * cd &lt;your-bugzilla-directory&gt; ; ./whine.pl</programlisting> Nit: */15 would achieve the same effect, I believe. >+ >+ <note> >+ <para> >+ Whines can be executed as often as every 15 minutes, so if you specify >+ longer intervals between executions of whine.pl, some users may not >+ be whined at as often as they would expect. Depending on a person's >+ personality and overall, this can either be a very Good Thing or a >+ very Bad Thing. >+ </para> >+ </note> "personality and overall," seems an abrupt stop. >+ <note> >+ <para> >+ Windows does not have 'cron', but it does have the Task >+ Scheduler, which performs the same duties. There are also >+ third-party tools that can be used to implement cron, such as >+ <ulink url="http://www.nncron.ru/">nncron</ulink>. >+ </para> >+ </note> >+ </section> >+ >Index: using.xml >=================================================================== >RCS file: /cvsroot/mozilla/webtools/bugzilla/docs/xml/using.xml,v >retrieving revision 1.30 >diff -u -r1.30 using.xml >--- using.xml 20 Jun 2005 19:16:28 -0000 1.30 >+++ using.xml 23 Jun 2005 03:41:31 -0000 >@@ -1160,6 +1160,205 @@ > </para> > </section> > >+ <section id="whining"> >+ <title>Whining</title> >+ >+ <para> >+ Whining is a feature in Bugzilla that can regularly annoy users at >+ specified times. Using this feature, users can execute saved searches >+ at specific times (i.e. the 15th of the month at midnight) or at >+ regular intervals (i.e. every 15 minutes on Sundays). The results of the >+ searches are sent to the user, either as a single email or as one email >+ per bug, along with some descriptive text. Missing </para> With those fixed it generates, but I'm not enough of an expert on the whining system to say that the documentation is correct... over to erik for that.
Attachment #187097 - Flags: review?(documentation) → review-
Comment on attachment 187097 [details] [diff] [review] Whining docs, draft 1 Attachment 187097 [details] [diff] is being replaced, so I'm moving the request for review of its contents to draft 2.
Attachment #187097 - Flags: review?(erik)
Attached patch Whining docs, draft 2 (obsolete) — Splinter Review
Modification of attachment 187097 [details] [diff] [review], taking into account comment 7: > Missing / on the xref tag. Missing / added. > Nit: */15 would achieve the same effect, I believe. * looks much better than 0-59. Modified. > "personality and overall," seems an abrupt stop. True. Dropped phrase & modified wording a bit. > Missing </para> Missing tag added Again, requesting review from documentation@bugzilla.bugs. Colin (or whomever reviews this for documentation): Would it be possible to post the rendered HTML for viewing?
Attachment #187097 - Attachment is obsolete: true
Attachment #187119 - Flags: review?(documentation)
Comment on attachment 187119 [details] [diff] [review] Whining docs, draft 2 Moved request for review of accuracy of body from draft 1 to draft 2.
Attachment #187119 - Flags: review?(erik)
Comment on attachment 187119 [details] [diff] [review] Whining docs, draft 2 r+ pending someone that knows whining better than I reading it over...
Attachment #187119 - Flags: review?(documentation) → review+
Attached file HTML Output
Output from HTML
Comment on attachment 187119 [details] [diff] [review] Whining docs, draft 2 It's been 7+ days since the review request. Per instructions from IRC, asking joel.
Attachment #187119 - Flags: review?(erik) → review?(bugreport)
Comment on attachment 187119 [details] [diff] [review] Whining docs, draft 2 Heck yes... whining needs docs.
Attachment #187119 - Flags: review?(bugreport) → review+
joel: From your review+ on draft 2, can I take that to mean that the details are correct, and that nothing important is missing? If so, could you (or someone with appropriate privs.) request approval? Thanks!
Actually, there is always something left out. However, we start by going from no docs to some doc, then we improve further.
Flags: approval?
Flags: blocking2.20?
Flags: blocking2.20+
Flags: approval?
Flags: approval+
Checking in installation.xml; /cvsroot/mozilla/webtools/bugzilla/docs/xml/installation.xml,v <-- installation.xml new revision: 1.96; previous revision: 1.95 done Checking in using.xml; /cvsroot/mozilla/webtools/bugzilla/docs/xml/using.xml,v <-- using.xml new revision: 1.31; previous revision: 1.30 done (Yes, I do still exist :)
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Assignee: documentation → karl
Checking in using.xml; /cvsroot/mozilla/webtools/bugzilla/docs/xml/using.xml,v <-- using.xml new revision: 1.32; previous revision: 1.31 done Checking in installation.xml; /cvsroot/mozilla/webtools/bugzilla/docs/xml/installation.xml,v <-- installation.xml new revision: 1.97; previous revision: 1.96 done Backing bug out as it turned the tinderbox red, pending investigation (and a couple of spelling fixes...) jade:../xml/using.xml:1350:9:E: document type does not allow element "para" here; missing one of "glossary", "bibliography", "index" start-tag jade:../xml/using.xml:1356:9:E: document type does not allow element "para" here; missing one of "glossary", "bibliography", "index" start-tag Oddly, this will build perfectly with xmlto, but will not build with jade on landfill.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Quoting from 'Description' in <http://www.oreilly.com/catalog/docbook/chapter/book/section.html>: "None of the sectioning elements is allowed to "float" in a component. You can place paragraphs and other block elements before a section, but you cannot place anything after it." The 2 <para>s that were causing the error weren't in a <section>, and they came immediately after a </section>. I created a new <section> to hold the last 2 paragraphs. Also corrected two instances of 'wining', and changed an <important> to a <warning>.
Comment on attachment 187961 [details] [diff] [review] Whining docs, draft 3 Works in jade now too...
Attachment #187961 - Flags: review+
Attachment #187119 - Attachment is obsolete: true
Let's try again.... Checking in installation.xml; /cvsroot/mozilla/webtools/bugzilla/docs/xml/installation.xml,v <-- installation.xml new revision: 1.98; previous revision: 1.97 done Checking in using.xml; /cvsroot/mozilla/webtools/bugzilla/docs/xml/using.xml,v <-- using.xml new revision: 1.33; previous revision: 1.32 done
Status: REOPENED → RESOLVED
Closed: 20 years ago20 years ago
Resolution: --- → FIXED
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: