+1 There was also a suggestion at JuliaCon the badge could count the number of warnings displayed - perhaps, this would give some incentive for progressive cleanup/levelingup of code.
On Tuesday, July 12, 2016 at 1:15:24 PM UTC-4, Erik Schnetter wrote: > > Our Julia projects live on Github, and many projects proudly present > badges for Travis, Appveyor, Codecov, and probably a few more. TL;DR: There > should be a badge for "no compatibility warnings" as well. > > In the past weeks, Julia 0.5 deprecated a certain number of features. > These continue to work fine, but lead to long trails of "WARNING: XYZ is > deprecated". Usually, some package depends on some other packages, and one > of these isn't using Compat in the right way yet, and the result is a long > string of "Base.OS_NAME is deprecated in deps/build.jl:21", repeated 27 > times, in some package for which you have only a tangential interest. > > I've occasionally began to fix this for packages where I contribute (HDF5, > MPI), and for packages they use (BinDeps, Compat), but truth be told, > there's a lot of these warnings, and it's not always easy to figure out > where they come from, or whether they are already fixed on the package's > master branch, which just hasn't been tagged yet. > > So -- here is my idea: Create a badge for "my project doesn't show any > compatibility warnings for the Julia master branch". I'd happily add it to > all my projects. > > -erik > > -- > Erik Schnetter <[email protected] <javascript:>> > http://www.perimeterinstitute.ca/personal/eschnetter/ >
