Thanks for responding Justin. Your response, however, contradicts the
"Contributing to Django" doc says that its ok for the general
community to move bugs into "Accepted" if they're obviously bugs:
> Triage by the general community
> Although the core developers and ticket triagers make the big decisions in the ticket triage process, there’s also a lot that general community members can do to help the triage process. In particular, you can help out by:
> * Promoting “Unreviewed” tickets to “Design decision needed” if a design decision needs to be made, or “Accepted” in case of obvious bugs.
IMO, its an obvious bug, but it would be great to get it on the work
stack of someone who knows that code better.
I'm just trying to figure out what the best action I can take to get
this bug fixed/committed and its really not clear :-/
--
--Leo
On Nov 14, 4:13 pm, Justin Lilly <
jus...@justinlilly.com> wrote:
> The accepted tag is typically for someone triaging to accept that yes, this
> really is a bug (that we want to fix). You should not change this yourself.
>
> -justin
>
> On Fri, Nov 13, 2009 at 7:24 PM, Leo <
leo.shklovs...@gmail.com> wrote:
> > Could I please get a core committer or a triager to take a look at
> > this ticket and triage it please? It fixes a fairly core bug in the
> > db.model.field code:
>
> >
http://code.djangoproject.com/ticket/11716
>
> > What's the right process here, should I move it to 'Accepted' myself?
>
> > --
> > --Leo
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "Django developers" group.
> > To post to this group, send email to
django-d...@googlegroups.com.
> > To unsubscribe from this group, send email to
> >
django-develop...@googlegroups.com<
django-developers%2Bunsu...@googlegroups.com>
> > .