This bug is out of sync with current large features planned (such as cross-database support, customized fields, etc) and doesn't really seem to be on anybody's radar. Can I invalidate it?
If you know the bug numbers for very invasive changes, why not simply add them? (justdave, mattyt and jake already did that in the past.) If you choose to invalidate this bug, please add a pointer to the place where this info is being tracked instead. (Note that this bug doesn't care about mere extensions that involve only very little changes to existing code.)
Reassigning bugs that I'm not actively working on to the default component owner in order to try to make some sanity out of my personal buglist. This doesn't mean the bug isn't being dealt with, just that I'm not the one doing it. If you are dealing with this bug, please assign it to yourself.
Assignee: justdave → general
QA Contact: mattyt-bugzilla → default-qa
Old meta-bug which got no attention at all. Doesn't make sense to keep it open except polluting our queries. Bug 278579 is much more up-to-date. *** This bug has been marked as a duplicate of 278579 ***
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
Target Milestone: Future → ---
You need to log in before you can comment on or make changes to this bug.