On Fri, Apr 30, 2010 at 11:06 PM, Jeremy Dunck <jdu...@gmail.com> 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 quantities of these resources (especially the former) have been depleted by past nightmare upgrades. > Who has access to the server? What do I need to do to convince to let > me upgrade? To the best of my knowledge, the list of people with access to the server is: * Jacob * James Bennett * A couple of sysadmins at the Journal World who have instructions to kick various reset buttons if smoke starts pouring out and the first two aren't contactable. As for who do you have to convince? If you're volunteering to look after Trac, you don't have to convince me :-) > This is purely exploratory-- I imagine the workflow stuff I'm trying > to do doesn't really need the upgrade, but Russ complained a bit about > nits, so I thought I'd at least see what's what. Agreed. Thanks for doing this, Jeremy. Yours, Russ Magee %-) -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
