Replies: 2 comments 5 replies
-
What say ye, fellow v3.6.x release buddy @ESadek-MO ? |
Beta Was this translation helpful? Give feedback.
1 reply
-
It can certainly be frustrating! We did make some concessions to this problem - the section numbers, and changing the I know it's not perfect, but I imagined that anything more sophisticated would take some more complex engineering, and I'm mindful of the 80/20 rule. To put it another way: this is time that we could spend on another Iris problem so we'd need to justify that this has greater importance. |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
📰 Custom Issue
As a core dev and recent
iris
release manager, I totally ❤️ the release_do_nothing.py script.It gives me the confidence of getting the release right first time, so as such it's pretty priceless as it makes my job way easier.
However, I tend to not do the release in one sitting, end-to-end, so mid-release and coming back to it, I have to cycle through the
SECTIONS
of the script to get back to where I left off.It would be handy to be able to jump in to the script, starting for a custom
SECTION
e.g., something like this:> python release_do_nothing.py --section 10
Or extending the script so that it locally cached the stage of the release automatically so that you could hop back in seamlessly. If this was attractive as a workflow, I'd imaging that you'd also want a way of clearing/resettomg the cache e.g.,
Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions