On 22/04/2007, at 9:02 AM, Ming-Wei Shih wrote:
But there are a lot of issues and I am lazy :-)
lazy approach would have been to keep using the same trac db.
- the user DB do not match on the 2, it will be a hard time to figure out who's who and if the user does not exist on the new one, how should we handle it? A lot of devs/users have come and gone or changed nick.
Can trac expire users after a period of no activity?
- It's a way to clean things up. There are too many "is it a bug or a feature"tickets, so if the person who filed the bug does not care about the it(notwanting to move it) who should? For example I see bug from 2005 stillopen.
Well perhaps many people have found the same bugs and haven't reported them because they've already been reported! You can't assume that nobody cares about a bug because the original filer is no longer around to move the bug to the new trac.
I think it would be best to suck up the whole database for trac, all users and bugs and everything. I don't think it makes sense to start a new one afresh.
Jesse
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Callweaver-dev mailing list [email protected] http://lists.callweaver.org/mailman/listinfo/callweaver-dev
