Re: Upgrading Trac

On Sat, May 1, 2010 at 1:03 AM, Jeremy Dunck wrote: > > On Apr 30, 2010, at 10:56 AM, Russell Keith-Magee > wrote: > >> On Fri, Apr 30, 2010 at 11:11 PM, Jeremy Dunck wrote: >>> >>> As long as I'm here, how much interest is there in

Re: Upgrading Trac

On Sat, May 1, 2010 at 1:57 AM, Mike Axiak wrote: > On Fri, Apr 30, 2010 at 11:56 AM, Russell Keith-Magee > wrote: >> So, if we were to integrate a code review tool, it would only be to >> support case 3. I don't have any concrete numbers to back me up,

Re: Trac workflow assistance (commiter feedback needed)

On Friday 30 April 2010 19:22:33 Idan Gazit wrote: > FWIW, I spoke with Alex the other week about turning piano-man into > a more finished product. > > So long as core guarantees that they'll at least take a look at > whatever is made, I'm +1 on rolling our own, and am willing to > champion this

Re: managing javascript and css resources

Owen, The file is only created once, so the compression only happens once. Only when any of the files being aggregated is changed does the file get recreated. In other words, the process is automatic, but it has no performance penalty. Silvio On Apr 30, 10:27 am, Owen Nelson

Re: Upgrading Trac

Is it worth upgrading to the 0.11.X branch with Trac 0.12 scheduled to be out the door within a couple weeks? On the one hand, a brand new Trac release would be more likely to contain bugs than a bugfix branch that's now on it's 7th revision. The configurable workflows and per-user permissions

Re: Trac workflow assistance (commiter feedback needed)

On Fri, Apr 30, 2010 at 3:57 PM, Gabriel Hurley wrote: > I'd also be interested in working on this, as long as I'm not alone on > it. Have you and/or Alex set up any kind of mailing list for it? Do > you plan to use git's issue tracker or something else? What's the > process

Re: Trac workflow assistance (commiter feedback needed)

I'd also be interested in working on this, as long as I'm not alone on it. Have you and/or Alex set up any kind of mailing list for it? Do you plan to use git's issue tracker or something else? What's the process plan for getting development kick-started on it? - Gabriel On Apr 30, 11:22 am,

Re: Trac workflow assistance (commiter feedback needed)

On Apr 30, 8:02 am, Jeremy Dunck wrote: > I haven't heard one proposed.  I'll take a look at RedMine and/or > steal ideas from launchpad -- but writing a new tracker isn't the > problem I'm trying to solve. FWIW, I currently use (and administer) Redmine for my company. I'd

Re: Upgrading Trac

On Apr 30, 2010, at 9:06 AM, Jeremy Dunck wrote: > Does anyone have crib notes on what upgrading from (presumed) 0.10.4 > to 0.11.7 would buy us? If not, I can go read changelogs. > > Separate from that, I'd like to open discussion on what it would take > to do the upgrade. > > Who has access

Re: Trac workflow assistance (commiter feedback needed)

FWIW, I spoke with Alex the other week about turning piano-man into a more finished product. So long as core guarantees that they'll at least take a look at whatever is made, I'm +1 on rolling our own, and am willing to champion this project. I think having something we can easily shape to meet

Re: Upgrading Trac

On Fri, Apr 30, 2010 at 11:56 AM, Russell Keith-Magee wrote: > So, if we were to integrate a code review tool, it would only be to > support case 3. I don't have any concrete numbers to back me up, but > my gut feeling is that case 3 isn't a time sink for me. There is an

Re: Upgrading Trac

On Apr 30, 2010, at 10:56 AM, Russell Keith-Magee wrote: On Fri, Apr 30, 2010 at 11:11 PM, Jeremy Dunck wrote: As long as I'm here, how much interest is there in review board? http://code.google.com/p/reviewboard/ ... 5) The patch is missing

Re: Upgrading Trac

