Re: [gluster-packaging] [Gluster-Maintainers] Requesting for an early 5.6 release

2019-04-11 Thread Shyam Ranganathan
On 4/11/19 9:58 AM, Patrick Matthäi wrote:
> 
> Am 08.04.2019 um 16:04 schrieb Shyam Ranganathan:
>> On 4/6/19 1:47 AM, Poornima Gurusiddaiah wrote:
>>> Hi,
>>>
>>> We had a critical bug [1], that got introduced in gluster release 5.
>>> There are users waiting on an update with the fix. Hence requesting for
>>> an out of band release for 5.6. Myself and jiffin, volunteer to do some
>>> tasks of the release- tagging(?) testing. But would need help with the
>>> builds and other tasks.
> 
> Hi,
> 
> Debian Buster 10 is now in freeze and I were able to pull in version 5.5
> instead of 5.4 for it. Pulling again a new upstream version to buster
> could be difficult..
> 
> Could you point me to the bug report and the diff for the critical fix,
> so that I can upload this explicit change to buster?

Here you go,
Bug: https://bugzilla.redhat.com/show_bug.cgi?id=1673058
Fix/patch: https://review.gluster.org/c/glusterfs/+/22404
commit ID on release-5 branch: 1fba86169b0850c3fcd02e56d0ddbba3efe9ae78

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


Re: [gluster-packaging] [Gluster-Maintainers] Requesting for an early 5.6 release

2019-04-11 Thread Patrick Matthäi

Am 08.04.2019 um 16:04 schrieb Shyam Ranganathan:
> On 4/6/19 1:47 AM, Poornima Gurusiddaiah wrote:
>> Hi,
>>
>> We had a critical bug [1], that got introduced in gluster release 5.
>> There are users waiting on an update with the fix. Hence requesting for
>> an out of band release for 5.6. Myself and jiffin, volunteer to do some
>> tasks of the release- tagging(?) testing. But would need help with the
>> builds and other tasks.

Hi,

Debian Buster 10 is now in freeze and I were able to pull in version 5.5
instead of 5.4 for it. Pulling again a new upstream version to buster
could be difficult..

Could you point me to the bug report and the diff for the critical fix,
so that I can upload this explicit change to buster?


-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/

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


Re: [gluster-packaging] [Gluster-Maintainers] Requesting for an early 5.6 release

2019-04-09 Thread Poornima Gurusiddaiah
Thank you Shyam, Niels and Kaleb. Sure i shall pick the testing, and the
other tasks you mentioned. I may not be able to do the building of
community packages for this release, as i have no prior experience in doing
this.
Will wait for tagging and centos rpms, and proceed with the testing.

Thank You,
Poornima

On Mon, Apr 8, 2019 at 8:07 PM Niels de Vos  wrote:

> On Mon, Apr 08, 2019 at 10:04:30AM -0400, Shyam Ranganathan wrote:
> > On 4/6/19 1:47 AM, Poornima Gurusiddaiah wrote:
> > > Hi,
> > >
> > > We had a critical bug [1], that got introduced in gluster release 5.
> > > There are users waiting on an update with the fix. Hence requesting for
> > > an out of band release for 5.6. Myself and jiffin, volunteer to do some
> > > tasks of the release- tagging(?) testing. But would need help with the
> > > builds and other tasks.
> >
> > Tagging and building a tarball needs rights on the release branch, also
> > it takes about 10 minutes to do, hence I can take care of the same.
> >
> > Packaging is still done by just 2 folks, so added the packaging list to
> > this mail, to understand if they need any assistance and their time
> > constraints.
>
> Packaging for the CentOS Storage SIG does not take much time either. At
> the moment I think only Kaleb and I have the permissions to do so. Still
> waiting for other contributors to reply to Sankarshans email
> https://lists.gluster.org/pipermail/gluster-infra/2019-March/005483.html
>
> The other community packages that Kaleb singlehandedly builds takes
> (much) more time. Contributors for those are very much wanted, I think.
>
> I don't mind doing an early/extra CentOS Storage SIG build.
>
> Niels
>
>
> >
> > Post packaging, we test if the RPMS are fine, and upgrade from an older
> > version. I use containers to test the same as detailed here [1]. Helping
> > out with this step can be useful, and I will assume till I hear
> > otherwise that you would taking care of the same for this minor release.
> >
> > Other activities include,
> > - prepare release notes
> > - Upload release notes to the doc site
> > - Announce the release
> > - Close bugs fixed in the release post the announcement
> >
> > Again, something I can take care of, and should take about 30 minutes
> > overall.
> >
> > Shyam
> >
> > [1] Package testing: https://hackmd.io/-yC3Ol68SwaRWr8bzaL8pw#
> > ___
> > packaging mailing list
> > packaging@gluster.org
> > https://lists.gluster.org/mailman/listinfo/packaging
>
___
packaging mailing list
packaging@gluster.org
https://lists.gluster.org/mailman/listinfo/packaging


