Re: [Gluster-Maintainers] [gluster-packaging] glusterfs-5.4 released

[Shyam Ranganathan]

On 3/13/19 10:44 AM, Shyam Ranganathan wrote:
> On 3/13/19 9:09 AM, Kaleb Keithley wrote:
>> The v5.4 tag was made and a release job was run which gave us
>> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz.
>> If the v5.4 tag is moved then there's a logical disconnect between the
>> tag and _that_ tar file, or more accurately the files in that tar file. 
>>
>> Shyam and I discussed the merits of releasing v5.5 versus respinning
>> builds with patches.  Respinning builds with patches isn't uncommon. The
>> difference in the amount of work between one or the other is negligible.
>> In the end Shyam (mainly) decided to go with respinning with patches
>> because a full up "release" for him is a lot more work. (And we both
>> have other $dayjob things we need to be working on instead of endlessly
>> spinning releases and packages.)
> 
> Considering all comments/conversations, I think I will tag a v5.5 with
> the required commits and update the 5.4 release-notes to call it 5.5
> with the added changes.
> 
> Give me a couple of hours :)

Well that took longer (sorry was out sick for some time).

5.4 is now tagged and the release tarball generated for packaging.

> 
>>
>>
>> On Wed, Mar 13, 2019 at 8:52 AM Amar Tumballi Suryanarayan
>> mailto:atumb...@redhat.com>> wrote:
>>
>> I am totally fine with v5.5, my suggestion for moving the tag was if
>> we consider calling 5.4 with these two patches.
>>
>> Calling the release as 5.5 is totally OK, and we call it out
>> specifically in our version numbering scheme, as if something is
>> very serious, we can break 'release date' train.
>>
>> -Amar
>>
>> On Wed, Mar 13, 2019 at 6:13 PM Kaleb Keithley > > wrote:
>>
>> The Version tag should be (considered) immutable. Please don't
>> move it.
>>
>> If you want to add another tag to help us remember this issue
>> that's fine.
>>
>> The other option which Shyam and I discussed was tagging v5.5.
>>
>>
>> On Wed, Mar 13, 2019 at 8:32 AM Amar Tumballi Suryanarayan
>> mailto:atumb...@redhat.com>> wrote:
>>
>> We need to tag different commit may be? So the 'git checkout
>> v5.4' points to the correct commit?
>>
>> On Wed, 13 Mar, 2019, 4:40 PM Shyam Ranganathan,
>> mailto:srang...@redhat.com>> wrote:
>>
>> Niels, Kaleb,
>>
>> We need to respin 5.4 with the 2 additional commits as
>> follows,
>>
>> commit a00953ed212a7071b152c4afccd35b92fa5a682a (HEAD ->
>> release-5,
>>     core: make compute_cksum function op_version compatible
>>
>> commit 8fb4631c65f28dd0a5e0304386efff3c807e64a4
>>     dict: handle STR_OLD data type in xdr conversions
>>
>> As the current build breaks rolling upgrades, we had
>> held back on
>> announcing 5.4 and are now ready with the fixes that can
>> be used to
>> respin 5.4.
>>
>> Let me know if I need to do anything more from my end
>> for help with the
>> packaging.
>>
>> Once the build is ready, we would be testing it out as
>> usual.
>>
>> NOTE: As some users have picked up 5.4 the announce
>> would also carry a
>> notice, that they need to do a downserver upgrade to the
>> latest bits
>> owing to the patches that have landed in addition to the
>> existing content.
>>
>> Thanks,
>> Shyam
>>
>> On 3/5/19 8:59 AM, Shyam Ranganathan wrote:
>> > On 2/27/19 5:19 AM, Niels de Vos wrote:
>> >> On Tue, Feb 26, 2019 at 02:47:30PM +,
>> jenk...@build.gluster.org
>>  wrote:
>> >>> SRC:
>> 
>> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz
>> >>> HASH:
>> 
>> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum
>> >>
>> >> Packages for the CentOS Storage SIG are now available
>> for testing.
>> >> Please try them out and report test results on this list.
>> >>
>> >>   # yum install centos-release-gluster
>> >>   # yum install --enablerepo=centos-gluster5-test
>> glusterfs-server
>> >
>> > Due to patch [1] upgrades are broken, so we are
>> awaiting a fix or revert
>> > of the same before requesting a new build of 5.4.
>> >
>> > The current RPMs should hence not be 

Re: [Gluster-Maintainers] [gluster-packaging] glusterfs-5.4 released

[Shyam Ranganathan]

On 3/13/19 9:09 AM, Kaleb Keithley wrote:
> The v5.4 tag was made and a release job was run which gave us
> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz.
> If the v5.4 tag is moved then there's a logical disconnect between the
> tag and _that_ tar file, or more accurately the files in that tar file. 
> 
> Shyam and I discussed the merits of releasing v5.5 versus respinning
> builds with patches.  Respinning builds with patches isn't uncommon. The
> difference in the amount of work between one or the other is negligible.
> In the end Shyam (mainly) decided to go with respinning with patches
> because a full up "release" for him is a lot more work. (And we both
> have other $dayjob things we need to be working on instead of endlessly
> spinning releases and packages.)

Considering all comments/conversations, I think I will tag a v5.5 with
the required commits and update the 5.4 release-notes to call it 5.5
with the added changes.

Give me a couple of hours :)

