Nice job guys. Should make things much more clear.
Since the update I noticed that this page [1] no longer works. Thing
is, it's the only one with a problem that I could find (not that I
checked every page) and of course it is the one I wanted.
[1]:
http://code.djangoproject.com/browser/django
On Jan 18, 11:31 am, telenieko <[EMAIL PROTECTED]> wrote:
Maybe the WikiStart could be locked down so newcomers don't get confused? It
does not need to be changed that much ;)
Or at least set some guidelines for it. It seems to get more cluttered
by the day. I would like to see some of those
Maybe the WikiStart could be locked down so newcomers don't get confused? It
does not need to be changed that much ;)
On 1/18/07, Jeremy Dunck <[EMAIL PROTECTED]> wrote:
On 1/18/07, Jeff Forcier <[EMAIL PROTECTED]> wrote:
...
> Anyway, don't know if the current blank-ness is because someone wa
On 1/18/07, Jeff Forcier <[EMAIL PROTECTED]> wrote:
...
Anyway, don't know if the current blank-ness is because someone wanted
to vandalize,
251 was vandal, 252 was removing the vandalism, but not restoring the original:
http://code.djangoproject.com/wiki/WikiStart?action=diff&version=251
--~
Looks like someone's been futzing with the wiki frontpage, although I'm
unsure if it's really intentional or not: it's currently blank, but
when I tried to restore it to the last "good" version, Akismet
complains thusly:
Submission rejected as potential spam (Maximum number of external
links
Hi,
I'm being hit by a bug in trac. Whenever I try to attach a tar file,
I get this traceback from the trac installation:
Traceback (most recent call last):
File "/home/trac/new-djangoproject-trac-test/trac/web/main.py",
line 387, in dispatch_request
File "/home/trac/new-djangoproject-trac-te
On 1/17/07 7:45 PM, telenieko wrote:
Hi, what happened to "Milestones" ? I know there's the "Version" field, but
it only includes already released versions and SVN, I can no longer mark a
bug "blocker of 1.0" (which could be achieved with milestone=1.0 and
priority=blocker) how can "Must be solv
Hi, what happened to "Milestones" ? I know there's the "Version" field, but
it only includes already released versions and SVN, I can no longer mark a
bug "blocker of 1.0" (which could be achieved with milestone=1.0 and
priority=blocker) how can "Must be solved for 1.0" bugs be marked now?
Cheers
'Nother little thing, I fixed the broken link for "View active
tickets, make bug reports and contribute feature requests. " on
http://code.djangoproject.com/wiki to point to the "Reports" tab but
now the description's a bit off since from there you can't open new
tickets. Maybe needs two bull
On 1/17/07 5:24 PM, Honza Král wrote:
> I am really looking forward to listing through "patch needs
> improvement" and "has_patch" == no
> whenever I have the time and feel like some coding... ;)
Check out:
http://code.djangoproject.com/wiki/Reports#Ticketsneedingsomework
That should help anyon
Jacob Kaplan-Moss wrote:
> I'm about to roll out an upgrade to our Trac installation on
> code.djangoproject.com. We're adding a few features to make our internal
> management of ticket workflow better (some of you many have the thread about
> this on django-developers over the past week or so).
On 1/17/07 5:05 PM, Robert Myers wrote:
> Only one tiny remark, the closed tickets use to show up with a
> strike-through, possibly a missing css param?
Indeed - thanks, and fixed.
Jacob
--~--~-~--~~~---~--~~
You received this message because you are subscribed t
I love the new interface as well, congrats everyone!
Only one tiny remark, the closed tickets use to show up with a
strike-through, possibly a missing css param?
Robert
On 1/17/07, Deryck Hodge <[EMAIL PROTECTED]> wrote:
>
>
> On 1/17/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> > I'd also
On 1/17/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> Howdy folks --
>
> I'm about to roll out an upgrade to our Trac installation on
> code.djangoproject.com. We're adding a few features to make our internal
> management of ticket workflow better (some of you many have the thread about
> t
Robert Myers wrote:
> Only one tiny remark, the closed tickets use to show up with a
> strike-through, possibly a missing css param?
Oops, Robert beat me to it.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Djan
... and, as most people have noticed, we're done.
Triagers: you're good to start reviewing tickets. Of course anyone who has
time to help out by reading ticket comments and upadaing the "needs *" flags
accordingly is welcome to help.
Jacob
--~--~-~--~~~---~--~
Jacob Kaplan-Moss wrote:
> I'd also like to take this time to welcome Django's new official ticket
> managers:
>
> * Chris Beaven (aka SmileyChris)
> * Simon Greenhill
> * Michael Radziej
> * Gary Wilson
>
> Although anyone can -- and is encouraged to -- help out keeping
On 1/17/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> I'd also like to take this time to welcome Django's new official ticket
> managers:
>
> * Chris Beaven (aka SmileyChris)
> * Simon Greenhill
> * Michael Radziej
> * Gary Wilson
>
> Although anyone can -- an
On 1/17/07, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> I'd also like to take this time to welcome Django's new official ticket
> managers:
>
> * Chris Beaven (aka SmileyChris)
> * Simon Greenhill
> * Michael Radziej
> * Gary Wilson
>
> Although anyone can -- an
On Jan 17, 9:19 pm, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
> * Chris Beaven (aka SmileyChris)
> * Simon Greenhill
> * Michael Radziej
> * Gary Wilson
> Let's have a big virtual standing ovation for them!
Thanks guys! Thanks to the whole team in fact!
Hopefu
Howdy folks --
I'm about to roll out an upgrade to our Trac installation on
code.djangoproject.com. We're adding a few features to make our internal
management of ticket workflow better (some of you many have the thread about
this on django-developers over the past week or so).
There might b
21 matches
Mail list logo
