Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ukma!tut.cis.ohio-state.edu!att!ihuxy!vg55611
From: vg55611@ihuxy.ATT.COM (Gopal)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: How does a RUSH category sound?
Summary: How about priority based on demand ?
Message-ID: <2976@ihuxy.ATT.COM>
Date: 5 May 89 00:25:00 GMT
References: <7090@bsu-cs.bsu.edu> <3156@epimass.EPI.COM>
Reply-To: vg55611@ihuxy.UUCP (55421-Gopal,V.P.)
Organization: AT&T Bell Laboratories - Naperville, Illinois
Lines: 21

>In article <7090@bsu-cs.bsu.edu> dhesi@bsu-cs.bsu.edu (Rahul Dhesi) writes:
>How does a RUSH category sound for comp.binaries.ibm.pc?  If an
>incoming submission is marked RUSH in the subject heading,
>
>  -- it gets posted in 24 to 48 hours
>  -- it is not tested, nor assigned a volume/issue number

I have a different suggestion.  How about processing the programs that
are in demand most ?  The person who sends the program to the net also
posts a note to c.b.i.p.d saying that such a program has been posted
(with explanations of bug fixes etc.).  People who cannot wait can
send email to RD and RD can prioritize based on such demand.  I understand
this will be more work for RD but it is better than RUSHing ....

May be RD can also post a backlog list bi-monthly showing current priority.

Venu P. Gopal
UUCP:	att!ihuxy!vg55611
Internet: vg55611@ihuxy.att.com
BITNET: com%"vg55611@ihuxy.att.com"   or   com%"vg55611%ihuxy@research.att.com"
Silence those silent letters and save the world 500 million keystrokes a day.