[Gluster-devel] Release 3.11: RC1 is tagged!
srangana at redhat.com
Tue May 23 14:13:11 UTC 2017
On 05/23/2017 09:27 AM, Shyam wrote:
> A note on release notes:
> 1) release-notes are a part of the code repository, hence use gerrit to
> submit your changes to the release notes
Here is an example: https://review.gluster.org/#/c/17372/
> 2) Also, as we use github for features, and most content that would be
> submitted to the release notes would be for features, use the same issue
> # as the code submission to submit the release notes changes as well.
> For example, to submit release notes for "Enhance handleops readdirplus
> operation to return handles along with dirents", use "Updates: #174" in
> the release notes commit message. There is *no* *need* for a BUG
> The advantages of this are that, we can track all submissions for said
> feature from the same issue in github (all submissions refers to
> feature-spec, code, release-notes, documentation changes).
Here is how it gets reflected in the issue:
> 3) If a release-note is being added for a non-feature (say a warning
> about some feature, or that some functionality is still experimental,
> IOW things that do not have github issues), then use a bug for the
> submission as before.
> "Releases are made better together"
> On 05/22/2017 09:37 PM, Shyam wrote:
>> We just finished tagging release 3.11.0 RC1, that contains a few more
>> fixes post 3.11.0 RC0.
>> Packages for the same will be made available soon.
>> *Attention* contributors:
>> - We still are to see any updates to the release-notes , we have a
>> week before the release, please update the release notes appropriately
>> *Attention* all:
>> - Any pending bugs that are critical to the release need to be marked
>> as a blocker against  and we have about a week left to close out
>> these bugs!
>>  Tracker BZ for 3.11.0 blockers:
>>  Release notes:
>> Gluster-devel mailing list
>> Gluster-devel at gluster.org
More information about the Gluster-devel