Aside from checking out the package's master, a glance at the list of open PRs and recent commits usually tells you a lot.
Best, --Tim On Thursday, August 4, 2016 7:23:11 PM CDT Chris Rackauckas wrote: > Not always. Some repos have a dev branch or a v0.5 compatibility branch, > etc. I think that if you're looking to start working on the package, the > first thing to do is get in contact with one of the authors (join the > Gitter channel if they have one). > > On Thursday, August 4, 2016 at 4:50:55 PM UTC-7, Kristoffer Carlsson wrote: > > I would say that if you want to contribute to a package you should be on > > the latest master commit and work from there. > > > > On Friday, August 5, 2016 at 1:45:46 AM UTC+2, Eric Forgy wrote: > >> I agree. Another consequence of v0.5 updates on master that are not > >> tagged is that newbies, wanting to help, end up fixing things that are > >> already fixed not realizing. I've done this a couple of times and it is > >> frustrating.
