AWX modernization backwards compatibility

Hi guys,
Me and my team want to start using the AWX project and build some extra tooling along with it, and we had a few questions regarding the modernization effort.

Were starting development in the next few weeks and contemplating our options considering the upcoming changes, the one were probably going with includes using the new UI (as we want to make some UI changes) with the old API and upgrading once the new API is available,
so:
Is the new UI compatible with the old REST API?
Is the new REST API introducing any breaking changes?
Is there a projected timeline of the modernization effort?

Ask me anything to get more context of the issue,

Thank you

Welcome @shain We’re currently working on an update to provide more information about the modernization effort. (Please see this thread for a bit more detail.)

As mentioned in the thread, there’s a GitHub issue where some folks from the community have been asking questions and working on running off the devel branch. You might find that, and some of the other modernization posts, useful for more context.

Thanks for the questions too. I know I’m not directly answering them right now, which might not be ideal, but it is helpful to hear them. Please stay tuned.