Re: [gluster-packaging] [Gluster-Maintainers] Requesting for an early 5.6 release

2019-04-08 Thread Niels de Vos
On Mon, Apr 08, 2019 at 10:04:30AM -0400, Shyam Ranganathan wrote:
> On 4/6/19 1:47 AM, Poornima Gurusiddaiah wrote:
> > Hi,
> > 
> > We had a critical bug [1], that got introduced in gluster release 5.
> > There are users waiting on an update with the fix. Hence requesting for
> > an out of band release for 5.6. Myself and jiffin, volunteer to do some
> > tasks of the release- tagging(?) testing. But would need help with the
> > builds and other tasks.
> 
> Tagging and building a tarball needs rights on the release branch, also
> it takes about 10 minutes to do, hence I can take care of the same.
> 
> Packaging is still done by just 2 folks, so added the packaging list to
> this mail, to understand if they need any assistance and their time
> constraints.

Packaging for the CentOS Storage SIG does not take much time either. At
the moment I think only Kaleb and I have the permissions to do so. Still
waiting for other contributors to reply to Sankarshans email
https://lists.gluster.org/pipermail/gluster-infra/2019-March/005483.html

The other community packages that Kaleb singlehandedly builds takes
(much) more time. Contributors for those are very much wanted, I think.

I don't mind doing an early/extra CentOS Storage SIG build.

Niels


> 
> Post packaging, we test if the RPMS are fine, and upgrade from an older
> version. I use containers to test the same as detailed here [1]. Helping
> out with this step can be useful, and I will assume till I hear
> otherwise that you would taking care of the same for this minor release.
> 
> Other activities include,
> - prepare release notes
> - Upload release notes to the doc site
> - Announce the release
> - Close bugs fixed in the release post the announcement
> 
> Again, something I can take care of, and should take about 30 minutes
> overall.
> 
> Shyam
> 
> [1] Package testing: https://hackmd.io/-yC3Ol68SwaRWr8bzaL8pw#
> ___
> packaging mailing list
> packaging@gluster.org
> https://lists.gluster.org/mailman/listinfo/packaging
___
packaging mailing list
packaging@gluster.org
https://lists.gluster.org/mailman/listinfo/packaging


Re: [gluster-packaging] [Gluster-Maintainers] Requesting for an early 5.6 release

2019-04-08 Thread Shyam Ranganathan
On 4/6/19 1:47 AM, Poornima Gurusiddaiah wrote:
> Hi,
> 
> We had a critical bug [1], that got introduced in gluster release 5.
> There are users waiting on an update with the fix. Hence requesting for
> an out of band release for 5.6. Myself and jiffin, volunteer to do some
> tasks of the release- tagging(?) testing. But would need help with the
> builds and other tasks.

Tagging and building a tarball needs rights on the release branch, also
it takes about 10 minutes to do, hence I can take care of the same.

Packaging is still done by just 2 folks, so added the packaging list to
this mail, to understand if they need any assistance and their time
constraints.

Post packaging, we test if the RPMS are fine, and upgrade from an older
version. I use containers to test the same as detailed here [1]. Helping
out with this step can be useful, and I will assume till I hear
otherwise that you would taking care of the same for this minor release.

Other activities include,
- prepare release notes
- Upload release notes to the doc site
- Announce the release
- Close bugs fixed in the release post the announcement

Again, something I can take care of, and should take about 30 minutes
overall.

Shyam

[1] Package testing: https://hackmd.io/-yC3Ol68SwaRWr8bzaL8pw#
___
packaging mailing list
packaging@gluster.org
https://lists.gluster.org/mailman/listinfo/packaging