> 
> 
> On Wed, Mar 13, 2019 at 8:52 AM Amar Tumballi Suryanarayan
> mailto:atumb...@redhat.com>> wrote:
> 
> I am totally fine with v5.5, my suggestion for moving the tag was if
> we consider calling 5.4 with these two patches.
> 
> Calling the release as 5.5 is totally OK, and we call it out
> specifically in our version numbering scheme, as if something is
> very serious, we can break 'release date' train.
> 
> -Amar
> 
> On Wed, Mar 13, 2019 at 6:13 PM Kaleb Keithley  > wrote:
> 
> The Version tag should be (considered) immutable. Please don't
> move it.
> 
> If you want to add another tag to help us remember this issue
> that's fine.
> 
> The other option which Shyam and I discussed was tagging v5.5.
> 
> 
> On Wed, Mar 13, 2019 at 8:32 AM Amar Tumballi Suryanarayan
> mailto:atumb...@redhat.com>> wrote:
> 
> We need to tag different commit may be? So the 'git checkout
> v5.4' points to the correct commit?
> 
> On Wed, 13 Mar, 2019, 4:40 PM Shyam Ranganathan,
> mailto:srang...@redhat.com>> wrote:
> 
> Niels, Kaleb,
> 
> We need to respin 5.4 with the 2 additional commits as
> follows,
> 
> commit a00953ed212a7071b152c4afccd35b92fa5a682a (HEAD ->
> release-5,
>     core: make compute_cksum function op_version compatible
> 
> commit 8fb4631c65f28dd0a5e0304386efff3c807e64a4
>     dict: handle STR_OLD data type in xdr conversions
> 
> As the current build breaks rolling upgrades, we had
> held back on
> announcing 5.4 and are now ready with the fixes that can
> be used to
> respin 5.4.
> 
> Let me know if I need to do anything more from my end
> for help with the
> packaging.
> 
> Once the build is ready, we would be testing it out as
> usual.
> 
> NOTE: As some users have picked up 5.4 the announce
> would also carry a
> notice, that they need to do a downserver upgrade to the
> latest bits
> owing to the patches that have landed in addition to the
> existing content.
> 
> Thanks,
> Shyam
> 
> On 3/5/19 8:59 AM, Shyam Ranganathan wrote:
> > On 2/27/19 5:19 AM, Niels de Vos wrote:
> >> On Tue, Feb 26, 2019 at 02:47:30PM +,
> jenk...@build.gluster.org
>  wrote:
> >>> SRC:
> 
> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz
> >>> HASH:
> 
> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum
> >>
> >> Packages for the CentOS Storage SIG are now available
> for testing.
> >> Please try them out and report test results on this list.
> >>
> >>   # yum install centos-release-gluster
> >>   # yum install --enablerepo=centos-gluster5-test
> glusterfs-server
> >
> > Due to patch [1] upgrades are broken, so we are
> awaiting a fix or revert
> > of the same before requesting a new build of 5.4.
> >
> > The current RPMs should hence not be published.
> >
> > Sanju/Hari, are we reverting this patch so that we can
> release 5.4, or
> > are we expecting the fix to land in 5.4 (as in [2])?
> >
> > Thanks,
> 

Re: [Gluster-Maintainers] [gluster-packaging] glusterfs-5.4 released

[Kaleb Keithley]

The v5.4 tag was made and a release job was run which gave us
https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz.
If the v5.4 tag is moved then there's a logical disconnect between the tag
and _that_ tar file, or more accurately the files in that tar file.

Shyam and I discussed the merits of releasing v5.5 versus respinning builds
with patches.  Respinning builds with patches isn't uncommon. The
difference in the amount of work between one or the other is negligible. In
the end Shyam (mainly) decided to go with respinning with patches because a
full up "release" for him is a lot more work. (And we both have other
$dayjob things we need to be working on instead of endlessly spinning
releases and packages.)


On Wed, Mar 13, 2019 at 8:52 AM Amar Tumballi Suryanarayan <
atumb...@redhat.com> wrote:

> I am totally fine with v5.5, my suggestion for moving the tag was if we
> consider calling 5.4 with these two patches.
>
> Calling the release as 5.5 is totally OK, and we call it out specifically
> in our version numbering scheme, as if something is very serious, we can
> break 'release date' train.
>
> -Amar
>
> On Wed, Mar 13, 2019 at 6:13 PM Kaleb Keithley 
> wrote:
>
>> The Version tag should be (considered) immutable. Please don't move it.
>>
>> If you want to add another tag to help us remember this issue that's fine.
>>
>> The other option which Shyam and I discussed was tagging v5.5.
>>
>>
>> On Wed, Mar 13, 2019 at 8:32 AM Amar Tumballi Suryanarayan <
>> atumb...@redhat.com> wrote:
>>
>>> We need to tag different commit may be? So the 'git checkout v5.4'
>>> points to the correct commit?
>>>
>>> On Wed, 13 Mar, 2019, 4:40 PM Shyam Ranganathan, 
>>> wrote:
>>>
 Niels, Kaleb,

 We need to respin 5.4 with the 2 additional commits as follows,

 commit a00953ed212a7071b152c4afccd35b92fa5a682a (HEAD -> release-5,
 core: make compute_cksum function op_version compatible

 commit 8fb4631c65f28dd0a5e0304386efff3c807e64a4
 dict: handle STR_OLD data type in xdr conversions

 As the current build breaks rolling upgrades, we had held back on
 announcing 5.4 and are now ready with the fixes that can be used to
 respin 5.4.

 Let me know if I need to do anything more from my end for help with the
 packaging.

 Once the build is ready, we would be testing it out as usual.

 NOTE: As some users have picked up 5.4 the announce would also carry a
 notice, that they need to do a downserver upgrade to the latest bits
 owing to the patches that have landed in addition to the existing
 content.

 Thanks,
 Shyam

 On 3/5/19 8:59 AM, Shyam Ranganathan wrote:
 > On 2/27/19 5:19 AM, Niels de Vos wrote:
 >> On Tue, Feb 26, 2019 at 02:47:30PM +, jenk...@build.gluster.org
 wrote:
 >>> SRC:
 https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz
 >>> HASH:
 https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum
 >>
 >> Packages for the CentOS Storage SIG are now available for testing.
 >> Please try them out and report test results on this list.
 >>
 >>   # yum install centos-release-gluster
 >>   # yum install --enablerepo=centos-gluster5-test glusterfs-server
 >
 > Due to patch [1] upgrades are broken, so we are awaiting a fix or
 revert
 > of the same before requesting a new build of 5.4.
 >
 > The current RPMs should hence not be published.
 >
 > Sanju/Hari, are we reverting this patch so that we can release 5.4, or
 > are we expecting the fix to land in 5.4 (as in [2])?
 >
 > Thanks,
 > Shyam
 >
 > [1] Patch causing regression:
 https://review.gluster.org/c/glusterfs/+/22148
 >
 > [2] Proposed fix on master:
 https://review.gluster.org/c/glusterfs/+/22297/
 > ___
 > maintainers mailing list
 > maintainers@gluster.org
 > https://lists.gluster.org/mailman/listinfo/maintainers
 >
 ___
 maintainers mailing list
 maintainers@gluster.org
 https://lists.gluster.org/mailman/listinfo/maintainers

>>> ___
>>> maintainers mailing list
>>> maintainers@gluster.org
>>> https://lists.gluster.org/mailman/listinfo/maintainers
>>>
>>
>
> --
> Amar Tumballi (amarts)
>
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] [gluster-packaging] glusterfs-5.4 released

[Niels de Vos]

On Wed, Mar 13, 2019 at 08:43:38AM -0400, Kaleb Keithley wrote:
> The Version tag should be (considered) immutable. Please don't move it.
> 
> If you want to add another tag to help us remember this issue that's fine.
> 
> The other option which Shyam and I discussed was tagging v5.5.

v5.5 or a v5.4.1 would have my preference. That also makes it clear for
packagers that build packages for other distributions and the users that
build from the source tarball.

Niels


> 
> 
> On Wed, Mar 13, 2019 at 8:32 AM Amar Tumballi Suryanarayan <
> atumb...@redhat.com> wrote:
> 
> > We need to tag different commit may be? So the 'git checkout v5.4' points
> > to the correct commit?
> >
> > On Wed, 13 Mar, 2019, 4:40 PM Shyam Ranganathan, 
> > wrote:
> >
> >> Niels, Kaleb,
> >>
> >> We need to respin 5.4 with the 2 additional commits as follows,
> >>
> >> commit a00953ed212a7071b152c4afccd35b92fa5a682a (HEAD -> release-5,
> >> core: make compute_cksum function op_version compatible
> >>
> >> commit 8fb4631c65f28dd0a5e0304386efff3c807e64a4
> >> dict: handle STR_OLD data type in xdr conversions
> >>
> >> As the current build breaks rolling upgrades, we had held back on
> >> announcing 5.4 and are now ready with the fixes that can be used to
> >> respin 5.4.
> >>
> >> Let me know if I need to do anything more from my end for help with the
> >> packaging.
> >>
> >> Once the build is ready, we would be testing it out as usual.
> >>
> >> NOTE: As some users have picked up 5.4 the announce would also carry a
> >> notice, that they need to do a downserver upgrade to the latest bits
> >> owing to the patches that have landed in addition to the existing content.
> >>
> >> Thanks,
> >> Shyam
> >>
> >> On 3/5/19 8:59 AM, Shyam Ranganathan wrote:
> >> > On 2/27/19 5:19 AM, Niels de Vos wrote:
> >> >> On Tue, Feb 26, 2019 at 02:47:30PM +, jenk...@build.gluster.org
> >> wrote:
> >> >>> SRC:
> >> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz
> >> >>> HASH:
> >> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum
> >> >>
> >> >> Packages for the CentOS Storage SIG are now available for testing.
> >> >> Please try them out and report test results on this list.
> >> >>
> >> >>   # yum install centos-release-gluster
> >> >>   # yum install --enablerepo=centos-gluster5-test glusterfs-server
> >> >
> >> > Due to patch [1] upgrades are broken, so we are awaiting a fix or revert
> >> > of the same before requesting a new build of 5.4.
> >> >
> >> > The current RPMs should hence not be published.
> >> >
> >> > Sanju/Hari, are we reverting this patch so that we can release 5.4, or
> >> > are we expecting the fix to land in 5.4 (as in [2])?
> >> >
> >> > Thanks,
> >> > Shyam
> >> >
> >> > [1] Patch causing regression:
> >> https://review.gluster.org/c/glusterfs/+/22148
> >> >
> >> > [2] Proposed fix on master:
> >> https://review.gluster.org/c/glusterfs/+/22297/
> >> > ___
> >> > maintainers mailing list
> >> > maintainers@gluster.org
> >> > https://lists.gluster.org/mailman/listinfo/maintainers
> >> >
> >> ___
> >> maintainers mailing list
> >> maintainers@gluster.org
> >> https://lists.gluster.org/mailman/listinfo/maintainers
> >>
> > ___
> > maintainers mailing list
> > maintainers@gluster.org
> > https://lists.gluster.org/mailman/listinfo/maintainers
> >

> ___
> packaging mailing list
> packag...@gluster.org
> https://lists.gluster.org/mailman/listinfo/packaging

___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] [gluster-packaging] glusterfs-5.4 released

[Amar Tumballi Suryanarayan]

I am totally fine with v5.5, my suggestion for moving the tag was if we
consider calling 5.4 with these two patches.

Calling the release as 5.5 is totally OK, and we call it out specifically
in our version numbering scheme, as if something is very serious, we can
break 'release date' train.

-Amar

On Wed, Mar 13, 2019 at 6:13 PM Kaleb Keithley  wrote:

> The Version tag should be (considered) immutable. Please don't move it.
>
> If you want to add another tag to help us remember this issue that's fine.
>
> The other option which Shyam and I discussed was tagging v5.5.
>
>
> On Wed, Mar 13, 2019 at 8:32 AM Amar Tumballi Suryanarayan <
> atumb...@redhat.com> wrote:
>
>> We need to tag different commit may be? So the 'git checkout v5.4' points
>> to the correct commit?
>>
>> On Wed, 13 Mar, 2019, 4:40 PM Shyam Ranganathan, 
>> wrote:
>>
>>> Niels, Kaleb,
>>>
>>> We need to respin 5.4 with the 2 additional commits as follows,
>>>
>>> commit a00953ed212a7071b152c4afccd35b92fa5a682a (HEAD -> release-5,
>>> core: make compute_cksum function op_version compatible
>>>
>>> commit 8fb4631c65f28dd0a5e0304386efff3c807e64a4
>>> dict: handle STR_OLD data type in xdr conversions
>>>
>>> As the current build breaks rolling upgrades, we had held back on
>>> announcing 5.4 and are now ready with the fixes that can be used to
>>> respin 5.4.
>>>
>>> Let me know if I need to do anything more from my end for help with the
>>> packaging.
>>>
>>> Once the build is ready, we would be testing it out as usual.
>>>
>>> NOTE: As some users have picked up 5.4 the announce would also carry a
>>> notice, that they need to do a downserver upgrade to the latest bits
>>> owing to the patches that have landed in addition to the existing
>>> content.
>>>
>>> Thanks,
>>> Shyam
>>>
>>> On 3/5/19 8:59 AM, Shyam Ranganathan wrote:
>>> > On 2/27/19 5:19 AM, Niels de Vos wrote:
>>> >> On Tue, Feb 26, 2019 at 02:47:30PM +, jenk...@build.gluster.org
>>> wrote:
>>> >>> SRC:
>>> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz
>>> >>> HASH:
>>> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum
>>> >>
>>> >> Packages for the CentOS Storage SIG are now available for testing.
>>> >> Please try them out and report test results on this list.
>>> >>
>>> >>   # yum install centos-release-gluster
>>> >>   # yum install --enablerepo=centos-gluster5-test glusterfs-server
>>> >
>>> > Due to patch [1] upgrades are broken, so we are awaiting a fix or
>>> revert
>>> > of the same before requesting a new build of 5.4.
>>> >
>>> > The current RPMs should hence not be published.
>>> >
>>> > Sanju/Hari, are we reverting this patch so that we can release 5.4, or
>>> > are we expecting the fix to land in 5.4 (as in [2])?
>>> >
>>> > Thanks,
>>> > Shyam
>>> >
>>> > [1] Patch causing regression:
>>> https://review.gluster.org/c/glusterfs/+/22148
>>> >
>>> > [2] Proposed fix on master:
>>> https://review.gluster.org/c/glusterfs/+/22297/
>>> > ___
>>> > maintainers mailing list
>>> > maintainers@gluster.org
>>> > https://lists.gluster.org/mailman/listinfo/maintainers
>>> >
>>> ___
>>> maintainers mailing list
>>> maintainers@gluster.org
>>> https://lists.gluster.org/mailman/listinfo/maintainers
>>>
>> ___
>> maintainers mailing list
>> maintainers@gluster.org
>> https://lists.gluster.org/mailman/listinfo/maintainers
>>
>

-- 
Amar Tumballi (amarts)
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] [gluster-packaging] glusterfs-5.4 released

[Kaleb Keithley]

The Version tag should be (considered) immutable. Please don't move it.

If you want to add another tag to help us remember this issue that's fine.

The other option which Shyam and I discussed was tagging v5.5.


On Wed, Mar 13, 2019 at 8:32 AM Amar Tumballi Suryanarayan <
atumb...@redhat.com> wrote:

> We need to tag different commit may be? So the 'git checkout v5.4' points
> to the correct commit?
>
> On Wed, 13 Mar, 2019, 4:40 PM Shyam Ranganathan, 
> wrote:
>
>> Niels, Kaleb,
>>
>> We need to respin 5.4 with the 2 additional commits as follows,
>>
>> commit a00953ed212a7071b152c4afccd35b92fa5a682a (HEAD -> release-5,
>> core: make compute_cksum function op_version compatible
>>
>> commit 8fb4631c65f28dd0a5e0304386efff3c807e64a4
>> dict: handle STR_OLD data type in xdr conversions
>>
>> As the current build breaks rolling upgrades, we had held back on
>> announcing 5.4 and are now ready with the fixes that can be used to
>> respin 5.4.
>>
>> Let me know if I need to do anything more from my end for help with the
>> packaging.
>>
>> Once the build is ready, we would be testing it out as usual.
>>
>> NOTE: As some users have picked up 5.4 the announce would also carry a
>> notice, that they need to do a downserver upgrade to the latest bits
>> owing to the patches that have landed in addition to the existing content.
>>
>> Thanks,
>> Shyam
>>
>> On 3/5/19 8:59 AM, Shyam Ranganathan wrote:
>> > On 2/27/19 5:19 AM, Niels de Vos wrote:
>> >> On Tue, Feb 26, 2019 at 02:47:30PM +, jenk...@build.gluster.org
>> wrote:
>> >>> SRC:
>> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz
>> >>> HASH:
>> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum
>> >>
>> >> Packages for the CentOS Storage SIG are now available for testing.
>> >> Please try them out and report test results on this list.
>> >>
>> >>   # yum install centos-release-gluster
>> >>   # yum install --enablerepo=centos-gluster5-test glusterfs-server
>> >
>> > Due to patch [1] upgrades are broken, so we are awaiting a fix or revert
>> > of the same before requesting a new build of 5.4.
>> >
>> > The current RPMs should hence not be published.
>> >
>> > Sanju/Hari, are we reverting this patch so that we can release 5.4, or
>> > are we expecting the fix to land in 5.4 (as in [2])?
>> >
>> > Thanks,
>> > Shyam
>> >
>> > [1] Patch causing regression:
>> https://review.gluster.org/c/glusterfs/+/22148
>> >
>> > [2] Proposed fix on master:
>> https://review.gluster.org/c/glusterfs/+/22297/
>> > ___
>> > maintainers mailing list
>> > maintainers@gluster.org
>> > https://lists.gluster.org/mailman/listinfo/maintainers
>> >
>> ___
>> maintainers mailing list
>> maintainers@gluster.org
>> https://lists.gluster.org/mailman/listinfo/maintainers
>>
> ___
> maintainers mailing list
> maintainers@gluster.org
> https://lists.gluster.org/mailman/listinfo/maintainers
>
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] [gluster-packaging] glusterfs-5.4 released

[Amar Tumballi Suryanarayan]

We need to tag different commit may be? So the 'git checkout v5.4' points
to the correct commit?

On Wed, 13 Mar, 2019, 4:40 PM Shyam Ranganathan, 
wrote:

> Niels, Kaleb,
>
> We need to respin 5.4 with the 2 additional commits as follows,
>
> commit a00953ed212a7071b152c4afccd35b92fa5a682a (HEAD -> release-5,
> core: make compute_cksum function op_version compatible
>
> commit 8fb4631c65f28dd0a5e0304386efff3c807e64a4
> dict: handle STR_OLD data type in xdr conversions
>
> As the current build breaks rolling upgrades, we had held back on
> announcing 5.4 and are now ready with the fixes that can be used to
> respin 5.4.
>
> Let me know if I need to do anything more from my end for help with the
> packaging.
>
> Once the build is ready, we would be testing it out as usual.
>
> NOTE: As some users have picked up 5.4 the announce would also carry a
> notice, that they need to do a downserver upgrade to the latest bits
> owing to the patches that have landed in addition to the existing content.
>
> Thanks,
> Shyam
>
> On 3/5/19 8:59 AM, Shyam Ranganathan wrote:
> > On 2/27/19 5:19 AM, Niels de Vos wrote:
> >> On Tue, Feb 26, 2019 at 02:47:30PM +, jenk...@build.gluster.org
> wrote:
> >>> SRC:
> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz
> >>> HASH:
> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum
> >>
> >> Packages for the CentOS Storage SIG are now available for testing.
> >> Please try them out and report test results on this list.
> >>
> >>   # yum install centos-release-gluster
> >>   # yum install --enablerepo=centos-gluster5-test glusterfs-server
> >
> > Due to patch [1] upgrades are broken, so we are awaiting a fix or revert
> > of the same before requesting a new build of 5.4.
> >
> > The current RPMs should hence not be published.
> >
> > Sanju/Hari, are we reverting this patch so that we can release 5.4, or
> > are we expecting the fix to land in 5.4 (as in [2])?
> >
> > Thanks,
> > Shyam
> >
> > [1] Patch causing regression:
> https://review.gluster.org/c/glusterfs/+/22148
> >
> > [2] Proposed fix on master:
> https://review.gluster.org/c/glusterfs/+/22297/
> > ___
> > maintainers mailing list
> > maintainers@gluster.org
> > https://lists.gluster.org/mailman/listinfo/maintainers
> >
> ___
> maintainers mailing list
> maintainers@gluster.org
> https://lists.gluster.org/mailman/listinfo/maintainers
>
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] [gluster-packaging] glusterfs-5.4 released

[Shyam Ranganathan]

Niels, Kaleb,

We need to respin 5.4 with the 2 additional commits as follows,

commit a00953ed212a7071b152c4afccd35b92fa5a682a (HEAD -> release-5,
core: make compute_cksum function op_version compatible

commit 8fb4631c65f28dd0a5e0304386efff3c807e64a4
dict: handle STR_OLD data type in xdr conversions

As the current build breaks rolling upgrades, we had held back on
announcing 5.4 and are now ready with the fixes that can be used to
respin 5.4.

Let me know if I need to do anything more from my end for help with the
packaging.

Once the build is ready, we would be testing it out as usual.

NOTE: As some users have picked up 5.4 the announce would also carry a
notice, that they need to do a downserver upgrade to the latest bits
owing to the patches that have landed in addition to the existing content.

Thanks,
Shyam

On 3/5/19 8:59 AM, Shyam Ranganathan wrote:
> On 2/27/19 5:19 AM, Niels de Vos wrote:
>> On Tue, Feb 26, 2019 at 02:47:30PM +, jenk...@build.gluster.org wrote:
>>> SRC: 
>>> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz
>>> HASH: 
>>> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum
>>
>> Packages for the CentOS Storage SIG are now available for testing.
>> Please try them out and report test results on this list.
>>
>>   # yum install centos-release-gluster
>>   # yum install --enablerepo=centos-gluster5-test glusterfs-server
> 
> Due to patch [1] upgrades are broken, so we are awaiting a fix or revert
> of the same before requesting a new build of 5.4.
> 
> The current RPMs should hence not be published.
> 
> Sanju/Hari, are we reverting this patch so that we can release 5.4, or
> are we expecting the fix to land in 5.4 (as in [2])?
> 
> Thanks,
> Shyam
> 
> [1] Patch causing regression: https://review.gluster.org/c/glusterfs/+/22148
> 
> [2] Proposed fix on master: https://review.gluster.org/c/glusterfs/+/22297/
> ___
> maintainers mailing list
> maintainers@gluster.org
> https://lists.gluster.org/mailman/listinfo/maintainers
> 
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] [gluster-packaging] glusterfs-5.4 released

[Sanju Rakonde]

On Tue, Mar 5, 2019 at 9:46 PM Shyam Ranganathan 
wrote:

> On 3/5/19 10:10 AM, Sanju Rakonde wrote:
> >
> >
> > On Tue, Mar 5, 2019 at 7:29 PM Shyam Ranganathan  > > wrote:
> >
> > On 2/27/19 5:19 AM, Niels de Vos wrote:
> > > On Tue, Feb 26, 2019 at 02:47:30PM +,
> > jenk...@build.gluster.org  wrote:
> > >> SRC:
> >
> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz
> > >> HASH:
> >
> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum
> > >
> > > Packages for the CentOS Storage SIG are now available for testing.
> > > Please try them out and report test results on this list.
> > >
> > >   # yum install centos-release-gluster
> > >   # yum install --enablerepo=centos-gluster5-test glusterfs-server
> >
> > Due to patch [1] upgrades are broken, so we are awaiting a fix or
> revert
> > of the same before requesting a new build of 5.4.
> >
> > The current RPMs should hence not be published.
> >
> > Sanju/Hari, are we reverting this patch so that we can release 5.4,
> or
> > are we expecting the fix to land in 5.4 (as in [2])?
> >
> >
> > Shyam, I need some more time(approximately 1 day) to provide the fix. If
> > we have 1 more day with us, we can wait. Or else we can revert the
> > patch[1] and continue with the release.
>
> We can wait a day, let me know tomorrow regarding the status. Thanks.
>

Shyam, the fix got some reviews. We are waiting for other reviewers to take
a look at it. If there are no other review comments, the patch
will  get merge tomorrow morning IST.

>
> >
> >
> > Thanks,
> > Shyam
> >
> > [1] Patch causing regression:
> > https://review.gluster.org/c/glusterfs/+/22148
> >
> > [2] Proposed fix on master:
> > https://review.gluster.org/c/glusterfs/+/22297/
> >
> >
> >
> > --
> > Thanks,
> > Sanju
>


-- 
Thanks,
Sanju
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] [gluster-packaging] glusterfs-5.4 released

