search

dart-lang / pub-dev

The pub.dev website
https://pub.dev
BSD 3-Clause "New" or "Revised" License
782 stars 147 forks source link

Mail maintainers when new issues are detected #3582

Open rrousselGit opened 4 years ago

rrousselGit commented 4 years ago

Hello! Sometimes, for any reason, new issues are detected by pub.

These are very useful informations, but it is easy to miss. For example, a property used may get deprecated, or a package may not support the latest version of a dependency.

It would be great if pub could mail maintainers when new issues arise (with potentially a way to manually subscribe/unsubscribe?)

sigurdm commented 4 years ago

Transferring to pub-dev

Ephenodrom commented 4 years ago

Feel free to consider the situation described in this issue : #3179

sigurdm commented 3 weeks ago

This might still be valuable

It's a bit tricky technically to compare with the analysis results of an earlier deployment (not impossible though).

We could probably only detect when a package goes from max points to not max points (because the scoring model might change between releases).

We would need an option for enabling this. Should it be per package or per user? Who should get the mail.

Email sending is also tricky - we could opt for notifications in the web ui.

rrousselGit commented 3 weeks ago

What about sending a mail whenever there's a new unique failing score?
If a new test is added to the scoring model, and it's failing on an existing package, package authors would want to know about it.

Each failed test could be given a unique error code, and we'd send a mail when a new code is detected.

rrousselGit commented 3 weeks ago

Ideally we'd have a way for an admin to subscribe to the score of all of their packages by default.
I'd rather not realise months afterward that I forgot to subscribe to the mailing list of one of my packages.

And we'd also likely ignore mails for deprecated packages.

isoos commented 3 weeks ago

Maybe this could be a weekly email. It could be not just about the changes in the scores but also further insights (usage, likes, downloads...). That way batching of these issues would be together with some possibly uplifting news too :)

rrousselGit commented 3 weeks ago

With a weekly email, I'd be worried that new issues would be lost in the noise. Too much info and too many mail, and folks ignore those mails.

I think there's a lot of value in notifying only when there's a change