Another suggestion would be to allow the package maintainer to specify which version of code s/he wants to test with each version. As an example, I will be tagging a version of my package that will be the final one that supports 0.3; it will make no sense for successive releases of the code to be tested against 0.3, but I'd love to know if something breaks in that final tag.
On Wednesday, September 2, 2015 at 11:23:09 AM UTC-7, David Anthoff wrote: > > Sounds good to me! The visual is actually quite good with different > badges, because you do get a sense which version of the package you get on > which version of julia. > > > > *From:* [email protected] <javascript:> [mailto: > [email protected] <javascript:>] *On Behalf Of *Iain Dunning > *Sent:* Wednesday, September 2, 2015 11:21 AM > *To:* [email protected] <javascript:> > *Subject:* Re: [julia-users] FYI: PackageEvaluator/pkg.julialang.org > badge URL change > > > > I'm not sure to be honest. We've never had one badge to aggregate it, I > think it'd be too much to cram into a badge. > > I'm not sure I'll ever test 0.3, 0.4, and 0.5 simultaneously. > > I guess I'll just provide the results, and people can select what they > think is relevant to users. > > > > On Wed, Sep 2, 2015 at 2:11 PM, David Anthoff <[email protected] > <javascript:>> wrote: > > Is the idea that we have a separate badge for every julia version now, > i.e. very soon three? Or is there also one badge that shows the aggregated > information? > > > > *From:* [email protected] <javascript:> [mailto: > [email protected] <javascript:>] *On Behalf Of *Iain Dunning > *Sent:* Wednesday, September 2, 2015 12:47 AM > *To:* julia-users <[email protected] <javascript:>> > *Subject:* [julia-users] FYI: PackageEvaluator/pkg.julialang.org badge > URL change > > > > Hi all, > > > > In an effort to prepare for a reality where Julia 0.3, 0.4, and 0.5-dev > will all be in the wild simultaneously, I had to change the > PackageEvaluator badge URL scheme. I also took the opportunity to change > the badge design to be more informative about what its showing exactly. > > > > I've fixed about ~100 package READMEs, but there will be many more out > there. > > To fix your README, or to add the badges, simply look up you package on > pkg.julialang.org and click "Get permalink/badge" for the Markdown. Your > badge may still work, depending on when you last updated it, but the link > will almost surely be out-of-date (but won't give a 404). > > > > What is PackageEvaluator, you may ask? See > https://github.com/IainNZ/PackageEvaluator.jl for more info. > > > > Thanks, > Iain > > > > PS: we're not far from 700 registered packages! > > > > > > -- > > *Iain Dunning* > > PhD Candidate > <http://orc.scripts.mit.edu/people/student.php?name=idunning> / MIT > Operations Research Center <http://web.mit.edu/orc/www/> > > http://iaindunning.com / http://juliaopt.org >
