|Open||MMiller_WMF||T252822 [EPIC] Growth: "add a link" structured task|
|Open||None||T266437 Add a link engineering: backend product specifications|
|Open||None||T261396 Add a link: engineering tasks for initial release|
|Open||kostajh||T265603 Add Link engineering: Link recommendation service setup|
|Open||kostajh||T265893 Add Link engineering: Deployment Pipeline setup|
|Resolved||kostajh||T266110 Add Link engineering: Codehealth integration|
Hi Release-Engineering-Team, @MGerlach and Growth team will be working on implementing the deployment pipeline for https://gerrit.wikimedia.org/r/plugins/gitiles/research/mwaddlink/+/refs/heads/main. It's a python application, and there will be two requirements.txt files, one for building the application with the capability for training a ML model, and the other for a slimmed-down application that handles web requests and queries data dictionaries.
Do you have any preferences on naming for the requirements.txt files, placement in the repo, whether we should use a virtual env in the Docker image building process, or other concerns?