Mailing-List: contact dev-help@geode.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geode.apache.org
MIME-Version: 1.0
References: <536C5EF0-446D-4B7C-81D3-DFF676325EBE@pivotal.io>
 <CANZq1gCBPQDsx8O5uQk=ry=c8eKsCqM27DhFE7FuuAceTZce-A@mail.gmail.com> <F4F456BD-DD9A-4AD0-A211-D0A12249E30E@pivotal.io>
In-Reply-To: <F4F456BD-DD9A-4AD0-A211-D0A12249E30E@pivotal.io>
From: Swapnil Bawaskar <sbawaskar@pivotal.io>
Date: Fri, 15 Sep 2017 20:11:53 +0000
Message-ID: <CANZq1gCrwTpF8LyBtcpMmv32JamQ_ETe1n5W6AEzefxuXoLnwQ@mail.gmail.com>
Subject: Re: 1.3.0 release
To: dev@geode.apache.org
Content-Type: multipart/alternative; boundary="001a113d73b6a68d40055940013b"
archived-at: Fri, 15 Sep 2017 20:12:14 -0000

--001a113d73b6a68d40055940013b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I took preliminary look and tagged some issues for 1.3.0.
Looks like we have 11 issues remaining:
https://issues.apache.org/jira/secure/RapidBoard.jspa?rapidView=3D92&projec=
tKey=3DGEODE&view=3Dplanning&selectedIssue=3DGEODE-2788&versions=3Dvisible&=
selectedVersion=3D12340669

Please take a look at these issues to see which are not critical to fix in
1.3 and also look at issues assigned to you/reported by you to see if they
must be tagged for 1.3.

Thanks!


On Fri, Sep 15, 2017 at 10:36 AM Anthony Baker <abaker@pivotal.io> wrote:

> Excellent!  Can you review the open issues currently tagged for 1.3.0 (I
> think it=E2=80=99s probably not accurate) and gather consensus on any rem=
aining
> changes needed?
>
> Anthony
>
> > On Sep 12, 2017, at 2:40 PM, Swapnil Bawaskar <sbawaskar@pivotal.io>
> wrote:
> >
> > Sound good.
> >
> > I would like to volunteer to be the release manager.
> >
> > Thanks!
> >
> >
> > On Tue, Sep 12, 2017 at 2:24 PM Anthony Baker <abaker@pivotal.io> wrote=
:
> >
> >> Hi all,
> >>
> >> I think we should begin discussing scope and timeline for the 1.3.0
> >> release.  I know we=E2=80=99re still finalizing 1.2.1, but we released=
 1.2.0
> almost
> >> two months ago and we=E2=80=99ve fixed almost 200 issues in that time.=
  IMO, we
> >> should complete 1.2.1 and then immediately turn around 1.3.0.
> >>
> >> Thoughts?  Any volunteers for release manager?
> >>
> >> Anthony
> >>
> >>
>
>

--001a113d73b6a68d40055940013b--