You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@madlib.apache.org by Rahul Iyer <ri...@apache.org> on 2018/08/06 22:31:39 UTC
v1.15 release status
Hi MADlibers,
We're close to releasing v1.15. We've two pending issues
<https://issues.apache.org/jira/browse/MADLIB-1195?jql=project%20%3D%2012318923%20AND%20resolution%20%3D%20Unresolved%20AND%20fixVersion%20%3D%20v1.15%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC>
in v1.15 that need to be resolved (or postponed) to start the release
process.
We can move these issues to the next release, unless someone has an opinion
about wrapping them in v1.15.
Best.
Rahul
Re: v1.15 release status
Posted by Jingyi Mei <jm...@pivotal.io>.
+1 with Frank. We should go with what we have now.
On Mon, Aug 6, 2018 at 3:41 PM, Frank McQuillan <fm...@pivotal.io>
wrote:
> i'd suggest moving them to a later release and going with what we have now.
>
> Frank
>
> On Mon, Aug 6, 2018 at 3:31 PM, Rahul Iyer <ri...@apache.org> wrote:
>
> > Hi MADlibers,
> >
> > We're close to releasing v1.15. We've two pending issues
> > <https://issues.apache.org/jira/browse/MADLIB-1195?jql=
> > project%20%3D%2012318923%20AND%20resolution%20%3D%20Unresolved%20AND%
> > 20fixVersion%20%3D%20v1.15%20ORDER%20BY%20priority%
> 20DESC%2C%20key%20ASC>
> > in v1.15 that need to be resolved (or postponed) to start the release
> > process.
> > We can move these issues to the next release, unless someone has an
> opinion
> > about wrapping them in v1.15.
> >
> > Best.
> > Rahul
> >
>
Re: v1.15 release status
Posted by Frank McQuillan <fm...@pivotal.io>.
i'd suggest moving them to a later release and going with what we have now.
Frank
On Mon, Aug 6, 2018 at 3:31 PM, Rahul Iyer <ri...@apache.org> wrote:
> Hi MADlibers,
>
> We're close to releasing v1.15. We've two pending issues
> <https://issues.apache.org/jira/browse/MADLIB-1195?jql=
> project%20%3D%2012318923%20AND%20resolution%20%3D%20Unresolved%20AND%
> 20fixVersion%20%3D%20v1.15%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC>
> in v1.15 that need to be resolved (or postponed) to start the release
> process.
> We can move these issues to the next release, unless someone has an opinion
> about wrapping them in v1.15.
>
> Best.
> Rahul
>