jas8522 at gmail.com
Sun Nov 28 03:45:09 UTC 2010
I like Zac's idea of switching to Google Code, although re-creating
dozens of feature requests and bug reports would be quite a hassle. Is
there an import tool from Trac to Google Code?
That said, we *could* start with a clean slate of tickets and only
re-create those which we have milestoned for the next major and minor
Is it worth doing that? Do we lose any features that Trac has and
Google Code does not? (Obviously only features we make use of now).
On Sat, Nov 27, 2010 at 11:30 PM, Christopher Forsythe <chris at growl.info> wrote:
> I don't think you realize how hard it is to update trac as compared to
> updating os x or adium. Adium has a few customizations to boot that
> would need to be worked with.
> On Sat, Nov 27, 2010 at 11:06 AM, Shawn Khan <shawn.khan at gmail.com> wrote:
>> Hello all,
>> I believe we should keep Trac updated as we do with Adium and Mac OS X.
>> This might not fix everything but at least this is closer and we can file a
>> ticket with them about our problem and see where that goes.
>> On Nov 27, 2010 11:52 AM, "Zachary West" <zacw at adium.im> wrote:
>> On Sat, Nov 27, 2010 at 08:08, Jordan <jas8522 at gmail.com> wrote:
>>> We *could* also leave it as is ...
>> I took out the big bat and deleted all the tickets by the user. Annoying
>> spammer, taking advantage of Turkey-based absences.
>> Another option is to upgrade to Trac 0.12 in the hopes that it fixes
>> whatever problems we have and adds better plugins for anti-spam, or going to
>> something hosted like Google Code's project stuff (I have the 'adium'
>> project there: <http://code.google.com/p/adium>), though I'm not sure how
>> much it has matured since I last looked at it a year or so ago.
More information about the devel