[Shyam Ranganathan]

On 3/5/19 10:10 AM, Sanju Rakonde wrote:
> 
> 
> On Tue, Mar 5, 2019 at 7:29 PM Shyam Ranganathan  > wrote:
> 
> On 2/27/19 5:19 AM, Niels de Vos wrote:
> > On Tue, Feb 26, 2019 at 02:47:30PM +,
> jenk...@build.gluster.org  wrote:
> >> SRC:
> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz
> >> HASH:
> 
> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum
> >
> > Packages for the CentOS Storage SIG are now available for testing.
> > Please try them out and report test results on this list.
> >
> >   # yum install centos-release-gluster
> >   # yum install --enablerepo=centos-gluster5-test glusterfs-server
> 
> Due to patch [1] upgrades are broken, so we are awaiting a fix or revert
> of the same before requesting a new build of 5.4.
> 
> The current RPMs should hence not be published.
> 
> Sanju/Hari, are we reverting this patch so that we can release 5.4, or
> are we expecting the fix to land in 5.4 (as in [2])?
> 
> 
> Shyam, I need some more time(approximately 1 day) to provide the fix. If
> we have 1 more day with us, we can wait. Or else we can revert the
> patch[1] and continue with the release.

We can wait a day, let me know tomorrow regarding the status. Thanks.

