stop publishing for Scala 2.11 #1729
Conversation
bjaglin
force-pushed
the
scala211
branch
2 times, most recently
from
4328fe8
to
610820b
Compare
|
Hi @julienrf! Apologies for the random ping, but I am planning to cut a minor release with this PR in the coming weeks (when the new Scala releases are out), so I am looking at getting some data to confirm my decision (and revert if needed). I realize I should have done that earlier... I don't have access to Sonatype OSS - is there any chance you or someone with access could pull download stats on the 2.11 artifacts (relative to other versions)? Happy to discuss further on Discord in case you are not comfortable sharing this openly. More generally, I'd be happy to see more trends (maybe there is a way to get me an account with limited rights on Sonatype OSS?). Thanks! |
|
Hey @bjaglin, Unfortunately, managing access rights with Sonatype is a bit complicated. And there is no way to create an account with access to the stats only. Currently, scalafix is published with the organization-wide Scala Center credentials. I could create a new Sonatype user just for Scalafix and share the credentials with you but if you are only interested in the stats, maybe for now I can simply share this screenshot?
This is the total number of downloads for scalafix-core for 2.11. For the record, for both 2.12 and 2.13, numbers are more like 250k downloads per month. Please let me know if this is enough. And in case you would like to see more stats, I can also set up a script like this one. |
|
Thanks for the insights @julienrf !
Definitely. By June, when I get more bandwidth to actively maintain scalafix (as I have had close to zero in the last year), I'd like to deprecate stuff towards a 1.0 and having a breakdown of versions usage would help me find the right level of aggressiveness. But I can reach out at that time.
It looks like the repo is private and I couldn't find what it generates, but I don't think it's worth the investment. Thanks though! |
Closes #1635