On Fri, Apr 30, 2010 at 11:11 PM, Jeremy Dunck wrote: > As long as I'm here, how much interest is there in review board? > http://code.google.com/p/reviewboard/ I'm not sure. Like Alex, I've never used reviewboard itself. I have used codereview.appspot to review some patches

Re: Upgrading Trac

On Fri, Apr 30, 2010 at 11:06 PM, Jeremy Dunck wrote: > Separate from that, I'd like to open discussion on what it would take > to do the upgrade. To the best of my knowledge, the only things standing in the way of a Trac upgrade are: * Enthusiasm * Time The available

Re: Upgrading Trac

On Fri, Apr 30, 2010 at 11:11 AM, Jeremy Dunck wrote: > As long as I'm here, how much interest is there in review board? > http://code.google.com/p/reviewboard/ > > On Fri, Apr 30, 2010 at 10:06 AM, Jeremy Dunck wrote: >> Does anyone have crib notes on what

Re: Upgrading Trac

As long as I'm here, how much interest is there in review board? http://code.google.com/p/reviewboard/ On Fri, Apr 30, 2010 at 10:06 AM, Jeremy Dunck wrote: > Does anyone have crib notes on what upgrading from (presumed) 0.10.4 > to 0.11.7 would buy us?  If not, I can go read

Upgrading Trac

Does anyone have crib notes on what upgrading from (presumed) 0.10.4 to 0.11.7 would buy us? If not, I can go read changelogs. Separate from that, I'd like to open discussion on what it would take to do the upgrade. Who has access to the server? What do I need to do to convince to let me

Re: Trac workflow assistance (commiter feedback needed)

On Fri, Apr 23, 2010 at 10:26 PM, Russell Keith-Magee wrote: ... >>> I'm not a huge fan of Trac - it's >>> got lots of quirks and bugs that annoy the bejezus out of me, >> ... >> Perhaps upgrading would get us some distance? > > Possibly. Was that you volunteering to

Re: Trac workflow assistance (commiter feedback needed)

On Fri, Apr 30, 2010 at 10:56 AM, Jeremy Dunck wrote: > On Sun, Apr 25, 2010 at 1:27 AM, Stephen Wolff > wrote: >>> I recognize running tests w/ regressions pass would be useful, but >>> it's getting into CI-land -- once we have some CI infrastructure

Re: Trac workflow assistance (commiter feedback needed)

On Sun, Apr 25, 2010 at 5:37 PM, yml wrote: ... > While spending some more time looking at launchpad.net I stumbled upon > another very neat feature you can also sort the bug by heat [1]. Thanks for this -- I'll be reading it shortly. -- You received this message because

Re: Trac workflow assistance (commiter feedback needed)

On Sun, Apr 25, 2010 at 1:27 AM, Stephen Wolff wrote: >> I recognize running tests w/ regressions pass would be useful, but >> it's getting into CI-land -- once we have some CI infrastructure in >> place, I'd be happy to use that. >> >> > > In case you missed it, there

Re: managing javascript and css resources

In this case you're compressing at runtime... or am I missing something? I think I'm just going to burrow for a little while and prototype some helpers. I've got a project coming up shortly with some room for R on this front, so hopefully I'll be able to put them into production for a while

Re: @Meebo - 2 Django Contractors Needed!

On Fri, Apr 30, 2010 at 4:24 PM, Joshua Partogi wrote: > I've noticed that the mailing list name 'django-developers' always > creates confusion for first time users. You aren't the first person to make this suggestion. Here's the most recent discussion about the topic

Re: @Meebo - 2 Django Contractors Needed!

I've noticed that the mailing list name 'django-developers' always creates confusion for first time users. Kind regards, Joshua -- http://twitter.com/scrum8 On Apr 28, 9:51 am, Alex Gaynor wrote: > On Tue, Apr 27, 2010 at 7:14 PM, Kiko Griffin wrote: