[Dev] Proper SR Comments for OBS

Łukasz Stelmach l.stelmach at samsung.com
Thu Oct 24 07:40:45 GMT 2013


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.

[1] https://wiki.tizen.org/wiki/OSDev/Development_guide#How_to_trigger_submission_to_OBS
-- 
Łukasz Stelmach
Samsung R&D Institute Poland
Samsung Electronics
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 489 bytes
Desc: not available
URL: <http://lists.tizen.org/pipermail/dev/attachments/20131024/ea61e13d/attachment.sig>


More information about the Dev mailing list