Hi Cameron, Jeff,
Thanks -- I will go ahead and push these to the main yt repository.
I'll also redirect all the current Trac links over there, and slowly
start converting the Wiki.
The bugreport command might be pretty easy to implement, but I'll ping
Cameron off-list to see if we can iterate on a good interface for it.
On Thu, Jun 2, 2011 at 2:00 PM, Cameron Hummels
agreed. great work!
i like the idea about a yt bugreport. perhaps it would drop you into your
default text editor with a form that you could fill out and then submit the
bug? before submitting, it could ask you if you have verified that it is a
new and real bug by going through the mailing list history, the existing bug
reports and also going on irc to discuss it. if people do these steps, then
there may not actually be a need to send it to yt-dev because the community
might already know about it, although i suppose it couldn't hurt.
On 6/2/11 4:45 PM, j s oishi wrote:
> looks awesome.
> On Wed, Jun 1, 2011 at 10:07 PM, Matthew Turk<matthewturk(a)gmail.com>
>> Hi all,
>> I've created a test repository with the tickets from the old Trac
>> installation imported.
>> Here are the issues:
>> You can browse around, see the components, etc, and filter as well.
>> This is all the issues.
>> The conversion is a bit lossy, in that old comments and whatnot had to
>> be included in the main content of the issue. And I believe most of
>> the InterTrac links have been broken. But otherwise I think I'm
>> mostly happy with it. Can I get +1/-1 on the current conversion
>> process? I'll migrate the tickets once we're settled on how to
>> convert them.
>> After tickets have been migrated, I will probably close down Trac.
>> I'd also like to start encouraging people to report bugs on BB,
>> possibly even through a "yt bugreport" command. It might also be a
>> good idea to have new ticket reports echoed to yt-dev. Thoughts on
>> Yt-dev mailing list
> Yt-dev mailing list
Yt-dev mailing list