I'd like to know ohw's handling the bug reports.
I'd also like to know who assigns the bug reports, and to whom can he assign them to?
As well as how the assigned is notified?
Please don't tell me it's all vroom.
(Can the system overlord do everything?)

I recently made bug#243, cause perlfunc:index is kinda blank, and then i discovered bug#222.

Now this hasen't been fixed, yeah it's not life threatning, but should be.

Yeah I know that the bug report facility was kind of broken, after all i did make bug#223. And yeah I know bug reports go kind of slow, but dkubb made bug#222 in January.

And overall, all the POD located here is outdated. I really like this site(if you couldn't tell already), and I feel d'pod should be updated. Half the time when i'm programmering in perl, and want to look at the latest POD, i just go to my local copy, and miss out on some important cb conversation. I'd rather have the up-to-date pod here, at perlmonks, so that I have one less reason to leave, even if for only a moment.

And as for super search, does anyone know what the long term cost is?
(see, you can end a question with a prep·o·si·tion)

 
___crazyinsomniac_______________________________________
Disclaimer: Don't blame. It came from inside the void
perl -e "$q=$_;map({chr unpack qq;H*;,$_}split(q;;,q*H*));print;$q/$q;"

  • Comment on Crazy about a bug report (and POD and super search)

Replies are listed 'Best First'.
Re: Crazy about docs
by footpad (Abbot) on Mar 25, 2001 at 22:58 UTC

    Regarding online versions of the latest docs, you can always use perldoc; it looks like it's up to date.

    I realize that this means you're still leaving the Monastery and agree that it would be nice to update the local docs. I thought it worht pointing out because a) we often caution against needlessly reinventing the wheel, b) to raise awareness of that site (in case some monks aren't aware of it, and c) to provide an alterntative (aka a workaround) until the local copies are updated.

    --f

    Update: Added second paragraph to reply to crazyinsomniac's reply.

[reply]
      No. The whole point is to make perlmonks better, and for me not to leave perlmonks. Like i said i could just as easily switch to my local copy of the pod, but i'd rather not.

       
      ___crazyinsomniac_______________________________________
      Disclaimer: Don't blame. It came from inside the void
      perl -e "$q=$_;map({chr unpack qq;H*;,$_}split(q;;,q*H*));print;$q/$q;"

[reply]
Re (tilly) 1: Crazy about a bug report (and POD and super search)
by tilly (Archbishop) on Mar 26, 2001 at 02:56 UTC
    I would prefer that people learn to use and rely on their local documentation. It is simply impossible for this website - or any documentation external to your system - to accurately document what people have installed.

    Do you choose Perl 5.005 as the current version? Then our does not exist!

    Do you choose Perl 5.6 as the current version? Then our does exist and we get into the confusion discussed at RE (3): Should I use $ and $# ?. Either way people are relying on incorrect information.

    Instead I would like to see the documentation remain at something resembling a lowest common denominator but for every page to have added to it the following:

    This documentation is probably for a different version of Perl than you have. For the version of this document applicable to your system type perldoc -f open
    (Where open is just an example.)
[reply]

Back to Perl Monks Discussion