dogpile.core is hosted on `Bitbucket <http://bitbucket.org>`_ - the lead project page is at https://bitbucket.org/zzzeek/dogpile.core. Source
-code is tracked here using `Mercurial <http://mercurial.selenic.com/>`_.
+code is tracked here using Git.
+.. versionchanged:: 0.4.2 Moved source repository to git.
Releases and project status are available on Pypi at http://pypi.python.org/pypi/dogpile.core.
-dogpile.core is developed by `Mike Bayer <http://techspot.zzzeek.org>`_, and is
+dogpile.core is developed by `Mike Bayer <http://techspot.zzzeek.org>`_, and is
loosely associated with the `Pylons Project <http://www.pylonsproject.org/>`_.
As usage of dogpile.core and dogpile.cache increases, it is anticipated that the Pylons mailing list and IRC channel
will become the primary channels for support.
Bugs and feature enhancements to dogpile.core should be reported on the `Bitbucket
-<https://bitbucket.org/zzzeek/dogpile/issues?status=new&status=open>`_. If you're not sure
+<https://bitbucket.org/zzzeek/dogpile/issues?status=new&status=open>`_. If you're not sure
that a particular issue is specific to either dogpile.cache or dogpile.core, posting to the `dogpile.cache issue tracker <https://bitbucket.org/zzzeek/dogpile.cache/issues?status=new&status=open>`_
is likely the better place to post first, but it's not critical either way.