Release Notes Issues not Linked

[tvaught]

The release notes have a nice reference to the issue addressed by each bullet, but they're not linked to the actual issue. In my quick scan, I didn't see an easy way to mark this up in the release notes rst. You can use brute force to do it with something like:

[[[ - Add to_clipboard function to pandas namespace for writing objects to
the system clipboard (#774 <http://github.com/pydata/pandas/issues/774>_) ]]]

If it won't mess up the docs, I can add these links to the rst. But, I wanted to check first to see if this anyone knew of a simpler method or whether this would cause problems with the Sphinx stuff.

Ideas?

[takluyver]

There's a Sphinx extension to do this - we use it for IPython: https://github.com/ipython/ipython/blob/master/docs/sphinxext/github.py

[tvaught]

Ahh, I didn't look far enough. Looks like the prior release notes found in pandas/doc/source/whatsnew/v0.7.0.txt uses the markup GH220_ for example.

I see how the includes work for Sphinx, but I don't see how the v.0.x.x.txt files get put together in the RELEASE.rst? Is this a manual process?

[adamklein]

We've been keeping RELEASE.rst manually and just mention the issues like #xxx ... we've really only take care to cross-link in the whatsnew rst docs, which make it into the html documentation, using the markup you mention -

[ghost]

closed via 145d196