[Dev] Proper SR Comments for OBS

Kanevskiy, Alexander alexander.kanevskiy at intel.com
Thu Oct 24 15:59:41 GMT 2013

On 10/24/13 10:40 , "Łukasz Stelmach" <l.stelmach at samsung.com> wrote:

Backend service exposing content of annotation for submit tag to SR.


Submitter: Rusty Lynch <rusty.lynch at intel.com>
Comments: Add a build config option for turning on journal logging
Git project: platform/core/system/dlog
Tag: submit/tizen/20131024.153312
Commit: ac126309162b9bd470402571d7b7030dc3111d8c Update changelog

$ git show submit/tizen/20131024.153312
tag submit/tizen/20131024.153312
Tagger: Rusty Lynch <rusty.lynch at intel.com>
Date:   Thu Oct 24 08:33:12 2013 -0700

Add a build config option for turning on journal logging

commit ac126309162b9bd470402571d7b7030dc3111d8c

So, as soon as maintainers put some meaningful comment into submit, it
will be visible for release engineers.

>It was <2013-10-23 śro 10:03>, when ANUJ MISHRA wrote:
>> Dear Package Maintainers,
>> Once you raise the SR, you should add proper & meaningful comment to
>> identify the changes. Comment should reflect the purpose
>> correctly. This would help Release Engineer to identify criticality
>> and reason of each SR in OBS.
>> For many of the SR Release Engineer cannot identify the purpose and he
>> has to contact individually or trackback to identify the purpose.
>> Going forward, if SR comment is not meaningful, I would suggest
>> Release Engineer to reject those SR immediately.
>According to [1] the submission should contain updates to the changlog.
>Let's make those changes visible as SR comment.
>Łukasz Stelmach
>Samsung R&D Institute Poland
>Samsung Electronics

Best regards, Alexander Kanevskiy.

Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki 
Business Identity Code: 0357606 - 4 
Domiciled in Helsinki 

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

More information about the Dev mailing list