-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
File name made more understandable #17021
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
File name made more understandable #17021
Conversation
…o file_name_made_more_understandable
@anntzer @story645 @tacaswell kindly review this pr |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we put the explicit number all over the docs, this will get outdated as I don‘t think it will be updated consistently.
I‘d go for using „the most recent api_changes_X.Y“ or a similar term.
I think "recent api_changes_X.Y“ is explanatory enough. We don't need "the
most". What do you think?
…On Sat, 4 Apr 2020, 4:26 am Tim Hoffmann, ***@***.***> wrote:
***@***.**** commented on this pull request.
If we put the explicit number all over the docs, this will get outdated as
I don‘t think it will be updated consistently.
I‘d go for using „the most recent api_changes_X.Y“ or a similar term.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#17021 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFAAEQ5PKOYQENYX6IBPQHDRKZSTRANCNFSM4L4PSFNA>
.
|
Fine by me. |
@timhoffm I think I am missing something very crucial due to which majority of CI are failing. I have pushed the changes. Trying to debug the failing CIs. Any help appreciated. |
CircleCI shows
Do I need to upload any output files too? Maybe for the test outputs? |
You can download the log file and look for "warnings". Here you'll find
which means that you forgot to edit doc/api/api_changes.rst, and therefore the moved files are not referenced anywhere. |
Thanks for the help. |
I am skeptical of this change, it may make it slightly clearer but it is going to require a whole bunch of places to be updated after we fork off v3.3.x and 3.4 becomes the "next" release. |
Ping @tacaswell this has only one explicit filename left (and it's in the toc). Do you think this is bearable? |
Yes, that seems OK. |
Can we merge it? If it is ok?
Thanks all for helping 😊
…On Mon, 6 Apr 2020, 6:49 pm Thomas A Caswell, ***@***.***> wrote:
Yes, that seems OK.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#17021 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AFAAEQ4627YTRIMEDH2U4ZLRLHJH3ANCNFSM4L4PSFNA>
.
|
There are conflicts. Resolving them now |
34c6e1c
to
91920e4
Compare
…o file_name_made_more_understandable
Resolved. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some typos to fix.
Co-Authored-By: Elliott Sales de Andrade <[email protected]>
Co-Authored-By: Elliott Sales de Andrade <[email protected]>
Done. Thanks |
PR Summary
Putting an actual version number on the next_api_changes directory may help avoiding notes going to the wrong file during long RC periods where it's not so obvious whether next_api_changes refers to the currently rc'd release, or the next one.
Closes #16588
PR Checklist