New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Copy modified blurbs to idlelib/NEWS.txt for 3.7.0 #75111
Comments
As I prepare blurbs, I copy to a private file, replacing 'IDLE' with bpo-nnnnn. And maybe edit a bit more, maybe not. I occasionally copy batches to idlelib/NEWS.txt. The first 2 times with git, I marked PR as trivial, but decided to open this continuing issue to record merges. A script could be written to do this automatically, but it would have to be run just before the blurbs are moved into Python's NEWS. |
Backport of 2703 is 2704, which has been merged. Somehow bpo# on title got stripped and I did not notice until merged, and merge was allowed without trivial tag. NOTE: THE DOUBLE SPACING AFTER THE SEPARATOR LINE IS INTENTIONAL, to avoid backport merge conflicts. |
Next patch should correct bp0-30723. |
Making the upper merge context be "==================================== " (a line of equals and 2 blanks) has worked great to eliminate backport merge conflicts.) |
This should prepare IDLE for 3.6.3 and 3.7.0a1 cutoff tomorrow morning. |
Add 1 new entry to all 3 versions. There will likely be merge conflicts to be resolved because the lower context is not the same, but this should establish a uniform lower context for the immediate future. |
Correction: entries currently go under "What's New in IDLE 3.7.0" for both master and 3.7 branches. Each "What's New in IDLE 3.x.0" is "since 3.(x-1).0 was released. (We used to not branch off x+1 until the first x.0rc1, instead of at x.0b1, so the overlap was much less.) I will edit to make that explicit. So only 3.6 should have conflicts. |
I plan to start a new issue for 3.8.0 when 3.7.0rc1 is released and 'What's new in 3.8.0 (since 3.7.0)' is added to master. IDLE PRs after rc1 that are not an emergency fix will go into 3.7.1 |
I was looking for a way to link to a message in the context of an issue rather that on a page by itself. Neither worked. |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: