|
| 1 | +# Maintainers’ Guide |
| 2 | + |
| 3 | +This guide is meant for the maintainers of this repository and it is about |
| 4 | +releasing new versions of ASP.NET Docker Image for each release. |
| 5 | + |
| 6 | +## Releasing a New Version |
| 7 | + |
| 8 | +> **NOTE:** It is recommended to do the following steps on a Mac/Linux machine as |
| 9 | +some of the steps rely on symbolic links who does not properly work with |
| 10 | +Git on Windows. |
| 11 | + |
| 12 | +#### Step 1: New folder and Dockerfile |
| 13 | + |
| 14 | +Create a new folder at the root with the image name and place the Dockerfile |
| 15 | +updated over there. |
| 16 | + |
| 17 | +We store all images in `master` branch (without tags) and this enables |
| 18 | +us to maintain all versions at the same time easily. |
| 19 | + |
| 20 | +Example: |
| 21 | + |
| 22 | + mkdir 1.0.0-beta6 |
| 23 | + |
| 24 | +#### Step 2: Move README |
| 25 | + |
| 26 | +README.md is the file that is shown as the Docker Image description on |
| 27 | +the Docker Hub page of the image. However Docker Hub has a bug (by design) |
| 28 | +and requires README.md to be next to a Dockerfile that gets built. |
| 29 | + |
| 30 | +In order to achieve that we keep the README.md right next to the latest |
| 31 | +Dockerfile and update the symbolic link (also called README.md) to this |
| 32 | +file, this enables image description to show up on GitHub properly as well. |
| 33 | + |
| 34 | +Move README.md that lives in the latest image to this folder and update |
| 35 | +the symlink. |
| 36 | + |
| 37 | + mv 1.0.0-beta5/README.md 1.0.0-beta6 |
| 38 | + unlink README.md |
| 39 | + ln -s 1.0.0-beta6/README.md README.md |
| 40 | + |
| 41 | +#### Step 3: Update README |
| 42 | + |
| 43 | +Update the relevant sections of `README.md` to reflect the latest version. |
| 44 | + |
| 45 | +#### Step 4: Create a pull request |
| 46 | + |
| 47 | +Do not directly push to `aspnet/aspnet-docker` repo. All commits must come |
| 48 | +through GitHub pull requests and should be merged from the GitHub web UI. |
| 49 | + |
| 50 | +#### Step 5: Update Docker Hub |
| 51 | + |
| 52 | +Once the image is merged, it does not normally show up on Docker Hub because |
| 53 | +the `latest` tag is not pointing to the folder of the new version. |
| 54 | + |
| 55 | +Someone with the admin privileges on Microsoft organization on Docker Hub |
| 56 | +must go to the Automated Build Settings of the repository and add the new |
| 57 | +tag to the list and update the `latest` tag to point to this new folder as well. |
| 58 | + |
| 59 | +Once the tags are updated, the automated build will be kicked off for all the |
| 60 | +image tags, go to the Build Details page of the image to watch the results. |
0 commit comments