Actually, I'd like to see STREAMS-243 and STREAMS-183 fixed first to ensure S3 and ES are working and not dropping documents before the release.
STREAMS-213 would be nice-to-have from a documentation perspective in 0.1. Does anyone have strong feelings about other bugs we should push to fix before 0.1? Steve Blackmon [email protected] On Thu, Dec 4, 2014 at 10:06 AM, Steve Blackmon <[email protected]> wrote: > +1. It is time. Once we finish and merge 225 and make Jenkins happy, > let's do it. > > I just got access to modify the Jenkins build plan - I'll focus on this > today. > > Steve Blackmon > [email protected] > > On Thu, Dec 4, 2014 at 7:29 AM, Matt Franklin <[email protected]> > wrote: > >> n Thu Dec 04 2014 at 7:56:34 AM Robert Douglas < >> [email protected]> wrote: >> >> > Hi all, >> > >> > Over the past week or two, the Streams build has been pretty unstable. >> > There are also a bunch of pull requests currently open; some to fix >> > existing issues and others to improve functionality or add features. In >> the >> > interest of stability, I propose that we merge in the bug fix pull >> > requests, ensure the build is operational, and then cut a 0.1 release. >> This >> > way we can continue adding new functionality without sacrificing >> stability. >> > >> > Thoughts? >> > >> >> +1. One of the biggest challenges for an Incubating Apache project is >> getting the release correct. >> >> >> > >> > Thanks, >> > Robert Douglas >> > >> > >
