release 2.8.0 blog post #411
Conversation
|
Not complete yet... feel free to edit. |
_posts/2024-11-22-release-2.8.0.md
Outdated
| MDAnalysis thanks [NumFOCUS][] for its continued support as our fiscal sponsor and | ||
| the [Chan Zuckerberg Initiative][] for supporting MDAnalysis under EOSS4 and EOSS5 awards. | ||
|
|
||
| — The MDAnalysis Team |
There was a problem hiding this comment.
This may be up for discussion, but as the guy that has to go through really tedious releases, I was wondering if it would be ok for me to be the person signing off on release things on behalf of the team?
What I mean here is that it's always a major technical undertaking that doesn't get a mention in the notes/changelog because it happens outside the scope of it - so it's multiple FTE days of hidden work unless we don't make it hidden (happy to go with alternative solutions or be completely shot down)
There was a problem hiding this comment.
Fine with me, Whoever does the work.
I added your name and then also linked to the team page , does this look reasonable?
Co-authored-by: Irfan Alibay <[email protected]>
…ub.io into release-2.8.0
orbeckst
force-pushed
the
release-2.8.0
branch
from
ce3462f to
c4beae7
Compare
|
Need to check again that it builds properly and that links are working but content should be ok. |
- all deprecations - links to role list instead of role description - MDAKits with links
IAlibay
left a comment
IAlibay
left a comment
There was a problem hiding this comment.
Adding in a caveat for the lack of python 3.13 support in conda-forge right now.
Co-authored-by: Irfan Alibay <[email protected]>
|
@IAlibay I am putting you in charge of merging. You know when we're done done. |
|
Thanks, I think we can go ahead now :) |
|
We also posted publicly
Internally
|
Blog post with