geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Swapnil Bawaskar <sbawas...@pivotal.io>
Subject Re: 1.3.0 release
Date Fri, 15 Sep 2017 20:11:53 GMT
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=92&projectKey=GEODE&view=planning&selectedIssue=GEODE-2788&versions=visible&selectedVersion=12340669

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’s probably not accurate) and gather consensus on any remaining
> 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’re still finalizing 1.2.1, but we released 1.2.0
> almost
> >> two months ago and we’ve 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
> >>
> >>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message