<div dir="ltr"><div>Thanks for closing out this thread/topic, Lubos. That is a helpful practice.</div><div><br></div><div>Given Ina's input, I see that as a concern, because best practice for bugs is to have a title or description of the behavior that is a problem and NOT the solution so that they can easily be found by others experiencing the same bug. Whereas with features, it is best to have a title or description of new behavior being added. So I can see that this would make it hard to standardize practices here.</div><br clear="all"><div><div dir="ltr" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>
<p style="font-weight:bold;margin:0px;padding:0px;font-size:14px;font-family:"RedHatText",sans-serif">
<span>Robin</span> <span>Chan</span><span style="color:rgb(170,170,170);margin:0px"></span>
</p>
<p style="font-weight:normal;font-size:12px;margin:0px 0px 4px;text-transform:capitalize;font-family:"RedHatText",sans-serif">She/Her/Hers</p>
<p style="font-weight:normal;font-size:12px;margin:0px;font-family:"RedHatText",sans-serif">
<span>Satellite Software Engineering Manager - Pulp</span>
</p>
<p style="font-weight:normal;margin:0px 0px 4px;font-size:12px;font-family:"RedHatText",sans-serif">
<a style="color:rgb(0,136,206);font-size:12px;margin:0px;text-decoration:none;font-family:"RedHatText",sans-serif" href="https://www.redhat.com" target="_blank">Red Hat <span></span></a>
</p>
<div style="margin-bottom:4px">
</div>
<p style="font-weight:normal;margin:0px;font-size:12px;font-family:"RedHatText",sans-serif">
<span>IRC: <span>rchan</span></span>
</p>
<div style="margin-top:12px">
<table border="0">
<tbody><tr>
<td width="100px"><a href="https://www.redhat.com" target="_blank"> <img src="https://static.redhat.com/libs/redhat/brand-assets/2/corp/logo--200.png" width="90" height="auto"></a> </td>
</tr>
</tbody></table>
</div>
</div><div><br></div></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Feb 28, 2020 at 6:04 AM Lubos Mjachky <<a href="mailto:lmjachky@redhat.com" target="_blank">lmjachky@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">No inputs have been received for a week. Therefore, the changelog conventions should remain the same. That is, basically, no rules, and no conventions at all. I will continue using past simple on my own.</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Feb 17, 2020 at 5:31 PM Ina Panova <<a href="mailto:ipanova@redhat.com" target="_blank">ipanova@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div>Thank you for starting this thread.</div><div><br></div><div>The format of the changelog is different because the usual practice is to re-use the title of the issue/story/task/refactor.</div><div><br></div><div>If we want to create some standards than maybe we should start with the titles from redmine.<br></div><div dir="ltr"><br>--------<br>Regards,<br><br>Ina Panova<br>Senior Software Engineer| Pulp| Red Hat Inc.<br><br>"Do not go where the path may lead,<br> go instead where there is no path and leave a trail."<br></div><div><div><br></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Feb 17, 2020 at 4:55 PM Lubos Mjachky <<a href="mailto:lmjachky@redhat.com" target="_blank">lmjachky@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Dear colleagues,<div><br></div><div>I have recently noticed that our changelog often contains non-uniform messages informing about particular changes.</div><div><br></div><div>For instance, take a look at the changelogs in pulp_container (<a href="https://pulp-container.readthedocs.io/en/latest/changes.html" target="_blank">https://pulp-container.readthedocs.io/en/latest/changes.html</a>) or pulpcore (<a href="https://docs.pulpproject.org/en/master/nightly/changes.html" target="_blank">https://docs.pulpproject.org/en/master/nightly/changes.html</a>):</div>1. As a user I can manage images in OCI format.<br>2. Let users fetch the list of all distributed repositories via the _catalog endpoint.<br>3. Adds ability to build OCI images from Containerfiles. <br>4. Added v2s2 to v2s1 converter.<div>5. Allow administrators to add a signing service.</div><div>6. Files stored on S3 and Azure now download with the correct filename.<br><div><br></div><div>As you can see, we are using there random tenses and sentence structures. I am in favor of establishing one feasible convention for all changelog messages. We should strive to use only one tense, e.g. past simple. Then, the messages would rather look like this [0]:</div><div>1. Removed the filter for the field 'digest'.</div><div>2. Added support for mirror mode.</div><div><br></div><div>Please feel free to support this idea or raise any concerns. If we reach a viable consensus I will create a PR which will add a note about acceptable changelog messages to the corresponding section here <a href="https://docs.pulpproject.org/en/master/nightly/contributing/git.html#changelog-update" target="_blank">https://docs.pulpproject.org/en/master/nightly/contributing/git.html#changelog-update</a>. Thank you in advance.</div><div><br></div><div>[0] <a href="https://keepachangelog.com/en/1.0.0/#how" target="_blank">https://keepachangelog.com/en/1.0.0/#how</a></div></div></div>
_______________________________________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br>
</blockquote></div>
</blockquote></div>
_______________________________________________<br>
Pulp-dev mailing list<br>
<a href="mailto:Pulp-dev@redhat.com" target="_blank">Pulp-dev@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/pulp-dev" rel="noreferrer" target="_blank">https://www.redhat.com/mailman/listinfo/pulp-dev</a><br>
</blockquote></div>