Update changelog and changelog tool for v2.2.0#2043
Conversation
|
@jvegasbsc dude, what age was the base branch you used for this? This looks like it's from 1953 🤣 |
valeriupredoi
left a comment
valeriupredoi
left a comment
There was a problem hiding this comment.
Javi man, please modernize the base branch that you use, this is before the Gulf War (first one from 1991) - we froze the code today, so grab the state of master from a75326e or something like that 👍
…to update_release_notes_tool
This was started before the core release |
|
By thw way, I have not gone through the actual changelog, so please start reviewing only the tests and the draft tool. |
|
yeah no probs, the changelog we can go through it together next week, cheers for modernizing it 😁 |
bouweandela
left a comment
bouweandela
left a comment
There was a problem hiding this comment.
Looks good to me, could you also update the documentation on the release notes tool? https://docs.esmvaltool.org/en/latest/utils.html#draft-release-notes-py
|
Changelog ready! |
valeriupredoi
left a comment
valeriupredoi
left a comment
There was a problem hiding this comment.
nice work @jvegasbsc 🍺 Did you want to add the Highlights as well as you did for the Core release or is it too pretentious given that in Tool we shouldn't be too boasty about some changes and keep others as "normal"
|
I added the note about Iris 3. I think we do not have any other big thing for the tool |
|
cool, that should do it 👍 |
* Small changes in the release notes tools * Updated changelog and changelog tool * use 21st century environment file * use 21st century setup file * Fix some codacy issues * Small refactor * Final version of changelog * Add highlights * Add last commit changelog and update tool doc * Update doc Co-authored-by: Valeriu Predoi <valeriu.predoi@gmail.com>
3 participants
This PR updates the changelog for v2.2.0
It also containes some updates to the script that generates the draft of the release notes and a new test to check if there are duplicated entries in the changelog
Before you get started
Checklist
It is the responsibility of the author to make sure the PR is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.
pre-commitoryamllintchecksTo help with the number pull requests: