Commit a0e91dcc authored by Herman van Rink's avatar Herman van Rink

Create a specific Docker file

parent 6f54bcc1
......@@ -181,6 +181,13 @@ You can then re-upload the new .debs you've generated, using the '-f' (force) fl
After doing that, you can re-run the 'copy' commands to publish the .debs to the appropriate releases.
### 11. Create a specific Docker file
Create a new file like releases/Dockerfile-3.11 in the [dockerfiles]( repo.
Then create a build for it on:
### 11. Publish the release notes widely
Once all this is done and the tarballs are generated, the release notes are published in:
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment