Thanks, Jeremy. I'd like to add that all new features don't necessarily need to be added to the old Traffic Ops UI. That precedent has already been set with features like Delivery Service Cloning and URI Signing which are only available in Traffic Portal as of today, and I think that's perfectly acceptable given the plan to deprecate the old Traffic Ops UI in the near future.
I'm not sure if we need to formalize this with a vote or not because the precedent is already set, but I'd say we should continue to fix things like bugs and security issues but not add new features/enhancements to the old Traffic Ops UI. This should reduce the burden of shipping new features in Traffic Control while we're in this stage of having two different UIs. - Rawlin On Tue, Mar 6, 2018 at 3:12 PM, Jeremy Mitchell <mitchell...@apache.org> wrote: > At last year's TC summit, we discussed the deprecation of the TO UI in > favor of the Traffic Portal. > > Now that TP has almost achieved feature parity with the TO UI, that day is > coming soon. > Here are 2 issues I know that need to be complete to achieve feature parity: > > https://github.com/apache/incubator-trafficcontrol/issues/1616 > https://github.com/apache/incubator-trafficcontrol/issues/1287 > > Deprecation may mean simply deleting traffic_ops/app/public/ for 2.3 (or > 3.x). Or maybe it means something else. Not sure yet. > > But the point is, if you want to ensure that all new UI features that you > build live past 2.3 (or 3.x), please be sure to put those features in TP. > Reach out to me if you need help with TP. > > Jeremy
