So some thoughts here:
Chronos is/was/maybe still is an important part of Mesos clusters that have been deployed. Now, I am not saying all Mesos clusters use Chronos, but for those clusters that DO use it, it's a critical component. Chronos has been, neglected, not updated, etc. And I am not trying to demand free maintenance on something like Chronos, but at the same time, while open sourced, its hard for some shops to have the dev skills to update it. The analogy, if we will take the most common analogy is if Mesos is like the Linux Kernel, and DC/OS is like Ubuntu or CentOS, then obviously, Cron is like Chronos (which folks have already come to the conclusion on). Well, to take that further, how many people work on Cron? I know Paul Vixie, and he's a great guy, but cron just isn't developed by "users" of Ubuntu... it doesn't happen. Now, I know Mesosphere has limited resources, but a change has been made, please help us transition and understand! :)
So some thoughts on Chronos -> Metronome
1. Please be clear about the roadmap here. Metronome was included in DC/OS 1.8 as the "master" scheduler so it could unify the interface with the included Marathon. Some posts on why, and how this integration happened would be very helpful to the community.
2. As has been asked, understanding the migration steps, would be very beneficial for those using Chronos already. Given Chronos hasn't had much dev work, and now this new thing is there, it's going to be a natural question so when people are working with their clusters, they have a sense of understanding on how to switch, why they've switched and what the end result may look like.
3. Understanding the "multi-role" Chronos setup and being able to answer is would be very important for some users (*raises hand) I see every tenant or role on my cluster having a Marathon and Chronos/Metronome instance that they can work with. This question on Metronome also extends to Marathon, with Marathon now being assimilated into the DCOS interface, can we still install Marathon as a service for specific roles?
I think when a change is made like the Chronos->Metronome transition, helping the community understand the plan can go a long way to easing the transition and getting support and assistance moving forward.