On Sat, Jun 2, 2018 at 12:11 AM Kaushal M <kshlmster@xxxxxxxxx> wrote: > > On Fri, Jun 1, 2018 at 6:19 PM Shyam Ranganathan <srangana@xxxxxxxxxx> 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 > > >>>> maintainers@xxxxxxxxxxx > > >>>> http://lists.gluster.org/mailman/listinfo/maintainers > > >>>> > > >>> _______________________________________________ > > >>> maintainers mailing list > > >>> maintainers@xxxxxxxxxxx > > >>> http://lists.gluster.org/mailman/listinfo/maintainers > > >>> > > >> _______________________________________________ > > >> Gluster-devel mailing list > > >> Gluster-devel@xxxxxxxxxxx > > >> http://lists.gluster.org/mailman/listinfo/gluster-devel > > >> > > > _______________________________________________ > > > Gluster-devel mailing list > > > Gluster-devel@xxxxxxxxxxx > > > http://lists.gluster.org/mailman/listinfo/gluster-devel > > > > > _______________________________________________ > > maintainers mailing list > > maintainers@xxxxxxxxxxx > > http://lists.gluster.org/mailman/listinfo/maintainers _______________________________________________ Gluster-devel mailing list Gluster-devel@xxxxxxxxxxx http://lists.gluster.org/mailman/listinfo/gluster-devel