> 
> 
> Thanks,
> Shyam
> 
> [1] Patch causing regression:
> https://review.gluster.org/c/glusterfs/+/22148
> 
> [2] Proposed fix on master:
> https://review.gluster.org/c/glusterfs/+/22297/
> 
> 
> 
> -- 
> Thanks,
> Sanju
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] [gluster-packaging] glusterfs-5.4 released

[Sanju Rakonde]

On Tue, Mar 5, 2019 at 7:29 PM Shyam Ranganathan 
wrote:

> On 2/27/19 5:19 AM, Niels de Vos wrote:
> > On Tue, Feb 26, 2019 at 02:47:30PM +, jenk...@build.gluster.org
> wrote:
> >> SRC:
> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz
> >> HASH:
> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum
> >
> > Packages for the CentOS Storage SIG are now available for testing.
> > Please try them out and report test results on this list.
> >
> >   # yum install centos-release-gluster
> >   # yum install --enablerepo=centos-gluster5-test glusterfs-server
>
> Due to patch [1] upgrades are broken, so we are awaiting a fix or revert
> of the same before requesting a new build of 5.4.
>
> The current RPMs should hence not be published.
>
> Sanju/Hari, are we reverting this patch so that we can release 5.4, or
> are we expecting the fix to land in 5.4 (as in [2])?
>

