Jonathan Jesse wrote:
> Cody A.W. Somerville wrote:
> > They've already produced the bug if they've reported it. It is
> > obviously important to ask if it is reproducible every time but the
> > more critical information is determining _how_ to reproduce it. If you
> > can't reproduce it on the ver
Hi Cody,
Cody A.W. Somerville wrote:
> On 3/20/08, Jonathan Jesse <[EMAIL PROTECTED]> wrote:
>
>
>
>
>> Good morning,
>>
>> How would you suggest doing this instead? I am one of those that is combing
>> launchpad for bugs that have not been reported or updated for a long time.
>> I try to rep
On Thu, Mar 20, 2008 at 10:49 AM, Cody A.W. Somerville <
[EMAIL PROTECTED]> wrote:
> On 3/20/08, Jonathan Jesse <[EMAIL PROTECTED]> wrote:
>
>
>
> > Good morning,
> >
> > How would you suggest doing this instead? I am one of those that is
> combing
> > launchpad for bugs that have not been repor
On 3/20/08, Jonathan Jesse <[EMAIL PROTECTED]> wrote:
> Good morning,
>
> How would you suggest doing this instead? I am one of those that is combing
> launchpad for bugs that have not been reported or updated for a long time.
> I try to reproduce the bugs on my own system or vm which I try to
On Thu, Mar 20, 2008 at 5:00 AM, Sitsofe Wheeler <[EMAIL PROTECTED]> wrote:
> Many bugs reported turn out to be "hit and run" reports where something
> is filed and never followed up. As such it is good that bugs are
> aggressively closed where possibly to prevent launchpad cluttering up.
> Unfort
Many bugs reported turn out to be "hit and run" reports where something
is filed and never followed up. As such it is good that bugs are
aggressively closed where possibly to prevent launchpad cluttering up.
Unfortunately there are scenarios where this becomes problematic.
These days I see people
