Timing sounds good. I can also comb through JIRA to see what we will need
to move to 1.3.

Kevin Risden


On Fri, Nov 2, 2018 at 9:39 AM larry mccay <lmc...@apache.org> wrote:

> Hi Kevin -
>
> Thank you for resurrecting this thread!
> I agree that we have had many upgrades and cleanup tasks as well as some
> meaningful enhancements.
> We should move on these as the 1.2.0 release as I don't believe that our
> KIP-11 based theme is going to provide much more in the next few weeks.
>
> Also, thank you for volunteering to be the RM for 1.2.
>
> +1 to your proposal and volunteering to be RM!
>
> I think if we are able to branch by Weds 11/7 that we should be able to
> have a RC by 11/14 or so and maybe have a successful by end of that week.
> I will start moving JIRAs out of 1.2.0 beginning this weekend.
>
> What are your thoughts on the above timing?
>
> thanks,
>
> --larry
>
> On Fri, Nov 2, 2018 at 9:03 AM
> Kevin Risden
> <kris...@apache.org> wrote:
>
> > There have been some great improvements to Apache Knox in the past 3
> months
> > since the 1.1.0 release on July 31. Many of these were cleanups to
> > dependencies and other build fixes. I am volunteering to be the release
> > manager for 1.2.0. I can start the process next week Wednesday Nov 7 to
> get
> > in any remaining fixes for 1.2.0.
> >
> > Kevin Risden
> >
> >
> > On Thu, Aug 30, 2018 at 7:30 PM larry mccay <lmc...@apache.org> wrote:
> >
> > > All -
> > >
> > > It is time to start planning for 1.2.0 release.
> > > There is a large backlog of JIRAs that were pushed out of previous
> > releases
> > > that we will need to triage before going any farther.
> > >
> > > There was also some discussion about a quick 1.2.0 release around cloud
> > > usecases. We will need to determine what usecases from KIP-11 or others
> > to
> > > add.
> > >
> > > I make a pass through the 1.2.0 backlog and move things out and narrow
> > the
> > > scope. Please feel free to ask for things to be moved back in, as
> > > appropriate.
> > >
> > > thanks,
> > >
> > > --larry
> > >
> >
>

Reply via email to