Dec 14, 2020 - Jan 8, 2021
Report on iteration Dec 14, 2020 — Jan 8, 2021 (includes all issues completed before Jan 11, 2021).
Due to the holidays and planned vacations, we decided to take a long iteration spanning from December 14th to the end of the first week in January.
We spent the majority of the time on maintenance and addressing some technical debt. The CDH website was successfully moved from Research Computing and a MySQL database to its new home on a PUL VM and running on the PUL Postgresql database server. We’re also making progress on CDH web 3.0, which involves the transition (which we’ve decided to call “exodus” to avoid confusion with “migration”) from Mezzanine to Wagtail.
This iteration we also finally successfully addressed the problem in PPA for adding new HathiTrust content. The release was tagged December 22nd, along with a supporting release of parasolr, but rather than deploy an update right before the holidays, it was held. That release will go into production early this iteration.
Demos
- The CDH website v2.8.1 update was largely an infrastructural one, so there is little that is visible to display and we expect and want it to look it exactly as before.
- One visible change: emoji are now supported! See Marina’s post on dates and dating to see the emojis she originally included, which were not supported on the previous version of the site.
Active projects
- CDH_ansible (0 points, 2 issues)
- cdh-ansible (0 points, 2 issues)
- cdh-web (0 points, 7 issues)
- ppa-django (0 points, 1 issue)
Releases
- cdh-web 2.8.1 — Monday Jan 4, 2021
- ppa-django 3.5 — Tuesday Dec 22, 2020
- parasolr 0.6 — Tuesday Dec 22, 2020
Velocity
Development
0 points, 12 issues. Rolling velocity: 5.67
Design
0 points, 0 issues. Rolling velocity: 1.33
Closed issues by project
- CDH_ansible (0 points, 3 issues)
- development (0 points, 3 issues)
- As a developer, I want a record of significant changes to our deploy process so that I can refer to it when creating and updating playbooks. 📖 documentation
- As a deployer, I would like to have the deploy user automatically created when running playbooks, so that required users are managed by the playbook. enhancement
- rename to 'devops' chore, wontfix
- development (0 points, 3 issues)
- cdh-ansible (0 points, 3 issues)
- development (0 points, 3 issues)
- As a developer, I want a record of significant changes to our deploy process so that I can refer to it when creating and updating playbooks. 📖 documentation
- As a deployer, I would like to have the deploy user automatically created when running playbooks, so that required users are managed by the playbook. enhancement
- rename to 'devops' wontfix, chore
- development (0 points, 3 issues)
- cdh-web (0 points, 8 issues)
- development (0 points, 8 issues)
- Create preliminary script with logic to convert mezzanine pages to wagtail pages duplicate, chore
- Include DB diagrams in documentation chore
- new playbook for production deploy to PUL VM chore
- new playbook for qa deploy to PUL VM with postgres chore
- migrate all site data to new PUL hosted instances chore
- test migrating data to PUL postgres instances chore
- test copying uploaded media to new QA machine chore
- set up wagtail chore
- development (0 points, 8 issues)
- ppa-django (0 points, 1 issues)
- development (0 points, 1 issues)