Shyam, I need some more time(approximately 1 day) to provide the fix. If we
have 1 more day with us, we can wait. Or else we can revert the patch[1]
and continue with the release.

>
> Thanks,
> Shyam
>
> [1] Patch causing regression:
> https://review.gluster.org/c/glusterfs/+/22148
>
> [2] Proposed fix on master:
> https://review.gluster.org/c/glusterfs/+/22297/
>


-- 
Thanks,
Sanju
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] [gluster-packaging] glusterfs-5.4 released

[Shyam Ranganathan]

On 2/27/19 5:19 AM, Niels de Vos wrote:
> On Tue, Feb 26, 2019 at 02:47:30PM +, jenk...@build.gluster.org wrote:
>> SRC: 
>> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz
>> HASH: 
>> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum
> 
> Packages for the CentOS Storage SIG are now available for testing.
> Please try them out and report test results on this list.
> 
>   # yum install centos-release-gluster
>   # yum install --enablerepo=centos-gluster5-test glusterfs-server

Due to patch [1] upgrades are broken, so we are awaiting a fix or revert
of the same before requesting a new build of 5.4.

The current RPMs should hence not be published.

Sanju/Hari, are we reverting this patch so that we can release 5.4, or
are we expecting the fix to land in 5.4 (as in [2])?

