-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Add tag for Alpine 3.10 #401
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
Conversation
Changes: - docker-library/python@d8d2a41: Merge pull request docker-library/python#401 from J0WI/alpine10-tag - docker-library/python@36af208: Add tag for Alpine 3.10 - docker-library/python@e846f9b: Merge pull request docker-library/python#399 from J0WI/alpine10 - docker-library/python@e057559: Add Alpine 3.10 and remove Alpine 3.8 - docker-library/python@1358d77: Update generated README
The issue is closed and PR is merged, but there is no PR about the change to official-images repo yet. How much should we wait? Is it an automated process or someone's responsibility? Edit: I saw this just after i wrote the comment.
It seems that PR was created in no time, but i'm not sure it targets the right repo. |
A PR has not yet been created: |
@J0WI Thanks. So, how does the process work? Is there a trigger for that or someone creates it manually? Also, why do we have docker-library-bot/official-images@bc698b6 this PR and what does it do? |
I don't know why @docker-library-bot haven't submitted the PR so far. They may want to merge #402 first to avoid rebuilding everything twice. |
@J0WI Is it something we can debug? |
Please see https://github.com/docker-library/faq#an-images-source-changed-in-git-now-what to understand the process. |
@tao12345666333 That's the issue. These steps doesn't work right now. We are stuck at step 2. |
@ulgens we can just open a PR for this. docker-library/official-images#6166 |
The bot only creates us some branches and then @tianon or I will go press the pull request button while double checking that the changes make sense (or if there is another PR that could be included soon to reduce image churn for users). Really anyone could press the "new pull request" button there, since they are all based on changes already committed to the individual repos. |
@yosifkit Thanks for the details. I understand the reasoning but "putting updates in Docker Hub" is already a painfuly slow process, and this review - PR process added 3 days to that. Is there any way to make it faster - automated? |
Closes #398