APEXMALHAR-2100. PR is open: https://github.com/apache/apex-malhar/pull/330

Regards,
Chaitanya

On Fri, Aug 5, 2016 at 1:10 PM, Priyanka Gugale <[email protected]>
wrote:

> APEXMALHAR-2171
> PR is open: https://github.com/apache/apex-malhar/pull/358
>
> -Priyanka
>
> On Fri, Aug 5, 2016 at 12:32 PM, Yogi Devendra <
> [email protected]
> > wrote:
>
> > Fix for APEXMALHAR-2176
> > PR open: https://github.com/apache/apex-malhar/pull/361
> >
> > ~ Yogi
> >
> > On 1 August 2016 at 11:59, Chinmay Kolhatkar <[email protected]>
> > wrote:
> >
> > > APEXMALHAR-2128 is already done. Somehow the status did not go to
> > resolved.
> > > Changed it now.
> > >
> > > On Fri, Jul 29, 2016 at 1:53 PM, Yogi Devendra <
> > > [email protected]
> > > > wrote:
> > >
> > > > APEXMALHAR-2116
> > > > https://github.com/apache/apex-malhar/pull/326
> > > >
> > > > @Ram
> > > > Your review comments are incorporated. Could you please have a look
> at
> > > > this?
> > > >
> > > > ~ Yogi
> > > >
> > > > On 29 July 2016 at 13:49, Thomas Weise <[email protected]>
> wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I would suggest to target the 3.5.0 release with an RC out perhaps
> 2
> > > > weeks
> > > > > from now, as there is a good amount of work that we should make
> > > available
> > > > > to the users:
> > > > >
> > > > >
> > > > >
> > > > https://issues.apache.org/jira/browse/APEXMALHAR/
> > > fixforversion/12335815/?selectedTab=com.atlassian.
> > > jira.jira-projects-plugin:version-issues-panel
> > > > >
> > > > > I also think that the following should go in:
> > > > >
> > > > > https://issues.apache.org/jira/browse/APEXMALHAR-2128
> > > > > https://issues.apache.org/jira/browse/APEXMALHAR-2142
> > > > > https://issues.apache.org/jira/browse/APEXMALHAR-2063
> > > > >
> > > > > Any other candidates?
> > > > >
> > > > > There are quite a few other PRs open:
> > > > >
> > > > > https://github.com/apache/apex-malhar/pulls
> > > > >
> > > > > Would be good to complete some more reviews for this release.
> > > > >
> > > > > Thanks,
> > > > > Thomas
> > > > >
> > > >
> > >
> >
>

Reply via email to