Open Bug 232113 Opened 21 years ago Updated 10 years ago

Remove old charting system

Categories

(Bugzilla :: Reporting/Charting, defect)

2.17.6
defect
Not set
normal

Tracking

()

People

(Reporter: gerv, Unassigned)

References

(Depends on 2 open bugs, Blocks 1 open bug)

Details

This bug tracks the removal of the old charting system - reports.cgi. The new
one (chart.cgi) has a superset of the old function, and so once it is proven in
practice, we can throw the old away and just use the new.

It is expected that the new one will be considered proven once it's been running
on b.m.o. for a few months.

Gerv
No longer blocks: 176011
gerv, ready to remove it? ;)
gerv, if we want to avoid new bugs about old charts (which would all be
wontfixed), it looks like a good idea to remove this stuff completely before we
release 2.20...
Flags: blocking2.20?
Hmm. On the one hand, there are still bugs in new charts, and I haven't had time
to fix them, and I feel guilty. On the other hand, you are right - we don't want
to support two charting systems for another cycle.

Feel like making a patch? :-)

Gerv
(In reply to comment #3)
> Feel like making a patch? :-)

If you could come a few minutes on IRC, we could discuss what needs to be done. ;)

Is it sufficient to nuke reports.cgi? Does it affect Series.pm in some way?
I think major feature *removal* is also something we shouldn't do while we're
frozen, particularly not after an RC. Of course, you can petition justdave if
you disagree with me.
Flags: blocking2.20? → blocking2.20-
Depends on: 306045
QA Contact: mattyt-bugzilla → default-qa
Depends on: chartsys_rewrite
Old Charts should not be removed unless --regenerate works for New Charts.

Also, if Old Charts had Date Period limit, it would do 95% of what I need.
--regenerate is never going to work for New Charts. We don't have the historical data, writing a generic database rollback mechanism is an enormous effort, and the result would take days to run. It's not going to happen.

Gerv
Assignee: gerv → charting
You need to log in before you can comment on or make changes to this bug.