Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
On Mon, Jun 18, 2018 at 11:30 PM Kaleb S. KEITHLEY wrote: > > On 06/18/2018 12:03 PM, Kaushal M wrote: > > > > GD2 packages have been built for Fedora 28 and available from the > > updates-testing repo, and soon from the updates repo > > Packages are also available for Fedora 29/Rawhide. > > > I built GD2 rpms for Fedora 27 using the -vendor tar file. They are > available at [1]. > > Attempts to build from the non-vendor tar file failed. Logs from one of > the failed builds are at [2] for anyone who cares to examine them to see > why they failed. It's because a few of the updated packages that are required were/are still in updates-testing. I've found the koji uses dependencies in updates-testing when building packages. So when I built the package previously, I didn't notice that the packages weren't actually available in the updates repo. This has now been corrected, the dependencies in updates-testing have moved to updates, and one additional missing dependency has been added to updates-testing, which should move into updates soon. > > > [1] https://download.gluster.org/pub/gluster/glusterd2/4.1/ > [2] https://koji.fedoraproject.org/koji/taskinfo?taskID=27705828 > > > -- > > Kaleb ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
On 06/18/2018 12:03 PM, Kaushal M wrote: > > GD2 packages have been built for Fedora 28 and available from the > updates-testing repo, and soon from the updates repo > Packages are also available for Fedora 29/Rawhide. > I built GD2 rpms for Fedora 27 using the -vendor tar file. They are available at [1]. Attempts to build from the non-vendor tar file failed. Logs from one of the failed builds are at [2] for anyone who cares to examine them to see why they failed. [1] https://download.gluster.org/pub/gluster/glusterd2/4.1/ [2] https://koji.fedoraproject.org/koji/taskinfo?taskID=27705828 -- Kaleb ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
On Fri, Jun 15, 2018 at 6:26 PM Niels de Vos wrote: > > On Fri, Jun 15, 2018 at 05:03:38PM +0530, Kaushal M wrote: > > In Tue, Jun 12, 2018 at 10:15 PM Niels de Vos wrote: > > > > > > On Tue, Jun 12, 2018 at 11:26:33AM -0400, Shyam Ranganathan wrote: > > > > On 05/31/2018 09:22 AM, Shyam Ranganathan wrote: > > > > > As brick-mux tests were failing (and still are on master), this was > > > > > holding up the release activity. > > > > > > > > > > We now have a final fix [1] for the problem, and the situation has > > > > > improved over a series of fixes and reverts on the 4.1 branch as well. > > > > > > > > > > So we hope to branch RC0 today, and give a week for package and > > > > > upgrade > > > > > testing, before getting to GA. The revised calendar stands as follows, > > > > > > > > > > - RC0 Tagging: 31st May, 2018 > > > > > - RC0 Builds: 1st June, 2018 > > > > > - June 4th-8th: RC0 testing > > > > > - June 8th: GA readiness callout > > > > > - June 11th: GA tagging > > > > > > > > GA has been tagged today, and is off to packaging. > > > > > > The glusterfs packages should land in the testing repositories from the > > > CentOS Storage SIG soon. Currently glusterd2 is still on rc0 though. > > > Please test with the instructions from > > > http://lists.gluster.org/pipermail/packaging/2018-June/000553.html > > > > > > Thanks! > > > Niels > > > > GlusterD2-v4.1.0 has been tagged and released [1]. > > > > [1]: https://github.com/gluster/glusterd2/releases/tag/v4.1.0 > > Packages should become available in the CentOS Storage SIGs > centos-gluster41-test repository (el7 only) within an hour or so. > Testing can be done with the description from > http://lists.gluster.org/pipermail/packaging/2018-June/000553.html, the > package is called glusterd2. > > Please let me know if the build is functioning as required and I'll mark > if for release. GD2 packages have been built for Fedora 28 and available from the updates-testing repo, and soon from the updates repo Packages are also available for Fedora 29/Rawhide. > > Thanks, > Niels ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
On Fri, Jun 15, 2018 at 05:03:38PM +0530, Kaushal M wrote: > In Tue, Jun 12, 2018 at 10:15 PM Niels de Vos wrote: > > > > On Tue, Jun 12, 2018 at 11:26:33AM -0400, Shyam Ranganathan wrote: > > > On 05/31/2018 09:22 AM, Shyam Ranganathan wrote: > > > > As brick-mux tests were failing (and still are on master), this was > > > > holding up the release activity. > > > > > > > > We now have a final fix [1] for the problem, and the situation has > > > > improved over a series of fixes and reverts on the 4.1 branch as well. > > > > > > > > So we hope to branch RC0 today, and give a week for package and upgrade > > > > testing, before getting to GA. The revised calendar stands as follows, > > > > > > > > - RC0 Tagging: 31st May, 2018 > > > > - RC0 Builds: 1st June, 2018 > > > > - June 4th-8th: RC0 testing > > > > - June 8th: GA readiness callout > > > > - June 11th: GA tagging > > > > > > GA has been tagged today, and is off to packaging. > > > > The glusterfs packages should land in the testing repositories from the > > CentOS Storage SIG soon. Currently glusterd2 is still on rc0 though. > > Please test with the instructions from > > http://lists.gluster.org/pipermail/packaging/2018-June/000553.html > > > > Thanks! > > Niels > > GlusterD2-v4.1.0 has been tagged and released [1]. > > [1]: https://github.com/gluster/glusterd2/releases/tag/v4.1.0 Packages should become available in the CentOS Storage SIGs centos-gluster41-test repository (el7 only) within an hour or so. Testing can be done with the description from http://lists.gluster.org/pipermail/packaging/2018-June/000553.html, the package is called glusterd2. Please let me know if the build is functioning as required and I'll mark if for release. Thanks, Niels ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
what about packages built in Fedora? On 06/15/2018 07:33 AM, Kaushal M wrote: > In Tue, Jun 12, 2018 at 10:15 PM Niels de Vos wrote: >> >> On Tue, Jun 12, 2018 at 11:26:33AM -0400, Shyam Ranganathan wrote: >>> On 05/31/2018 09:22 AM, Shyam Ranganathan wrote: As brick-mux tests were failing (and still are on master), this was holding up the release activity. We now have a final fix [1] for the problem, and the situation has improved over a series of fixes and reverts on the 4.1 branch as well. So we hope to branch RC0 today, and give a week for package and upgrade testing, before getting to GA. The revised calendar stands as follows, - RC0 Tagging: 31st May, 2018 - RC0 Builds: 1st June, 2018 - June 4th-8th: RC0 testing - June 8th: GA readiness callout - June 11th: GA tagging >>> >>> GA has been tagged today, and is off to packaging. >> >> The glusterfs packages should land in the testing repositories from the >> CentOS Storage SIG soon. Currently glusterd2 is still on rc0 though. >> Please test with the instructions from >> http://lists.gluster.org/pipermail/packaging/2018-June/000553.html >> >> Thanks! >> Niels > > GlusterD2-v4.1.0 has been tagged and released [1]. > > [1]: https://github.com/gluster/glusterd2/releases/tag/v4.1.0 > >> ___ >> maintainers mailing list >> maintain...@gluster.org >> http://lists.gluster.org/mailman/listinfo/maintainers > ___ > maintainers mailing list > maintain...@gluster.org > http://lists.gluster.org/mailman/listinfo/maintainers > -- Kaleb ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
In Tue, Jun 12, 2018 at 10:15 PM Niels de Vos wrote: > > On Tue, Jun 12, 2018 at 11:26:33AM -0400, Shyam Ranganathan wrote: > > On 05/31/2018 09:22 AM, Shyam Ranganathan wrote: > > > As brick-mux tests were failing (and still are on master), this was > > > holding up the release activity. > > > > > > We now have a final fix [1] for the problem, and the situation has > > > improved over a series of fixes and reverts on the 4.1 branch as well. > > > > > > So we hope to branch RC0 today, and give a week for package and upgrade > > > testing, before getting to GA. The revised calendar stands as follows, > > > > > > - RC0 Tagging: 31st May, 2018 > > > - RC0 Builds: 1st June, 2018 > > > - June 4th-8th: RC0 testing > > > - June 8th: GA readiness callout > > > - June 11th: GA tagging > > > > GA has been tagged today, and is off to packaging. > > The glusterfs packages should land in the testing repositories from the > CentOS Storage SIG soon. Currently glusterd2 is still on rc0 though. > Please test with the instructions from > http://lists.gluster.org/pipermail/packaging/2018-June/000553.html > > Thanks! > Niels GlusterD2-v4.1.0 has been tagged and released [1]. [1]: https://github.com/gluster/glusterd2/releases/tag/v4.1.0 > ___ > maintainers mailing list > maintain...@gluster.org > http://lists.gluster.org/mailman/listinfo/maintainers ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
On Tue, Jun 12, 2018 at 11:26:33AM -0400, Shyam Ranganathan wrote: > On 05/31/2018 09:22 AM, Shyam Ranganathan wrote: > > As brick-mux tests were failing (and still are on master), this was > > holding up the release activity. > > > > We now have a final fix [1] for the problem, and the situation has > > improved over a series of fixes and reverts on the 4.1 branch as well. > > > > So we hope to branch RC0 today, and give a week for package and upgrade > > testing, before getting to GA. The revised calendar stands as follows, > > > > - RC0 Tagging: 31st May, 2018 > > - RC0 Builds: 1st June, 2018 > > - June 4th-8th: RC0 testing > > - June 8th: GA readiness callout > > - June 11th: GA tagging > > GA has been tagged today, and is off to packaging. The glusterfs packages should land in the testing repositories from the CentOS Storage SIG soon. Currently glusterd2 is still on rc0 though. Please test with the instructions from http://lists.gluster.org/pipermail/packaging/2018-June/000553.html Thanks! Niels ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
On 05/31/2018 09:22 AM, Shyam Ranganathan wrote: > As brick-mux tests were failing (and still are on master), this was > holding up the release activity. > > We now have a final fix [1] for the problem, and the situation has > improved over a series of fixes and reverts on the 4.1 branch as well. > > So we hope to branch RC0 today, and give a week for package and upgrade > testing, before getting to GA. The revised calendar stands as follows, > > - RC0 Tagging: 31st May, 2018 > - RC0 Builds: 1st June, 2018 > - June 4th-8th: RC0 testing > - June 8th: GA readiness callout > - June 11th: GA tagging GA has been tagged today, and is off to packaging. > - +2-4 days release announcement ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
On Mon, Jun 4, 2018 at 10:55 PM Kaleb S. KEITHLEY wrote: > > On 06/04/2018 11:32 AM, Kaushal M wrote: > > > > > We have a proper release this time. Source tarballs are available from [1]. > > > > [1]: https://github.com/gluster/glusterd2/releases/tag/v4.1.0-rc0 > > > > I didn't wait for you to do COPR builds. > > There are rpm packages for RHEL/CentOS 7, Fedora 27, Fedora 28, and > Fedora 29 at [1]. > > If you really want to use COPR builds instead, let me know and I'll > replace the ones I built with your COPR builds. > > I think you will find (as I did) that Fedora 28 (still) doesn't have all > the dependencies and you'll need to build from the -vendor tar file. > Ditto for Fedora 27. If you believe this should not be the case please > let me know. I did find this as well. Builds failed for F27 and F28, but succeeded on rawhide. What makes this strange is that our dependency versions haven't changed since 4.0, and I was able to build on all Fedora versions then. I'll need to investigate this. > > [1] https://download.gluster.org/pub/gluster/glusterd2/qa-releases/4.1rc0/ > > -- > > Kaleb ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
On Mon, Jun 04, 2018 at 09:02:30PM +0530, Kaushal M wrote: > On Mon, Jun 4, 2018 at 8:54 PM Kaushal M wrote: > > > > On Mon, Jun 4, 2018 at 8:39 PM Kaushal M wrote: > > > > > > On Sat, Jun 2, 2018 at 12:11 AM Kaushal M wrote: > > > > > > > > On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan > > > > wrote: > > > > > > > > > > On 05/31/2018 09:22 AM, Shyam Ranganathan wrote: > > > > > > As brick-mux tests were failing (and still are on master), this was > > > > > > holding up the release activity. > > > > > > > > > > > > We now have a final fix [1] for the problem, and the situation has > > > > > > improved over a series of fixes and reverts on the 4.1 branch as > > > > > > well. > > > > > > > > > > > > So we hope to branch RC0 today, and give a week for package and > > > > > > upgrade > > > > > > testing, before getting to GA. The revised calendar stands as > > > > > > follows, > > > > > > > > > > > > - RC0 Tagging: 31st May, 2018 > > > > > > > > > > RC0 Tagged and off to packaging! > > > > > > > > GD2 has been tagged as well. [1] > > > > > > > > [1]: https://github.com/gluster/glusterd2/releases/tag/v4.1.0-rc0 > > > > > > I've just realized I've made a mistake. I've pushed just the tags, > > > without updating the branch. > > > And now, the branch has landed new commits without my additional commits. > > > So, I've unintentionally created a different branch. > > > > > > I'm planning on deleting the tag, and updating the branch with the > > > release commits, and tagging once again. > > > Would this be okay? > > > > Oh well. Another thing I messed up in my midnight release-attempt. > > I forgot to publish the release-draft once I'd uploaded the tarballs. > > But this makes it easier for me. Because of this no one has the > > mis-tagged release. > > I'll do what I planned above, and do a proper release this time. > > We have a proper release this time. Source tarballs are available from [1]. > > [1]: https://github.com/gluster/glusterd2/releases/tag/v4.1.0-rc0 Thanks, I'll get this added to the CentOS Storage SIG repositories. Niels > > > > > > > > > > > > > > > > > > > > > - RC0 Builds: 1st June, 2018 > > > > > > - June 4th-8th: RC0 testing > > > > > > - June 8th: GA readiness callout > > > > > > - June 11th: GA tagging > > > > > > - +2-4 days release announcement > > > > > > > > > > > > Thanks, > > > > > > Shyam > > > > > > > > > > > > [1] Last fix for mux (and non-mux related): > > > > > > https://review.gluster.org/#/c/20109/1 > > > > > > > > > > > > On 05/09/2018 03:41 PM, Shyam Ranganathan wrote: > > > > > >> Here is the current release activity calendar, > > > > > >> > > > > > >> - RC0 tagging: May 14th > > > > > >> - RC0 builds: May 15th > > > > > >> - May 15th - 25th > > > > > >> - Upgrade testing > > > > > >> - General testing and feedback period > > > > > >> - (on need basis) RC1 build: May 26th > > > > > >> - GA readiness call out: May, 28th > > > > > >> - GA tagging: May, 30th > > > > > >> - +2-4 days release announcement > > > > > >> > > > > > >> Thanks, > > > > > >> Shyam > > > > > >> > > > > > >> On 05/06/2018 09:20 AM, Shyam Ranganathan wrote: > > > > > >>> Hi, > > > > > >>> > > > > > >>> Release 4.1 has been branched, as it was done later than > > > > > >>> anticipated the > > > > > >>> calendar of tasks below would be reworked accordingly this week > > > > > >>> and > > > > > >>> posted to the lists. > > > > > >>> > > > > > >>> Thanks, > > > > > >>> Shyam > > > > > >>> > > > > > >>> On 03/27/2018 02:59 PM, Shyam Ranganathan wrote: > > > > > Hi, > > > > > > > > > > As we have completed potential scope for 4.1 release (reflected > > > > > here [1] > > > > > and also here [2]), it's time to talk about the schedule. > > > > > > > > > > - Branching date (and hence feature exception date): Apr 16th > > > > > - Week of Apr 16th release notes updated for all features in the > > > > > release > > > > > - RC0 tagging: Apr 23rd > > > > > - Week of Apr 23rd, upgrade and other testing > > > > > - RCNext: May 7th (if critical failures, or exception features > > > > > arrive late) > > > > > - RCNext: May 21st > > > > > - Week of May 21st, final upgrade and testing > > > > > - GA readiness call out: May, 28th > > > > > - GA tagging: May, 30th > > > > > - +2-4 days release announcement > > > > > > > > > > and, review focus. As in older releases, I am starring reviews > > > > > that are > > > > > submitted against features, this should help if you are looking > > > > > to help > > > > > accelerate feature commits for the release (IOW, this list is > > > > > the watch > > > > > list for reviews). This can be found handy here [3]. > > > > > > > > > > So, branching is in about 4 weeks! > > > > > > > > > > Thanks, > > > > > Shyam > > > > > > > > > > [1] Issues marked against release 4.1: > > > > >
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
On 06/04/2018 11:32 AM, Kaushal M wrote: > > We have a proper release this time. Source tarballs are available from [1]. > > [1]: https://github.com/gluster/glusterd2/releases/tag/v4.1.0-rc0 > I didn't wait for you to do COPR builds. There are rpm packages for RHEL/CentOS 7, Fedora 27, Fedora 28, and Fedora 29 at [1]. If you really want to use COPR builds instead, let me know and I'll replace the ones I built with your COPR builds. I think you will find (as I did) that Fedora 28 (still) doesn't have all the dependencies and you'll need to build from the -vendor tar file. Ditto for Fedora 27. If you believe this should not be the case please let me know. [1] https://download.gluster.org/pub/gluster/glusterd2/qa-releases/4.1rc0/ -- Kaleb ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
On Mon, Jun 4, 2018 at 8:54 PM Kaushal M wrote: > > On Mon, Jun 4, 2018 at 8:39 PM Kaushal M wrote: > > > > On Sat, Jun 2, 2018 at 12:11 AM Kaushal M wrote: > > > > > > On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan > > > wrote: > > > > > > > > On 05/31/2018 09:22 AM, Shyam Ranganathan wrote: > > > > > As brick-mux tests were failing (and still are on master), this was > > > > > holding up the release activity. > > > > > > > > > > We now have a final fix [1] for the problem, and the situation has > > > > > improved over a series of fixes and reverts on the 4.1 branch as well. > > > > > > > > > > So we hope to branch RC0 today, and give a week for package and > > > > > upgrade > > > > > testing, before getting to GA. The revised calendar stands as follows, > > > > > > > > > > - RC0 Tagging: 31st May, 2018 > > > > > > > > RC0 Tagged and off to packaging! > > > > > > GD2 has been tagged as well. [1] > > > > > > [1]: https://github.com/gluster/glusterd2/releases/tag/v4.1.0-rc0 > > > > I've just realized I've made a mistake. I've pushed just the tags, > > without updating the branch. > > And now, the branch has landed new commits without my additional commits. > > So, I've unintentionally created a different branch. > > > > I'm planning on deleting the tag, and updating the branch with the > > release commits, and tagging once again. > > Would this be okay? > > Oh well. Another thing I messed up in my midnight release-attempt. > I forgot to publish the release-draft once I'd uploaded the tarballs. > But this makes it easier for me. Because of this no one has the > mis-tagged release. > I'll do what I planned above, and do a proper release this time. We have a proper release this time. Source tarballs are available from [1]. [1]: https://github.com/gluster/glusterd2/releases/tag/v4.1.0-rc0 > > > > > > > > > > > > > > > - RC0 Builds: 1st June, 2018 > > > > > - June 4th-8th: RC0 testing > > > > > - June 8th: GA readiness callout > > > > > - June 11th: GA tagging > > > > > - +2-4 days release announcement > > > > > > > > > > Thanks, > > > > > Shyam > > > > > > > > > > [1] Last fix for mux (and non-mux related): > > > > > https://review.gluster.org/#/c/20109/1 > > > > > > > > > > On 05/09/2018 03:41 PM, Shyam Ranganathan wrote: > > > > >> Here is the current release activity calendar, > > > > >> > > > > >> - RC0 tagging: May 14th > > > > >> - RC0 builds: May 15th > > > > >> - May 15th - 25th > > > > >> - Upgrade testing > > > > >> - General testing and feedback period > > > > >> - (on need basis) RC1 build: May 26th > > > > >> - GA readiness call out: May, 28th > > > > >> - GA tagging: May, 30th > > > > >> - +2-4 days release announcement > > > > >> > > > > >> Thanks, > > > > >> Shyam > > > > >> > > > > >> On 05/06/2018 09:20 AM, Shyam Ranganathan wrote: > > > > >>> Hi, > > > > >>> > > > > >>> Release 4.1 has been branched, as it was done later than > > > > >>> anticipated the > > > > >>> calendar of tasks below would be reworked accordingly this week and > > > > >>> posted to the lists. > > > > >>> > > > > >>> Thanks, > > > > >>> Shyam > > > > >>> > > > > >>> On 03/27/2018 02:59 PM, Shyam Ranganathan wrote: > > > > Hi, > > > > > > > > As we have completed potential scope for 4.1 release (reflected > > > > here [1] > > > > and also here [2]), it's time to talk about the schedule. > > > > > > > > - Branching date (and hence feature exception date): Apr 16th > > > > - Week of Apr 16th release notes updated for all features in the > > > > release > > > > - RC0 tagging: Apr 23rd > > > > - Week of Apr 23rd, upgrade and other testing > > > > - RCNext: May 7th (if critical failures, or exception features > > > > arrive late) > > > > - RCNext: May 21st > > > > - Week of May 21st, final upgrade and testing > > > > - GA readiness call out: May, 28th > > > > - GA tagging: May, 30th > > > > - +2-4 days release announcement > > > > > > > > and, review focus. As in older releases, I am starring reviews > > > > that are > > > > submitted against features, this should help if you are looking to > > > > help > > > > accelerate feature commits for the release (IOW, this list is the > > > > watch > > > > list for reviews). This can be found handy here [3]. > > > > > > > > So, branching is in about 4 weeks! > > > > > > > > Thanks, > > > > Shyam > > > > > > > > [1] Issues marked against release 4.1: > > > > https://github.com/gluster/glusterfs/milestone/5 > > > > > > > > [2] github project lane for 4.1: > > > > https://github.com/gluster/glusterfs/projects/1#column-1075416 > > > > > > > > [3] Review focus dashboard: > > > > https://review.gluster.org/#/q/starredby:srangana%2540redhat.com > > > > ___ > > > > maintainers mailing list > > > >
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
On Mon, Jun 4, 2018 at 8:39 PM Kaushal M wrote: > > On Sat, Jun 2, 2018 at 12:11 AM Kaushal M wrote: > > > > On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan > > wrote: > > > > > > On 05/31/2018 09:22 AM, Shyam Ranganathan wrote: > > > > As brick-mux tests were failing (and still are on master), this was > > > > holding up the release activity. > > > > > > > > We now have a final fix [1] for the problem, and the situation has > > > > improved over a series of fixes and reverts on the 4.1 branch as well. > > > > > > > > So we hope to branch RC0 today, and give a week for package and upgrade > > > > testing, before getting to GA. The revised calendar stands as follows, > > > > > > > > - RC0 Tagging: 31st May, 2018 > > > > > > RC0 Tagged and off to packaging! > > > > GD2 has been tagged as well. [1] > > > > [1]: https://github.com/gluster/glusterd2/releases/tag/v4.1.0-rc0 > > I've just realized I've made a mistake. I've pushed just the tags, > without updating the branch. > And now, the branch has landed new commits without my additional commits. > So, I've unintentionally created a different branch. > > I'm planning on deleting the tag, and updating the branch with the > release commits, and tagging once again. > Would this be okay? Oh well. Another thing I messed up in my midnight release-attempt. I forgot to publish the release-draft once I'd uploaded the tarballs. But this makes it easier for me. Because of this no one has the mis-tagged release. I'll do what I planned above, and do a proper release this time. > > > > > > > > > > - RC0 Builds: 1st June, 2018 > > > > - June 4th-8th: RC0 testing > > > > - June 8th: GA readiness callout > > > > - June 11th: GA tagging > > > > - +2-4 days release announcement > > > > > > > > Thanks, > > > > Shyam > > > > > > > > [1] Last fix for mux (and non-mux related): > > > > https://review.gluster.org/#/c/20109/1 > > > > > > > > On 05/09/2018 03:41 PM, Shyam Ranganathan wrote: > > > >> Here is the current release activity calendar, > > > >> > > > >> - RC0 tagging: May 14th > > > >> - RC0 builds: May 15th > > > >> - May 15th - 25th > > > >> - Upgrade testing > > > >> - General testing and feedback period > > > >> - (on need basis) RC1 build: May 26th > > > >> - GA readiness call out: May, 28th > > > >> - GA tagging: May, 30th > > > >> - +2-4 days release announcement > > > >> > > > >> Thanks, > > > >> Shyam > > > >> > > > >> On 05/06/2018 09:20 AM, Shyam Ranganathan wrote: > > > >>> Hi, > > > >>> > > > >>> Release 4.1 has been branched, as it was done later than anticipated > > > >>> the > > > >>> calendar of tasks below would be reworked accordingly this week and > > > >>> posted to the lists. > > > >>> > > > >>> Thanks, > > > >>> Shyam > > > >>> > > > >>> On 03/27/2018 02:59 PM, Shyam Ranganathan wrote: > > > Hi, > > > > > > As we have completed potential scope for 4.1 release (reflected here > > > [1] > > > and also here [2]), it's time to talk about the schedule. > > > > > > - Branching date (and hence feature exception date): Apr 16th > > > - Week of Apr 16th release notes updated for all features in the > > > release > > > - RC0 tagging: Apr 23rd > > > - Week of Apr 23rd, upgrade and other testing > > > - RCNext: May 7th (if critical failures, or exception features > > > arrive late) > > > - RCNext: May 21st > > > - Week of May 21st, final upgrade and testing > > > - GA readiness call out: May, 28th > > > - GA tagging: May, 30th > > > - +2-4 days release announcement > > > > > > and, review focus. As in older releases, I am starring reviews that > > > are > > > submitted against features, this should help if you are looking to > > > help > > > accelerate feature commits for the release (IOW, this list is the > > > watch > > > list for reviews). This can be found handy here [3]. > > > > > > So, branching is in about 4 weeks! > > > > > > Thanks, > > > Shyam > > > > > > [1] Issues marked against release 4.1: > > > https://github.com/gluster/glusterfs/milestone/5 > > > > > > [2] github project lane for 4.1: > > > https://github.com/gluster/glusterfs/projects/1#column-1075416 > > > > > > [3] Review focus dashboard: > > > https://review.gluster.org/#/q/starredby:srangana%2540redhat.com > > > ___ > > > maintainers mailing list > > > maintain...@gluster.org > > > http://lists.gluster.org/mailman/listinfo/maintainers > > > > > > >>> ___ > > > >>> maintainers mailing list > > > >>> maintain...@gluster.org > > > >>> http://lists.gluster.org/mailman/listinfo/maintainers > > > >>> > > > >> ___ > > > >> Gluster-devel mailing list > > > >> Gluster-devel@gluster.org > > > >>
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
On 06/04/2018 11:05 AM, Kaushal M wrote: > >> And it's good that RC0 was tagged in a timely matter. Who is building >> those packages? > > I can build the RPMs. I'll build them on the COPR I've been > maintaining. But I don't believe that those can be used as the > official RPM sources. > So where should I build and how should they be distributed? Test packages don't need to be "official" and can be built anywhere AFAIC. COPR is fine. Or koji scratch builds. Once they're built tell me where and I'll sign them and put them on download.gluster.org Thanks, -- Kaleb ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
On Sat, Jun 2, 2018 at 12:11 AM Kaushal M wrote: > > On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan wrote: > > > > On 05/31/2018 09:22 AM, Shyam Ranganathan wrote: > > > As brick-mux tests were failing (and still are on master), this was > > > holding up the release activity. > > > > > > We now have a final fix [1] for the problem, and the situation has > > > improved over a series of fixes and reverts on the 4.1 branch as well. > > > > > > So we hope to branch RC0 today, and give a week for package and upgrade > > > testing, before getting to GA. The revised calendar stands as follows, > > > > > > - RC0 Tagging: 31st May, 2018 > > > > RC0 Tagged and off to packaging! > > GD2 has been tagged as well. [1] > > [1]: https://github.com/gluster/glusterd2/releases/tag/v4.1.0-rc0 I've just realized I've made a mistake. I've pushed just the tags, without updating the branch. And now, the branch has landed new commits without my additional commits. So, I've unintentionally created a different branch. I'm planning on deleting the tag, and updating the branch with the release commits, and tagging once again. Would this be okay? > > > > > > - RC0 Builds: 1st June, 2018 > > > - June 4th-8th: RC0 testing > > > - June 8th: GA readiness callout > > > - June 11th: GA tagging > > > - +2-4 days release announcement > > > > > > Thanks, > > > Shyam > > > > > > [1] Last fix for mux (and non-mux related): > > > https://review.gluster.org/#/c/20109/1 > > > > > > On 05/09/2018 03:41 PM, Shyam Ranganathan wrote: > > >> Here is the current release activity calendar, > > >> > > >> - RC0 tagging: May 14th > > >> - RC0 builds: May 15th > > >> - May 15th - 25th > > >> - Upgrade testing > > >> - General testing and feedback period > > >> - (on need basis) RC1 build: May 26th > > >> - GA readiness call out: May, 28th > > >> - GA tagging: May, 30th > > >> - +2-4 days release announcement > > >> > > >> Thanks, > > >> Shyam > > >> > > >> On 05/06/2018 09:20 AM, Shyam Ranganathan wrote: > > >>> Hi, > > >>> > > >>> Release 4.1 has been branched, as it was done later than anticipated the > > >>> calendar of tasks below would be reworked accordingly this week and > > >>> posted to the lists. > > >>> > > >>> Thanks, > > >>> Shyam > > >>> > > >>> On 03/27/2018 02:59 PM, Shyam Ranganathan wrote: > > Hi, > > > > As we have completed potential scope for 4.1 release (reflected here > > [1] > > and also here [2]), it's time to talk about the schedule. > > > > - Branching date (and hence feature exception date): Apr 16th > > - Week of Apr 16th release notes updated for all features in the > > release > > - RC0 tagging: Apr 23rd > > - Week of Apr 23rd, upgrade and other testing > > - RCNext: May 7th (if critical failures, or exception features arrive > > late) > > - RCNext: May 21st > > - Week of May 21st, final upgrade and testing > > - GA readiness call out: May, 28th > > - GA tagging: May, 30th > > - +2-4 days release announcement > > > > and, review focus. As in older releases, I am starring reviews that are > > submitted against features, this should help if you are looking to help > > accelerate feature commits for the release (IOW, this list is the watch > > list for reviews). This can be found handy here [3]. > > > > So, branching is in about 4 weeks! > > > > Thanks, > > Shyam > > > > [1] Issues marked against release 4.1: > > https://github.com/gluster/glusterfs/milestone/5 > > > > [2] github project lane for 4.1: > > https://github.com/gluster/glusterfs/projects/1#column-1075416 > > > > [3] Review focus dashboard: > > https://review.gluster.org/#/q/starredby:srangana%2540redhat.com > > ___ > > maintainers mailing list > > maintain...@gluster.org > > http://lists.gluster.org/mailman/listinfo/maintainers > > > > >>> ___ > > >>> maintainers mailing list > > >>> maintain...@gluster.org > > >>> http://lists.gluster.org/mailman/listinfo/maintainers > > >>> > > >> ___ > > >> Gluster-devel mailing list > > >> Gluster-devel@gluster.org > > >> http://lists.gluster.org/mailman/listinfo/gluster-devel > > >> > > > ___ > > > Gluster-devel mailing list > > > Gluster-devel@gluster.org > > > http://lists.gluster.org/mailman/listinfo/gluster-devel > > > > > ___ > > maintainers mailing list > > maintain...@gluster.org > > http://lists.gluster.org/mailman/listinfo/maintainers ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
On Mon, Jun 4, 2018 at 5:29 PM Kaleb S. KEITHLEY wrote: > > On 06/02/2018 07:47 AM, Niels de Vos wrote: > > On Sat, Jun 02, 2018 at 12:11:55AM +0530, Kaushal M wrote: > >> On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan > >> wrote: > >>> > >>> On 05/31/2018 09:22 AM, Shyam Ranganathan wrote: > As brick-mux tests were failing (and still are on master), this was > holding up the release activity. > > We now have a final fix [1] for the problem, and the situation has > improved over a series of fixes and reverts on the 4.1 branch as well. > > So we hope to branch RC0 today, and give a week for package and upgrade > testing, before getting to GA. The revised calendar stands as follows, > > - RC0 Tagging: 31st May, 2018 > >>> > >>> RC0 Tagged and off to packaging! > >> > >> GD2 has been tagged as well. [1] > >> > >> [1]: https://github.com/gluster/glusterd2/releases/tag/v4.1.0-rc0 > > > > What is the status of the RPM for GD2? Can the Fedora RPM be rebuilt > > directly on CentOS, or does it need additional dependencies? (Note that > > CentOS does not allow dependencies from Fedora EPEL.) > > > > I checked, and was surprised to see that gd2 made it into Fedora[1]. I > guess I missed the announcement. This happened in time for the 4.0 release. I did send out an announcement IIRC. > > But I was disappointed to see that packages have only been built for > Fedora29/rawhide. We've been shipping glusterfs-4.0 in Fedora28 and even > if [2] didn't say so, I would think it would be obvious that we should > have packages for gd2 in F28 too. > The package got accepted during the F28 freeze. So I was only able to request a branch for F27 when 4.0 happened. I should have gotten around to requesting a branch for F28, but I forgot. > And it's good that RC0 was tagged in a timely matter. Who is building > those packages? I can build the RPMs. I'll build them on the COPR I've been maintaining. But I don't believe that those can be used as the official RPM sources. So where should I build and how should they be distributed? > > [1] https://koji.fedoraproject.org/koji/packageinfo?packageID=26508 > [2] https://docs.gluster.org/en/latest/Install-Guide/Community_Packages/ > -- > > Kaleb ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
On Mon, Jun 4, 2018 at 7:05 PM Kaleb S. KEITHLEY wrote: > > On 06/02/2018 07:47 AM, Niels de Vos wrote: > > On Sat, Jun 02, 2018 at 12:11:55AM +0530, Kaushal M wrote: > >> On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan > >> wrote: > >>> > >>> On 05/31/2018 09:22 AM, Shyam Ranganathan wrote: > As brick-mux tests were failing (and still are on master), this was > holding up the release activity. > > We now have a final fix [1] for the problem, and the situation has > improved over a series of fixes and reverts on the 4.1 branch as well. > > So we hope to branch RC0 today, and give a week for package and upgrade > testing, before getting to GA. The revised calendar stands as follows, > > - RC0 Tagging: 31st May, 2018 > >>> > >>> RC0 Tagged and off to packaging! > >> > >> GD2 has been tagged as well. [1] > >> > >> [1]: https://github.com/gluster/glusterd2/releases/tag/v4.1.0-rc0 > > > > What is the status of the RPM for GD2? Can the Fedora RPM be rebuilt > > directly on CentOS, or does it need additional dependencies? (Note that > > CentOS does not allow dependencies from Fedora EPEL.) > > > > My recollection of how this works is that one would need to build from > the "bundled vendor" tarball. > > Except when I tried to download the vendor bundle tarball I got the same > bits as the unbundled tarball. > > ISTR Kaushal had to do something extra to generate the vendor bundled > tarball. It doesn't appear that that occured. That is right. For CentOS/EL, the default in the spec is to use the vendored tarball. Using this, the only requirement to build GD2 is golang>=1.8. Are you sure you're downloading the right tarball [1]? [1]: https://github.com/gluster/glusterd2/releases/download/v4.1.0-rc0/glusterd2-v4.1.0-rc0-vendor.tar.xz > > -- > > Kaleb ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
On 06/02/2018 07:47 AM, Niels de Vos wrote: > On Sat, Jun 02, 2018 at 12:11:55AM +0530, Kaushal M wrote: >> On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan wrote: >>> >>> On 05/31/2018 09:22 AM, Shyam Ranganathan wrote: As brick-mux tests were failing (and still are on master), this was holding up the release activity. We now have a final fix [1] for the problem, and the situation has improved over a series of fixes and reverts on the 4.1 branch as well. So we hope to branch RC0 today, and give a week for package and upgrade testing, before getting to GA. The revised calendar stands as follows, - RC0 Tagging: 31st May, 2018 >>> >>> RC0 Tagged and off to packaging! >> >> GD2 has been tagged as well. [1] >> >> [1]: https://github.com/gluster/glusterd2/releases/tag/v4.1.0-rc0 > > What is the status of the RPM for GD2? Can the Fedora RPM be rebuilt > directly on CentOS, or does it need additional dependencies? (Note that > CentOS does not allow dependencies from Fedora EPEL.) > My recollection of how this works is that one would need to build from the "bundled vendor" tarball. Except when I tried to download the vendor bundle tarball I got the same bits as the unbundled tarball. ISTR Kaushal had to do something extra to generate the vendor bundled tarball. It doesn't appear that that occured. -- Kaleb ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
On 06/02/2018 07:47 AM, Niels de Vos wrote: > On Sat, Jun 02, 2018 at 12:11:55AM +0530, Kaushal M wrote: >> On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan wrote: >>> >>> On 05/31/2018 09:22 AM, Shyam Ranganathan wrote: As brick-mux tests were failing (and still are on master), this was holding up the release activity. We now have a final fix [1] for the problem, and the situation has improved over a series of fixes and reverts on the 4.1 branch as well. So we hope to branch RC0 today, and give a week for package and upgrade testing, before getting to GA. The revised calendar stands as follows, - RC0 Tagging: 31st May, 2018 >>> >>> RC0 Tagged and off to packaging! >> >> GD2 has been tagged as well. [1] >> >> [1]: https://github.com/gluster/glusterd2/releases/tag/v4.1.0-rc0 > > What is the status of the RPM for GD2? Can the Fedora RPM be rebuilt > directly on CentOS, or does it need additional dependencies? (Note that > CentOS does not allow dependencies from Fedora EPEL.) > I checked, and was surprised to see that gd2 made it into Fedora[1]. I guess I missed the announcement. But I was disappointed to see that packages have only been built for Fedora29/rawhide. We've been shipping glusterfs-4.0 in Fedora28 and even if [2] didn't say so, I would think it would be obvious that we should have packages for gd2 in F28 too. And it's good that RC0 was tagged in a timely matter. Who is building those packages? [1] https://koji.fedoraproject.org/koji/packageinfo?packageID=26508 [2] https://docs.gluster.org/en/latest/Install-Guide/Community_Packages/ -- Kaleb ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
On Sat, Jun 02, 2018 at 12:11:55AM +0530, Kaushal M wrote: > On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan wrote: > > > > On 05/31/2018 09:22 AM, Shyam Ranganathan wrote: > > > As brick-mux tests were failing (and still are on master), this was > > > holding up the release activity. > > > > > > We now have a final fix [1] for the problem, and the situation has > > > improved over a series of fixes and reverts on the 4.1 branch as well. > > > > > > So we hope to branch RC0 today, and give a week for package and upgrade > > > testing, before getting to GA. The revised calendar stands as follows, > > > > > > - RC0 Tagging: 31st May, 2018 > > > > RC0 Tagged and off to packaging! > > GD2 has been tagged as well. [1] > > [1]: https://github.com/gluster/glusterd2/releases/tag/v4.1.0-rc0 What is the status of the RPM for GD2? Can the Fedora RPM be rebuilt directly on CentOS, or does it need additional dependencies? (Note that CentOS does not allow dependencies from Fedora EPEL.) Thanks, Niels > > > > > > - RC0 Builds: 1st June, 2018 > > > - June 4th-8th: RC0 testing > > > - June 8th: GA readiness callout > > > - June 11th: GA tagging > > > - +2-4 days release announcement > > > > > > Thanks, > > > Shyam > > > > > > [1] Last fix for mux (and non-mux related): > > > https://review.gluster.org/#/c/20109/1 > > > > > > On 05/09/2018 03:41 PM, Shyam Ranganathan wrote: > > >> Here is the current release activity calendar, > > >> > > >> - RC0 tagging: May 14th > > >> - RC0 builds: May 15th > > >> - May 15th - 25th > > >> - Upgrade testing > > >> - General testing and feedback period > > >> - (on need basis) RC1 build: May 26th > > >> - GA readiness call out: May, 28th > > >> - GA tagging: May, 30th > > >> - +2-4 days release announcement > > >> > > >> Thanks, > > >> Shyam > > >> > > >> On 05/06/2018 09:20 AM, Shyam Ranganathan wrote: > > >>> Hi, > > >>> > > >>> Release 4.1 has been branched, as it was done later than anticipated the > > >>> calendar of tasks below would be reworked accordingly this week and > > >>> posted to the lists. > > >>> > > >>> Thanks, > > >>> Shyam > > >>> > > >>> On 03/27/2018 02:59 PM, Shyam Ranganathan wrote: > > Hi, > > > > As we have completed potential scope for 4.1 release (reflected here > > [1] > > and also here [2]), it's time to talk about the schedule. > > > > - Branching date (and hence feature exception date): Apr 16th > > - Week of Apr 16th release notes updated for all features in the > > release > > - RC0 tagging: Apr 23rd > > - Week of Apr 23rd, upgrade and other testing > > - RCNext: May 7th (if critical failures, or exception features arrive > > late) > > - RCNext: May 21st > > - Week of May 21st, final upgrade and testing > > - GA readiness call out: May, 28th > > - GA tagging: May, 30th > > - +2-4 days release announcement > > > > and, review focus. As in older releases, I am starring reviews that are > > submitted against features, this should help if you are looking to help > > accelerate feature commits for the release (IOW, this list is the watch > > list for reviews). This can be found handy here [3]. > > > > So, branching is in about 4 weeks! > > > > Thanks, > > Shyam > > > > [1] Issues marked against release 4.1: > > https://github.com/gluster/glusterfs/milestone/5 > > > > [2] github project lane for 4.1: > > https://github.com/gluster/glusterfs/projects/1#column-1075416 > > > > [3] Review focus dashboard: > > https://review.gluster.org/#/q/starredby:srangana%2540redhat.com > > ___ > > maintainers mailing list > > maintain...@gluster.org > > http://lists.gluster.org/mailman/listinfo/maintainers > > > > >>> ___ > > >>> maintainers mailing list > > >>> maintain...@gluster.org > > >>> http://lists.gluster.org/mailman/listinfo/maintainers > > >>> > > >> ___ > > >> Gluster-devel mailing list > > >> Gluster-devel@gluster.org > > >> http://lists.gluster.org/mailman/listinfo/gluster-devel > > >> > > > ___ > > > Gluster-devel mailing list > > > Gluster-devel@gluster.org > > > http://lists.gluster.org/mailman/listinfo/gluster-devel > > > > > ___ > > maintainers mailing list > > maintain...@gluster.org > > http://lists.gluster.org/mailman/listinfo/maintainers > ___ > maintainers mailing list > maintain...@gluster.org > http://lists.gluster.org/mailman/listinfo/maintainers ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan wrote: > > On 05/31/2018 09:22 AM, Shyam Ranganathan wrote: > > As brick-mux tests were failing (and still are on master), this was > > holding up the release activity. > > > > We now have a final fix [1] for the problem, and the situation has > > improved over a series of fixes and reverts on the 4.1 branch as well. > > > > So we hope to branch RC0 today, and give a week for package and upgrade > > testing, before getting to GA. The revised calendar stands as follows, > > > > - RC0 Tagging: 31st May, 2018 > > RC0 Tagged and off to packaging! GD2 has been tagged as well. [1] [1]: https://github.com/gluster/glusterd2/releases/tag/v4.1.0-rc0 > > > - RC0 Builds: 1st June, 2018 > > - June 4th-8th: RC0 testing > > - June 8th: GA readiness callout > > - June 11th: GA tagging > > - +2-4 days release announcement > > > > Thanks, > > Shyam > > > > [1] Last fix for mux (and non-mux related): > > https://review.gluster.org/#/c/20109/1 > > > > On 05/09/2018 03:41 PM, Shyam Ranganathan wrote: > >> Here is the current release activity calendar, > >> > >> - RC0 tagging: May 14th > >> - RC0 builds: May 15th > >> - May 15th - 25th > >> - Upgrade testing > >> - General testing and feedback period > >> - (on need basis) RC1 build: May 26th > >> - GA readiness call out: May, 28th > >> - GA tagging: May, 30th > >> - +2-4 days release announcement > >> > >> Thanks, > >> Shyam > >> > >> On 05/06/2018 09:20 AM, Shyam Ranganathan wrote: > >>> Hi, > >>> > >>> Release 4.1 has been branched, as it was done later than anticipated the > >>> calendar of tasks below would be reworked accordingly this week and > >>> posted to the lists. > >>> > >>> Thanks, > >>> Shyam > >>> > >>> On 03/27/2018 02:59 PM, Shyam Ranganathan wrote: > Hi, > > As we have completed potential scope for 4.1 release (reflected here [1] > and also here [2]), it's time to talk about the schedule. > > - Branching date (and hence feature exception date): Apr 16th > - Week of Apr 16th release notes updated for all features in the release > - RC0 tagging: Apr 23rd > - Week of Apr 23rd, upgrade and other testing > - RCNext: May 7th (if critical failures, or exception features arrive > late) > - RCNext: May 21st > - Week of May 21st, final upgrade and testing > - GA readiness call out: May, 28th > - GA tagging: May, 30th > - +2-4 days release announcement > > and, review focus. As in older releases, I am starring reviews that are > submitted against features, this should help if you are looking to help > accelerate feature commits for the release (IOW, this list is the watch > list for reviews). This can be found handy here [3]. > > So, branching is in about 4 weeks! > > Thanks, > Shyam > > [1] Issues marked against release 4.1: > https://github.com/gluster/glusterfs/milestone/5 > > [2] github project lane for 4.1: > https://github.com/gluster/glusterfs/projects/1#column-1075416 > > [3] Review focus dashboard: > https://review.gluster.org/#/q/starredby:srangana%2540redhat.com > ___ > maintainers mailing list > maintain...@gluster.org > http://lists.gluster.org/mailman/listinfo/maintainers > > >>> ___ > >>> maintainers mailing list > >>> maintain...@gluster.org > >>> http://lists.gluster.org/mailman/listinfo/maintainers > >>> > >> ___ > >> Gluster-devel mailing list > >> Gluster-devel@gluster.org > >> http://lists.gluster.org/mailman/listinfo/gluster-devel > >> > > ___ > > Gluster-devel mailing list > > Gluster-devel@gluster.org > > http://lists.gluster.org/mailman/listinfo/gluster-devel > > > ___ > maintainers mailing list > maintain...@gluster.org > http://lists.gluster.org/mailman/listinfo/maintainers ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
On 05/31/2018 09:22 AM, Shyam Ranganathan wrote: > As brick-mux tests were failing (and still are on master), this was > holding up the release activity. > > We now have a final fix [1] for the problem, and the situation has > improved over a series of fixes and reverts on the 4.1 branch as well. > > So we hope to branch RC0 today, and give a week for package and upgrade > testing, before getting to GA. The revised calendar stands as follows, > > - RC0 Tagging: 31st May, 2018 RC0 Tagged and off to packaging! > - RC0 Builds: 1st June, 2018 > - June 4th-8th: RC0 testing > - June 8th: GA readiness callout > - June 11th: GA tagging > - +2-4 days release announcement > > Thanks, > Shyam > > [1] Last fix for mux (and non-mux related): > https://review.gluster.org/#/c/20109/1 > > On 05/09/2018 03:41 PM, Shyam Ranganathan wrote: >> Here is the current release activity calendar, >> >> - RC0 tagging: May 14th >> - RC0 builds: May 15th >> - May 15th - 25th >> - Upgrade testing >> - General testing and feedback period >> - (on need basis) RC1 build: May 26th >> - GA readiness call out: May, 28th >> - GA tagging: May, 30th >> - +2-4 days release announcement >> >> Thanks, >> Shyam >> >> On 05/06/2018 09:20 AM, Shyam Ranganathan wrote: >>> Hi, >>> >>> Release 4.1 has been branched, as it was done later than anticipated the >>> calendar of tasks below would be reworked accordingly this week and >>> posted to the lists. >>> >>> Thanks, >>> Shyam >>> >>> On 03/27/2018 02:59 PM, Shyam Ranganathan wrote: Hi, As we have completed potential scope for 4.1 release (reflected here [1] and also here [2]), it's time to talk about the schedule. - Branching date (and hence feature exception date): Apr 16th - Week of Apr 16th release notes updated for all features in the release - RC0 tagging: Apr 23rd - Week of Apr 23rd, upgrade and other testing - RCNext: May 7th (if critical failures, or exception features arrive late) - RCNext: May 21st - Week of May 21st, final upgrade and testing - GA readiness call out: May, 28th - GA tagging: May, 30th - +2-4 days release announcement and, review focus. As in older releases, I am starring reviews that are submitted against features, this should help if you are looking to help accelerate feature commits for the release (IOW, this list is the watch list for reviews). This can be found handy here [3]. So, branching is in about 4 weeks! Thanks, Shyam [1] Issues marked against release 4.1: https://github.com/gluster/glusterfs/milestone/5 [2] github project lane for 4.1: https://github.com/gluster/glusterfs/projects/1#column-1075416 [3] Review focus dashboard: https://review.gluster.org/#/q/starredby:srangana%2540redhat.com ___ maintainers mailing list maintain...@gluster.org http://lists.gluster.org/mailman/listinfo/maintainers >>> ___ >>> maintainers mailing list >>> maintain...@gluster.org >>> http://lists.gluster.org/mailman/listinfo/maintainers >>> >> ___ >> Gluster-devel mailing list >> Gluster-devel@gluster.org >> http://lists.gluster.org/mailman/listinfo/gluster-devel >> > ___ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-devel > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
As brick-mux tests were failing (and still are on master), this was holding up the release activity. We now have a final fix [1] for the problem, and the situation has improved over a series of fixes and reverts on the 4.1 branch as well. So we hope to branch RC0 today, and give a week for package and upgrade testing, before getting to GA. The revised calendar stands as follows, - RC0 Tagging: 31st May, 2018 - RC0 Builds: 1st June, 2018 - June 4th-8th: RC0 testing - June 8th: GA readiness callout - June 11th: GA tagging - +2-4 days release announcement Thanks, Shyam [1] Last fix for mux (and non-mux related): https://review.gluster.org/#/c/20109/1 On 05/09/2018 03:41 PM, Shyam Ranganathan wrote: > Here is the current release activity calendar, > > - RC0 tagging: May 14th > - RC0 builds: May 15th > - May 15th - 25th > - Upgrade testing > - General testing and feedback period > - (on need basis) RC1 build: May 26th > - GA readiness call out: May, 28th > - GA tagging: May, 30th > - +2-4 days release announcement > > Thanks, > Shyam > > On 05/06/2018 09:20 AM, Shyam Ranganathan wrote: >> Hi, >> >> Release 4.1 has been branched, as it was done later than anticipated the >> calendar of tasks below would be reworked accordingly this week and >> posted to the lists. >> >> Thanks, >> Shyam >> >> On 03/27/2018 02:59 PM, Shyam Ranganathan wrote: >>> Hi, >>> >>> As we have completed potential scope for 4.1 release (reflected here [1] >>> and also here [2]), it's time to talk about the schedule. >>> >>> - Branching date (and hence feature exception date): Apr 16th >>> - Week of Apr 16th release notes updated for all features in the release >>> - RC0 tagging: Apr 23rd >>> - Week of Apr 23rd, upgrade and other testing >>> - RCNext: May 7th (if critical failures, or exception features arrive late) >>> - RCNext: May 21st >>> - Week of May 21st, final upgrade and testing >>> - GA readiness call out: May, 28th >>> - GA tagging: May, 30th >>> - +2-4 days release announcement >>> >>> and, review focus. As in older releases, I am starring reviews that are >>> submitted against features, this should help if you are looking to help >>> accelerate feature commits for the release (IOW, this list is the watch >>> list for reviews). This can be found handy here [3]. >>> >>> So, branching is in about 4 weeks! >>> >>> Thanks, >>> Shyam >>> >>> [1] Issues marked against release 4.1: >>> https://github.com/gluster/glusterfs/milestone/5 >>> >>> [2] github project lane for 4.1: >>> https://github.com/gluster/glusterfs/projects/1#column-1075416 >>> >>> [3] Review focus dashboard: >>> https://review.gluster.org/#/q/starredby:srangana%2540redhat.com >>> ___ >>> maintainers mailing list >>> maintain...@gluster.org >>> http://lists.gluster.org/mailman/listinfo/maintainers >>> >> ___ >> maintainers mailing list >> maintain...@gluster.org >> http://lists.gluster.org/mailman/listinfo/maintainers >> > ___ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-devel > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] [Gluster-Maintainers] Release 4.1: Branched
Here is the current release activity calendar, - RC0 tagging: May 14th - RC0 builds: May 15th - May 15th - 25th - Upgrade testing - General testing and feedback period - (on need basis) RC1 build: May 26th - GA readiness call out: May, 28th - GA tagging: May, 30th - +2-4 days release announcement Thanks, Shyam On 05/06/2018 09:20 AM, Shyam Ranganathan wrote: > Hi, > > Release 4.1 has been branched, as it was done later than anticipated the > calendar of tasks below would be reworked accordingly this week and > posted to the lists. > > Thanks, > Shyam > > On 03/27/2018 02:59 PM, Shyam Ranganathan wrote: >> Hi, >> >> As we have completed potential scope for 4.1 release (reflected here [1] >> and also here [2]), it's time to talk about the schedule. >> >> - Branching date (and hence feature exception date): Apr 16th >> - Week of Apr 16th release notes updated for all features in the release >> - RC0 tagging: Apr 23rd >> - Week of Apr 23rd, upgrade and other testing >> - RCNext: May 7th (if critical failures, or exception features arrive late) >> - RCNext: May 21st >> - Week of May 21st, final upgrade and testing >> - GA readiness call out: May, 28th >> - GA tagging: May, 30th >> - +2-4 days release announcement >> >> and, review focus. As in older releases, I am starring reviews that are >> submitted against features, this should help if you are looking to help >> accelerate feature commits for the release (IOW, this list is the watch >> list for reviews). This can be found handy here [3]. >> >> So, branching is in about 4 weeks! >> >> Thanks, >> Shyam >> >> [1] Issues marked against release 4.1: >> https://github.com/gluster/glusterfs/milestone/5 >> >> [2] github project lane for 4.1: >> https://github.com/gluster/glusterfs/projects/1#column-1075416 >> >> [3] Review focus dashboard: >> https://review.gluster.org/#/q/starredby:srangana%2540redhat.com >> ___ >> maintainers mailing list >> maintain...@gluster.org >> http://lists.gluster.org/mailman/listinfo/maintainers >> > ___ > maintainers mailing list > maintain...@gluster.org > http://lists.gluster.org/mailman/listinfo/maintainers > ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
