Github -- due in large part to complex social cues around encouraging public forking in a top-level namespace -- seems to encourage the assumption that developers will track git and add their own local patches, resulting in a significant decrease in upstream-interest in producing stable, formal, documented, tested, trustable releases and release builds.
I hope it does. However, when Clojure switched to github, basically nothing changed. The only difference was that changes showed up immediately instead of having to wait for the cron job that ran git-svn. They still only accept patches as attachments to Jira issues.
So it totally depends on the maintainers attitude. If they are switching because they're tired of everyone bugging them about it, then you probably won't see much change. If they're switching because they see compelling benefits to a process that allows more community involvement, then you might be in luck.