[Gluster-Maintainers] [Gluster-devel] Release 5: Branched and further dates
ravishankar at redhat.com
Mon Oct 8 11:25:56 UTC 2018
On 10/05/2018 08:29 PM, Shyam Ranganathan wrote:
> On 10/04/2018 11:33 AM, Shyam Ranganathan wrote:
>> On 09/13/2018 11:10 AM, Shyam Ranganathan wrote:
>>> RC1 would be around 24th of Sep. with final release tagging around 1st
>>> of Oct.
>> RC1 now stands to be tagged tomorrow, and patches that are being
>> targeted for a back port include,
> We still are awaiting release notes (other than the bugs section) to be
> There is one new bug that needs attention from the replicate team.
> The above looks important to me to be fixed before the release, @ravi or
> @pranith can you take a look?
I've attempted a fix @ https://review.gluster.org/#/c/glusterfs/+/21366/
>> 1) https://review.gluster.org/c/glusterfs/+/21314 (snapshot volfile in
>> mux cases)
>> @RaBhat working on this.
>> 2) Py3 corrections in master
>> @Kotresh are all changes made to master backported to release-5 (may not
>> be merged, but looking at if they are backported and ready for merge)?
> Done, release notes amend pending
>> 3) Release notes review and updates with GD2 content pending
>> @Kaushal/GD2 team can we get the updates as required?
> Still awaiting this.
>> 4) This bug  was filed when we released 4.0.
>> The issue has not bitten us in 4.0 or in 4.1 (yet!) (i.e the options
>> missing and hence post-upgrade clients failing the mount). This is
>> possibly the last chance to fix it.
>> Glusterd and protocol maintainers, can you chime in, if this bug needs
>> to be and can be fixed? (thanks to @anoopcs for pointing it out to me)
> Release notes to be corrected to call this out.
>> The tracker bug  does not have any other blockers against it, hence
>> assuming we are not tracking/waiting on anything other than the set above.
>>  Tracker: https://bugzilla.redhat.com/show_bug.cgi?id=glusterfs-5.0
>>  Potential upgrade bug:
>> maintainers mailing list
>> maintainers at gluster.org
More information about the maintainers