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
[Gluster-devel] Coverity covscan for 2018-06-01-b21f742f (master branch)
GlusterFS Coverity covscan results are available from http://download.gluster.org/pub/gluster/glusterfs/static-analysis/master/glusterfs-coverity/2018-06-01-b21f742f ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
Re: [Gluster-devel] Running regressions with GD2
Thanks Nigel for initiating this email. This is a pending (and critical) task for us to get back on to it and take it to completion as getting a confidence on overall gluster features to work with GD2, its a very important task for us. Its just that in 4.1 team was busy in finishing some of the features set and hence we couldn’t take this forward. We shall be able to get back in few days time with a complete plan and timeline for this task. On Fri, 1 Jun 2018 at 15:33, Nigel Babu wrote: > Hello, > > We're nearly at 4.1 release, I think now is a time to decide when to flip > the switch to default to GD2 server for all regressions or a nightly GD2 > run against the current regression. > > Can someone help with what tasks need to be done for this to be > accomplished and how the CI team can help. I'd like to set a deadline to > this, so the task list will help me pick a good date. > > I'm happy to help in terms of Infra/CI in any way I can for this effort. > > -- > nigelb > ___ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://lists.gluster.org/mailman/listinfo/gluster-devel -- - Atin (atinm) ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
[Gluster-devel] Running regressions with GD2
Hello, We're nearly at 4.1 release, I think now is a time to decide when to flip the switch to default to GD2 server for all regressions or a nightly GD2 run against the current regression. Can someone help with what tasks need to be done for this to be accomplished and how the CI team can help. I'd like to set a deadline to this, so the task list will help me pick a good date. I'm happy to help in terms of Infra/CI in any way I can for this effort. -- nigelb ___ Gluster-devel mailing list Gluster-devel@gluster.org http://lists.gluster.org/mailman/listinfo/gluster-devel
