On 06.12.2013 09:25, Togan Muftuoglu wrote:

Hi,

...

...

...

...

...

"Stephan" == Stephan Kulow writes:

Stephan> Hi, Stephan> I'm in the process of replacing Hermes mails by built in OBS Stephan> notifications and to avoid any surprises on your side: here is an Stephan> example mail in case you want to prepare your mail filters - or Stephan> have other wishes on their headers (or content). I basically tried Stephan> to mimic what bugzilla adds in the mail headers.

Precdence is misspelled, it should be Precedence: Thanks.

what are the X-OBS-event-types other than "review_wanted"

These are the current types: branch_command build_fail build_success comment_for_package comment_for_project comment_for_request commit create_package create_project delete_package delete_project request_change request_create request_delete request_statechange review_wanted update_package update_project_config update_project upload version_change

Stephan> It will be possible to disable notifications in OBS, but we're Stephan> not sure yet how and when it will be ready. So I will roll this Stephan> out very slowly :)

Will there be digest option as in the Hermes, ie send mails every x hours/days also

No. So far no one could name a reasoning for having them that wasn't better suited with having summary emails. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

On 06.12.2013 13:59, Robert Schweikert wrote:

On 12/06/2013 03:13 AM, Stephan Kulow wrote:

...

Hi,

I'm in the process of replacing Hermes mails by built in OBS notifications and to avoid any surprises on your side: here is an example mail in case you want to prepare your mail filters - or have other wishes on their headers (or content). I basically tried to mimic what bugzilla adds in the mail headers.

I take it this will be used for Devel projects as well. I think it would This is used for all reviews, e.g. GNOME project reviewers will get the same mails.

be great to have the project in the subject. For those that are project maintainers in multiple projects I think that is useful. Requests can have several target projects. Just as they can several types. I add all actions and their targets in the mail headers though, but I don't want anything action specific in the subject, because it's just not logic.

Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org

Am 06.12.2013 22:55, schrieb Christian Boltz:

Hello,

Am Freitag, 6. Dezember 2013 schrieb Stephan Kulow:

...

On 06.12.2013 13:59, Robert Schweikert wrote:

...

...

be great to have the project in the subject. For those that are project maintainers in multiple projects I think that is useful.

Requests can have several target projects. Just as they can several types. I add all actions and their targets in the mail headers though, but I don't want anything action specific in the subject, because it's just not logic.

Nevertheless, I'd guess most requests are about one package and one target - and for those it would be very helpful to have a meaningful subject with target project and package.

If a SR includes multiple packages (in the same target project), only add the target project to the subject.

And in case the SR delivers to 20 packages in 10 projects - well, then I'm ok with excluding them from the subject ;-)

An even better alternative would be to include only the first target, and prefix it with "10 targets, for example $first_target".

TL;DR summary:

"Subject: Request 123456: Review wanted" is about as helpful as "Subject: HELP !!!!!!111!!!" in a mailinglist ;-)

Then again, "Request 123456 (10 targets for example devel:languages:ruby:extensions/rubygem-activerecord-3_2), review wanted" is quite a long 'summary' :) The summary should "indicate the nature of the mail", not give away its content, but yeah, I agree that optimizing for the normal case of one target is feasible. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org