<div dir="ltr"><div><div>Was looking at Milestone in Github: <a href="https://github.com/gluster/glusterfs/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Release+3.11+%28STM%29%22">https://github.com/gluster/glusterfs/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Release+3.11+%28STM%29%22</a><br><br></div>It is still showing many things as open. I see some of them are done for sure. Please feel free to mark them as 'Closed'. Ideal to have commit id (from git log) while closing.<br><br></div>-Amar<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, May 23, 2017 at 7:43 PM, Shyam <span dir="ltr"><<a href="mailto:srangana@redhat.com" target="_blank">srangana@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 05/23/2017 09:27 AM, Shyam wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
A note on release notes:<br>
<br>
1) release-notes are a part of the code repository, hence use gerrit to<br>
submit your changes to the release notes<br>
</blockquote>
<br></span>
Here is an example: <a href="https://review.gluster.org/#/c/17372/" rel="noreferrer" target="_blank">https://review.gluster.org/#/c<wbr>/17372/</a><span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
2) Also, as we use github for features, and most content that would be<br>
submitted to the release notes would be for features, use the same issue<br>
# as the code submission to submit the release notes changes as well.<br>
<br>
For example, to submit release notes for "Enhance handleops readdirplus<br>
operation to return handles along with dirents", use "Updates: #174" in<br>
the release notes commit message. There is *no* *need* for a BUG<br>
<br>
The advantages of this are that, we can track all submissions for said<br>
feature from the same issue in github (all submissions refers to<br>
feature-spec, code, release-notes, documentation changes).<br>
</blockquote>
<br></span>
Here is how it gets reflected in the issue: <a href="https://github.com/gluster/glusterfs/issues/174#issuecomment-303403925" rel="noreferrer" target="_blank">https://github.com/gluster/glu<wbr>sterfs/issues/174#issuecomment<wbr>-303403925</a><div class="HOEnZb"><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
3) If a release-note is being added for a non-feature (say a warning<br>
about some feature, or that some functionality is still experimental,<br>
IOW things that do not have github issues), then use a bug for the<br>
submission as before.<br>
<br>
Thanks,<br>
Shyam<br>
<br>
"Releases are made better together"<br>
<br>
On 05/22/2017 09:37 PM, Shyam wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
We just finished tagging release 3.11.0 RC1, that contains a few more<br>
fixes post 3.11.0 RC0.<br>
<br>
Packages for the same will be made available soon.<br>
<br>
*Attention* contributors:<br>
- We still are to see any updates to the release-notes [2], we have a<br>
week before the release, please update the release notes appropriately<br>
<br>
*Attention* all:<br>
- Any pending bugs that are critical to the release need to be marked<br>
as a blocker against [1] and we have about a week left to close out<br>
these bugs!<br>
<br>
Thanks,<br>
Shyam<br>
<br>
[1] Tracker BZ for 3.11.0 blockers:<br>
<a href="https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-3.11.0" rel="noreferrer" target="_blank">https://bugzilla.redhat.com/sh<wbr>ow_bug.cgi?id=glusterfs-3.11.0</a><br>
<br>
[2] Release notes:<br>
<a href="https://github.com/gluster/glusterfs/blob/release-3.11/doc/release-notes/3.11.0.md" rel="noreferrer" target="_blank">https://github.com/gluster/glu<wbr>sterfs/blob/release-3.11/doc/<wbr>release-notes/3.11.0.md</a><br>
<br>
<br>
______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/gluster-devel</a><br>
</blockquote></blockquote>
______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a><br>
<a href="http://lists.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://lists.gluster.org/mailm<wbr>an/listinfo/gluster-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div>Amar Tumballi (amarts)<br></div></div></div></div></div>
</div>