Change Details

**Motivation** We want to avoid broken installations of wikibase-docker due to changes to wikidata-query-gui (e.g {T227031}). **Problem** Currently, we are pulling wikidata-query-gui master as part of building `latest` image of `wdqs-frontend` in our wikibase-docker bundle (check https://github.com/wmde/wikibase-docker/blob/master/wdqs-frontend/latest/Dockerfile#L7). If wikidata-query-gui changes in any incompatible way with the current configuration we supply as part of building this image, as seen in {T227031}, then the resulting image might end up being broken. **Suggested Solution** On the first day of each month take the current "latest" image, and release it tagged as YYYY-MM. This is not going to guarantee there are no broken images, but at least there will be a possible downgrade/upgrade path available for people using the image. **AC** [ ] There is a script which creates a new folder in the github repository, named YYYY-MM at the beginning of each month. [ ] There is a script that adds a docker file which builds Query Service UI from the most recent commit available at the start of the month, and when pushed by Travis should be tagged with YYYY-MM on docker hub, [ ] The scripts generating the above should be run monthly on CI server [ ] Readme should be changed to contain a note that only 6 most recent monthly "versions" of Query Service UI code are built and updated.

**Motivation** We want to avoid broken installations using the wikibase docker images due to changes to wikidata-query-gui (e.g {T227031}). **Problem** Currently, we are pulling wikidata-query-gui master as part of building `latest` and `legacy` image of `wdqs-frontend` in our wikibase-docker bundle (check https://github.com/wmde/wikibase-docker/blob/master/wdqs-frontend/latest/Dockerfile#L7). If wikidata-query-gui changes in any incompatible way with the current configuration we supply as part of building this image, as seen in {T227031}, then the resulting image might end up being broken. **Suggested Solution** On the first day of each month, or whenever a significant change is made, take the current "latest" and "legacy" images, and release it tagged as YYYY-MM using a specific commit hash in the Dockerfile instead of master. This is not going to guarantee there are no broken images, but at least there will be a possible downgrade/upgrade path available for people using the image. **AC** [ ] There is an initial tag for November 2019 for both the latest and legacy images [ ] There is a script which creates a new folder with appropriate Dockerfile in the github repository, named YYYY-MM for the month the script is being run. [ ] Readme should be changed to contain a note that only 3 most recent monthly "versions" of Query Service UI code are built and updated.

**Motivation** We want to avoid broken installations ofusing the wikibase- docker images due to changes to wikidata-query-gui (e.g {T227031}). **Problem** Currently, we are pulling wikidata-query-gui master as part of building `latest` and `legacy` image of `wdqs-frontend` in our wikibase-docker bundle (check https://github.com/wmde/wikibase-docker/blob/master/wdqs-frontend/latest/Dockerfile#L7). If wikidata-query-gui changes in any incompatible way with the current configuration we supply as part of building this image, as seen in {T227031}, then the resulting image might end up being broken. **Suggested Solution** On the first day of each month, or whenever a significant change is made, take the current "latest" and "legacy" images, and release it tagged as YYYY-MM using a specific commit hash in the Dockerfile instead of master. This is not going to guarantee there are no broken images, but at least there will be a possible downgrade/upgrade path available for people using the image. **AC** [ ] There is a script which creates a new folder in the github repository, named YYYY-MM atn initial tag for November 2019 for both the beginning of each month.latest and legacy images [ ] There is a script that adds a docker file which builds Query Service UI from the most recent commit available atwhich creates a new folder with appropriate Dockerfile in the start of the monthgithub repository, and when pushed by Travis should be tagged with YYYY-MM on docker hub,named YYYY-MM for the month the script is being run. [ ] The scripts generating the above should be run monthly on CI server [ ] Readme should be changed to contain a note that only 63 most recent monthly "versions" of Query Service UI code are built and updated.