It would be useful if patchwork were able to send out emails to the patch submitter when the status of the patch changed; in particular it's useful to know when a patch gets merged. I think we'd start by making this opt-in through patchwork, once we get it working we can at least have the system send out an automatic email to first-time submitters telling them how to enable it, assuming we don't make it opt-out.
Sounds useful indeed. Filed an issue on my side: https://github.com/dlespiau/patchwork/issues/60
We'd also want to see updates when the patch goes into the staging branch(es) - see bug 10715.
I think this bug can be reconsidered now that patchwork is working. I think it is useful to receive these notifications. Sending it back to triage.
We discussed Patchwork notifications in "[OE-core] Patchwork not picking changes from the ML" and there seems to be a consensus that Patchwork should send a confirmation for each new patch series (or, if just a single patch, for that patch) to the mailing list and the patch submitter. The confirmation should include the URL of the Patchwork entry. If the submitter has disable email notifications, that should suppress the email to the submitter, but not the mailing list (new requirement, not discussed on the list). The rationale was: * submitters not aware of Patchwork are notified where they can track patch status * everyone gets a confirmation that the process is working
Feature implementation in production has been queued and will be completed in M3, so I'm moving this bug accordingly.
The server configuration required for the requested email-notifications feature to be available is still in queue for implementation, although higher priority items are being handled before. I'm moving this request to the next enhancements-allowed milestone.
Following are the required configurations at the OE-Patchwork host server that are still pending to be applied: 1- Edit the Patchwork settings file (should be <patchwork-dir>/patchwork/settings.production.py) with the following values or what makes more sense for the server: EMAIL_HOST = os.getenv('EMAIL_HOST', 'localhost') EMAIL_PORT = os.getenv('EMAIL_PORT', 25) EMAIL_HOST_USER = os.getenv('EMAIL_HOST_USER', '') EMAIL_HOST_PASSWORD = os.getenv('EMAIL_HOST_PASSWORD', '') EMAIL_USE_TLS = False DEFAULT_FROM_EMAIL = 'Patchwork <patchwork@patchwork.openembedded.org>' SERVER_EMAIL = DEFAULT_FROM_EMAIL NOTIFICATION_FROM_EMAIL = DEFAULT_FROM_EMAIL *Comment the EMAIL_BACKEND line if available 2- Configure the Patchwork cron job at the server's crontab. Patchwork has a default "NOTIFICATION_DELAY_MINUTES" value of 10 minutes, and the cron job should be set to the same value. However, this may be too much. It could be set as NOTIFICATION_DELAY_MINUTES = 30 in the settings file (same as in previous step) and in the crontab something like: # m h dom mon dow command */30 * * * * cd patchwork; python3 ./manage.py cron 3- Enable "send notifications" at each project's django administration view. I suggest to first enable the notification only for OE-core project and see how it goes for a couple days before replicating to other projects.
Amanda - could you try what Jose suggested and see how well it works?
looking into this.
Bulk move from 4.99 or 0.00 to 5.99