On Thu, Jul 20, 2006 at 08:52:34PM -0700, Brett Cannon wrote:
> * Summary
> A one-line describing the problem so as to make it easy for
> developers to spot whether they have the expertise needed to work on
> the bug.
Summary is also displayed as a title on index and search pages, so it is
Kevin Jacobs <[EMAIL PROTECTED]> wrote:
> It may just be bad karma, but SourceForge tends to lock or go off into
> lala land whenever I log in. Thus, I would file many bug reports, with
> a reply-to address, if non-login bug submissions where allowed. My long
> term hope is that you toss out S
On 7/21/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Brett> Sure. It can also wait until we begin discussing the transitionBrett> to our next bug tracker.Would be kinda nice if the new bug tracker allowed submitters to enter afollowup email address without formally logging in. (Of cou
Brett> Sure. It can also wait until we begin discussing the transition
Brett> to our next bug tracker.
Would be kinda nice if the new bug tracker allowed submitters to enter a
followup email address without formally logging in. (Of course, email-based
submissions would go a long way to
On 7/20/06, Fred L. Drake, Jr. <[EMAIL PROTECTED]> wrote:
On Friday 21 July 2006 00:10, Neil Hodgson wrote: > Brett Cannon: > > But SourceForge does not support anonymous reporting. > >SourceForge does support anonymous reporting. A large proportion of
> the fault reports I receive for Scintil
On Friday 21 July 2006 00:10, Neil Hodgson wrote:
> Brett Cannon:
> > But SourceForge does not support anonymous reporting.
>
>SourceForge does support anonymous reporting. A large proportion of
> the fault reports I receive for Scintilla are anonymous as indicated
> by "nobody" in the "S
Brett Cannon:
> But SourceForge does not support anonymous reporting.
SourceForge does support anonymous reporting. A large proportion of
the fault reports I receive for Scintilla are anonymous as indicated
by "nobody" in the "Submitted By" column.
https://sourceforge.net/tracker/?group_id=243
Here is a first stab at writing up guidelines for people to follow
when reporting bug. If this goes well I will also do ones for
patches, committing, and PEPs.
-Brett
---
These sets of guidelines are to help you file a bug report for the Python
p
