Re: Bug status suggestion (was Re: 19990607.008)

Richard Soderberg wrote:
> 
> Most definitely.  Some sort of status to signify that action
> has been taken by a bugdb admin, and now we're waiting for some
claimed | 
???

> On a side note, none of the help documentation seems to specify
> any sort of example email subject commands for the bugdb; am I
> missing a nonobvious connection between http://bugs.perl.org
Don't forget to differentiate between the user and admin sides.  The help from
both web and email frontends are different depending on context.  For example
casual users will not get details of administration commands (if I can help
it).  Though they may well be able to extrapolate out :-)  It's not designed
as a secret interface, (the code is open), but to seperate out the two
functionalities.

It's possible for example that you might do better to look under:
	http://bugs.perl.org/admin/perlbug.cgi?req=help
............................._____.....................

> and what I'm supposed to send to [email protected]?
If you send mail to the [email protected] or [email protected] address, with a
subject line of -h you should get a help mail back that will help :-)  

-H (upper case) will bring back more examples.

	To: [email protected]
	Subject: -H

I'm in the process of upgrading the docs, while more people are using the
system and asking the same questions.  These have been updated:
	
	http://bugs.perl.org/admin/perlbug.cgi?req=help 
	http://bugs.perl.org/admin/perlbug.cgi?req=spec

When the FAQ lands, I'd like to put that there too.
	http://bugs.perl.org/perlbug.cgi?req=faq 

In the meantime here is the current result from the above email (to save you
the trouble :-)

Automatic response from the Perlbug database
--------------------------------------------------------------------------------

-H: 
A searchable live reference database of email-initiated bugs and patches.  For
more details see the specification: 
        
        http://bugs.perl.org/perlbug.cgi?req=spec
                        

NOTE:
All switches and arguments to the email interface are expected to be separated
by a space.

RETRIEVAL:
There are several different ways of searching the db:
    by ticketid:    t, T
    by messagid:    m, M
    by subject:     s
    by messagebody: b
        by sql query:   b
    by overview:    o

Upper case letters usually expand upon or reverse the effect of the lowercase
command in some way.

r will return all tickets with optional search criteria.
eg; 
    '-r low library'  (status = 'low' and category = 'library') 
    '-r lo li'        (status = 'low' and category = 'library')
    '-r l'                (status = 'low' and category = 'library' :-)
    '-r mac op pat'   (status = open and category = 'patch' and osname =
'macos')

Note that 'p' is acceptable as a shortened form of 'patch' etc. and may 
be defined by either the first letter or the next several letters, if they 
uniquely identify the available flag, (look at 'l').  If not unique you get
all 
the flags in an 'and' operation.

The sql query (q) command expects to see the keyword 'select' at the start of
each 
query included in the body of the email.  These are not restricted to any
particular 
set of fields and it is possible to exersize full searches on the db.
    
When an item is requested from the db, the data is formatted according to the 
format (-f) flag setting and returned via email.  The supported flags are: 
    a (ascii-default), A (more info), h (html), H (more data in your HTML)
    
EXAMPLE:
Below is an example email which retrieves tickets: '19990606.002' and
'19990606.003', then returns this help message, along with all open tickets, 
and those which are still open and under the patch category, then returns the 
results with a copy to the extra email address:

    To: [email protected]
    Subject: -e [email protected] -t 19990606.002 19990606.003 -h -r p

    
TUTORIAL:
Beginners may get used to the system by trying out these subject lines:
    -H
    -h
    -o
    -t 19990606.002
    -T 19990606.003 
    -m 7
    -r util clos
    -r b sev op
    -o -h -m 3 55 21 -r abandoned patch -f A
    -Q
etc.
    
Comments, feedback, suggestions to '[email protected]'.

ADMINISTRATION: 
The admin (-a) command reads like this:
    set these flags, (if not an admin of this ticket - make me one),
    in the following ticketids eg;
    
    -a closed build 19990606.002 19990606.003 
        #translates to:
            UPDATE tm_tickets
            SET status = 'closed' and category = 'build' 
            WHERE ticketid IN ('19990606.002', '19990606.003')
        
    Shortcuts are acceptable and '-A' has added-value by returning the ticket
    -A c p 19990606.002 19990606.003
        #translates to:
                UPDATE tm_tickets
                SET status = 'closed' and category = 'patch'
                WHERE ticketid IN ('19990606.002', '19990606.003')
    
        You may also use To: addresses to a similar effect:
        
        To: [email protected]
        
        
--------------------------------------------------------------------------------
Message from the Perlbug squashing team at '[email protected]'