microsoft / microsoft/dotnet-framework-docker
Automate the collection of release data and update the appropriate files
@lbussell is already working on this.
Since Jul 19, 2023.
- Dominant language
- C#
- Stars
- 761
- Forks
- 349
- Avg merge
- 36m
- Merged PRs (30d)
- 1
Description
The hardest part of the release process that is currently manually done is figuring out what needs to be updated in the various infrastructure data files (manifest.versions.json and manifest.datestamps.json) and collecting the data to know what content those files should have.
This consists of the following aspects:
- Collect the KB numbers that are relevant for the release and update them in the
manifest.versions.json. - Collecting the download URLs for those KB numbers on release day when the URLs are live - https://github.com/microsoft/dotnet-framework-docker/pull/1251
- Update
manifest.datestamps.jsonfile for those Dockerfiles that are being updated, and only those Dockerfiles.
We should investigate how all of these aspects can be automated to reduce the burden that is required for the release process.
As a source for the KB info, we use the information from https://aka.ms/TrackIt (internal link). This is based on an API: https://www.osgwiki.com/wiki/WSD_Wiki-DiscoverIt_PLC_Web_API (internal link) that could potentially give us the information we need.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.