Are you using Sonatype Nexus Repository 2's Yum support? If so, we want to hear from you.
As you may know, we're in the process of building out Yum support for Nexus Repository v3 - we've released proxy support in Nexus Repository 3.5.0, and our Yum hosted support is approaching the finish line.
We're taking a different approach to implementing Yum support than in Nexus Repository 2. Because of 2's architectural limitations, we implemented Yum support on top of maven2: You store your RPMs inside a maven2 repository, and a Yum capability generates the Yum-specific metadata.
Nexus Repository 3 frees us from a Maven-centric architecture, so we've built a pure Yum implementation, not connected to Maven. This means we need to carefully understand how people use Yum in Nexus Repository 2, because a direct migration isn't possible.
How are you using Yum in Nexus Repository 2? Are you mixing your maven2 and Yum components in your repositories, or are you keeping them separate? How much Yum do you have?
If you're using Nexus Repository 2 Yum repositories, we want to hear from you. Take our survey on Yum migration and tell us about your experiences using Yum with Nexus Repository 2.