Thanks,
Shyam

[1] Patch causing regression: https://review.gluster.org/c/glusterfs/+/22148

[2] Proposed fix on master: https://review.gluster.org/c/glusterfs/+/22297/
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] [gluster-packaging] glusterfs-5.4 released

[Kaleb Keithley]

glusterfs-5.4 packages for:

* Fedora 29 are in the Fedora Updates-Testing repo. Use `dnf` to install.
Fedora packages will move to the Fedora Updates repo after a nominal
testing period. Fedora 28 and Fedora 30 packages are at [1].

* RHEL 8 Beta are at [1].

* Debian Stretch/9 are on download.gluster.org at [1] (arm64 packages
coming soon.) Debian Buster/Sid/10 packages will land after an issue with
the Buster mirrors is resolved.

* Xenial/16.04, Bionic/18.04, Cosmic/18.10, and Disco/19.04 are on
Launchpad at [2].

* SUSE SLES12SP4, Tumbleweed, SLES15, and Leap15 will be on OpenSUSE Build
Service at [3] soon.

I have updated all the .../LATEST symlinks.

[1] https://download.gluster.org/pub/gluster/glusterfs/5
[2] https://launchpad.net/~gluster/+archive/ubuntu/glusterfs-5
[3] https://build.opensuse.org/project/subprojects/home:glusterfs



On Tue, Feb 26, 2019 at 9:47 AM  wrote:

> SRC:
> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz
> HASH:
> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum
>
> This release is made off
> jenkins-release-80___
> packaging mailing list
> packag...@gluster.org
> https://lists.gluster.org/mailman/listinfo/packaging
>
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers

Re: [Gluster-Maintainers] [gluster-packaging] glusterfs-5.4 released

[Niels de Vos]

On Tue, Feb 26, 2019 at 02:47:30PM +, jenk...@build.gluster.org wrote:
> SRC: 
> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.tar.gz
> HASH: 
> https://build.gluster.org/job/release-new/80/artifact/glusterfs-5.4.sha512sum

Packages for the CentOS Storage SIG are now available for testing.
Please try them out and report test results on this list.

  # yum install centos-release-gluster
  # yum install --enablerepo=centos-gluster5-test glusterfs-server

Thanks,
Niels
___
maintainers mailing list
maintainers@gluster.org
https://lists.gluster.org/mailman/listinfo/maintainers