Release announcement/update for 3.1 #286
Conversation
announcements/release-3.1.html
Outdated
| <a href="http://docs.astropy.org/en/stable/whatsnew/3.1.html">http://docs.astropy.org/en/stable/whatsnew/3.1.html</a> | ||
| </p> | ||
| <p> | ||
| Note that the Astropy 3.x series only supports Python 3. Python 2 users can continue to use the 2.x series, which will receive bug fixes and support until the Python developers permanently sunset Python 2.7 (scheduled for 2019). |
There was a problem hiding this comment.
Maybe also emphasize that the 2.x series are not receiving new features?
Co-Authored-By: eteq <erik.tollerud@gmail.com>
announcements/release-3.1.html
Outdated
| <ul> | ||
| <li><a href="http://docs.astropy.org" target="_blank">Current Release</a></li> | ||
| <li><a href="http://devdocs.astropy.org/" target="_blank">In Development</a></li> | ||
| <li><a href="https://astropy.readthedocs.io/en/v1.2.2/index.html" target="_blank">v1.2.2</a></li> |
There was a problem hiding this comment.
@eteq - it still has the full dropdown, please change it to the text only 3 options that was discussed in Adrian's PR.
There was a problem hiding this comment.
Yeah, I am still working on this, will push it up along with the other things shortly.
|
@adrn - maybe have a quick look at the updates I made to the dropdown and make sure you're 👍 ? (key point: turns out the dropdowns were mis-matched in a lot of places, but now they are better, since we don't have to worry about updating version numbers any more.) |
|
|
||
| </p> | ||
| <p> | ||
| If you use Astropy directly for your work, or as a dependency to another |
There was a problem hiding this comment.
Why not copy and paste the acknowledgement from the acknowledging and citing page, or link to that?
I agree in spirit, but it's hard to combine that with static web pages, unfortunately... I think this is why PHP was invented 😉. But maybe we can try at some point transitioning to hyde or some similar static site generator? If that's a direction to go, we should probably make an issue... At any rate, I think I've updated this based on your comments, @adrn. |
|
(oops, I screwed things up with a rebase/force push, one moment please) |
these were originally on github but accidentally force-pushed away
Just what it says on the tin... To be merged when the 3.1 builds are all done.