On Mar 29, 4:47 pm, Gabriel Hurley wrote:
> The component re-organization is done now, as per Julien's (and Jannis')
> suggestions above. I even re-categorized the 84 tickets that were in
> "Contrib apps" into their new separate contrib.foo components (thank god for
> Trac bulk
The component re-organization is done now, as per Julien's (and Jannis')
suggestions above. I even re-categorized the 84 tickets that were in
"Contrib apps" into their new separate contrib.foo components (thank god for
Trac bulk modify privileges!).
The organization definitely makes more sense
On Mar 29, 8:58 am, Gabriel Hurley wrote:
> I can work on it late tonight (about 6-8 hours from now) if no one else gets
> to it.
>
> All the best,
>
> - Gabriel
Excellent, thank you Gabriel! There's no rush -- whenever it suits
you. Let me know if I can help in any way.
I can work on it late tonight (about 6-8 hours from now) if no one else gets
to it.
All the best,
- Gabriel
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com.
To
On Mon, Mar 28, 2011 at 4:08 PM, Julien Phalip wrote:
> I wouldn't mind trying but I don't have much experience administering
> Trac and I wouldn't want to make a mess. Earlier in this thread
> Gabriel has offered to help as he's got the Trac skillz.
>
> Gabriel, are you
On Mar 29, 2:01 am, Jacob Kaplan-Moss wrote:
> On Mon, Mar 28, 2011 at 12:56 AM, Julien Phalip wrote:
> > Now that 1.3 has been released (yay!), I'm reviving this thread to see
> > if we can make Trac a little more efficient on our way to 1.4. I'll
> > try
On Mon, Mar 28, 2011 at 12:56 AM, Julien Phalip wrote:
> Now that 1.3 has been released (yay!), I'm reviving this thread to see
> if we can make Trac a little more efficient on our way to 1.4. I'll
> try to summarise what's been suggested so far in regard to improving
> and
On 28.03.2011, at 07:56, Julien Phalip wrote:
> Now that 1.3 has been released (yay!), I'm reviving this thread to see
> if we can make Trac a little more efficient on our way to 1.4. I'll
> try to summarise what's been suggested so far in regard to improving
> and clarifying the "Component"
On 03/28/2011 02:33 AM, Russell Keith-Magee wrote:
> As with the other thread on Trac changes -- I agree this is worth
> doing, but would like to hear some other core dev voices before making
> any changes.
These changes look to me like a gain in sanity on every front. +1
Carl
--
You
On Mon, Mar 28, 2011 at 1:56 PM, Julien Phalip wrote:
> Hi all,
>
> Now that 1.3 has been released (yay!), I'm reviving this thread to see
> if we can make Trac a little more efficient on our way to 1.4. I'll
> try to summarise what's been suggested so far in regard to
Hi all,
Now that 1.3 has been released (yay!), I'm reviving this thread to see
if we can make Trac a little more efficient on our way to 1.4. I'll
try to summarise what's been suggested so far in regard to improving
and clarifying the "Component" field:
* The "Contrib apps" component would be
I'm not endorsing any specific set of changes here, but I can address the
feasibility of making the changes in Trac:
>From empirical testing on my own Trac installation (running 0.11 currently,
Django is on 0.12) updates to components, resolutions, etc. all propagate
correctly when edited
On Feb 28, 10:58 am, Paul McMillan wrote:
> I think the django-admin.py categories could be consolidated into a single
> one.
>
> In the interest of readability, we might rename django.contrib.foo to
> simply contrib.foo.
>
> As long as we're clarifying, "Django Web Site" might
>> * The "Contrib apps" component [1] should be made redundant and new
>> components for each missing contrib app (e.g. contenttypes, sitemaps)
>> should be added. I mean, even databrowse has its own component! :) The
>> "Contrib app" mixes lots of unrelated things, making it a bit
>> pointless.
On Mon, Feb 28, 2011 at 4:13 PM, Julien Phalip wrote:
> Hi,
>
> Tweaking Trac seems to be in the air, so I had some more ideas to
> suggest :)
>
> The "component" field in Trac is very useful when people look for
> tickets in their areas of familiarity/expertise. I think there
Hi,
Tweaking Trac seems to be in the air, so I had some more ideas to
suggest :)
The "component" field in Trac is very useful when people look for
tickets in their areas of familiarity/expertise. I think there are a
few things that should be cleaned up to make the system a bit more
useful and
16 matches
Mail list logo