Link to mailing list archives.
parent
7ee6b612f7
commit
5e3aa62d3e
|
@ -5,7 +5,7 @@ The easiest way to get help with the project is to join the ``#readthedocs``
|
|||
channel on Freenode_. We hang out there and you can get real-time help with
|
||||
your projects. The other good way is to open an issue on Github_.
|
||||
|
||||
The mailing list at readthedocs@librelist.org is also available for support.
|
||||
The mailing list at `readthedocs@librelist.org`_ is also available for support.
|
||||
|
||||
.. _Freenode: irc://freenode.net/
|
||||
.. _Github: http://github.com/rtfd/readthedocs.org/issues
|
||||
|
@ -14,7 +14,9 @@ Backwards Incompatible Changes
|
|||
==============================
|
||||
|
||||
Backwards Incompatible Changes will be emailed to the mailing list,
|
||||
readthedocs@librelist.org. They will be prefixed with "Backwards Incompatible
|
||||
Changes". We are thinking about having some kind of Backwards Incompatible
|
||||
Changes policy, much like the 1.0 of a code base, once we define the redirects
|
||||
and interfaces that we wish to expose permanently.
|
||||
`readthedocs@librelist.org`_. They will be prefixed with "Backwards
|
||||
Incompatible Changes". We are thinking about having some kind of Backwards
|
||||
Incompatible Changes policy, much like the 1.0 of a code base, once we define
|
||||
the redirects and interfaces that we wish to expose permanently.
|
||||
|
||||
.. _readthedocs@librelist.org: http://librelist.com/browser/readthedocs/
|
||||
|
|
Loading…
Reference in New Issue