Hello,
likely everyone on sr-dev likely noticed the rather large amount of github-actions notifications related to opened issues and pull requests, they happened because of trying to automatise/optimize tasks related to them and somehow keep both reporters and interested developers aware of items ageing. Enabling that action to see how it goes with it triggered rather large amount of notifications, because it worked also on existing items, not only on the future ones.
Anyhow, if there is notification that an item is getting too old and nobody has interest on it, then it may be closed after a while, right now is 6 weeks notice of inactivity, plus 2 weeks to react on it -- these values can adjusted of course base on feedback. If there is interest in the item, simply the label stale can be removed.
Cheers, Daniel
Hello,
we probably also might want to inform the users on the sr-users lists about that, as reporting bugs can be some work indeed.
One question related to the process: If the stale label has been removed from a user or developer, will it automatically be added again from the bot after 6 weeks? Or does the bot remember that it was removed and not touch it anymore.
Cheers,
Henning
Hello,
On 08.11.23 10:29, Henning Westerholt wrote:
Hello,
we probably also might want to inform the users on the sr-users lists about that, as reporting bugs can be some work indeed.
One question related to the process: If the stale label has been removed from a user or developer, will it automatically be added again from the bot after 6 weeks? Or does the bot remember that it was removed and not touch it anymore.
Victor did everything here, the rest at the K dev discussed and agreed that it is something good to have, so maybe he can answer with further details. I understood the process (or the github-action settings) is quite flexible, a lot of things can be tuned (e.g., don't close items tagged "bug", change time frames for pre-notice and closing). For your particular question, right now it is re-adding automatically after 6 weeks, which I find it ok. An important aspect is that it counts from the last activity in the item (e.g., comment), not from the moment is opened or the label removed.
A major scope here is to keep the reporters as well as developers engaged somehow, keep their interest active to troubleshoot, provide further details and pursue for a fix or merge.
Cheers, Daniel
Cheers,
Henning
-- Henning Westerholt - https://skalatan.de/blog/ Kamailio services - https://gilawa.com
-----Original Message----- From: Daniel-Constantin Mierla via sr-dev sr-dev@lists.kamailio.org Sent: Mittwoch, 8. November 2023 10:12 To: Kamailio (SER) - Devel Mailing List sr-dev@lists.kamailio.org Cc: Daniel-Constantin Mierla miconda@gmail.com Subject: [sr-dev] Github actions for opened issues and pull requests
Hello,
likely everyone on sr-dev likely noticed the rather large amount of github- actions notifications related to opened issues and pull requests, they happened because of trying to automatise/optimize tasks related to them and somehow keep both reporters and interested developers aware of items ageing. Enabling that action to see how it goes with it triggered rather large amount of notifications, because it worked also on existing items, not only on the future ones.
Anyhow, if there is notification that an item is getting too old and nobody has interest on it, then it may be closed after a while, right now is 6 weeks notice of inactivity, plus 2 weeks to react on it -- these values can adjusted of course base on feedback. If there is interest in the item, simply the label stale can be removed.
Cheers, Daniel
-- Daniel-Constantin Mierla (@ asipto.com) twitter.com/miconda -- linkedin.com/in/miconda Kamailio Consultancy and Development Services
Kamailio (SER) - Development Mailing List To unsubscribe send an email to sr- dev-leave@lists.kamailio.org
-
Daniel-Constantin Mierla -
Henning Westerholt