So what do we do now? Can we narrow down what features we want to merge still?
In any case, it would be good to branch off the 0.8 release branch soon, as we have major changes waiting to be merged that should only go into the next major version (0.9). Stephan On Mon, Dec 8, 2014 at 1:36 PM, Stephan Ewen <se...@apache.org> wrote: > Hey! > > I sort of agree with Ufuk. Type system rework easily leads to followup > issues. I suspect that if we wait for that, there is not going to be a > release before Christmas. > > How essential is that functionality? Is the streaming API fundamentally > broken without that, or is it rather a set of features that define the next > big step? For issues that fall into the first category, let's prioritize > and include them. But for issues in the second category, I think it is fine > to postpone them to the next release (which we may want to do rather soon > after). > > Stephan > > > On Mon, Dec 8, 2014 at 1:28 PM, Ufuk Celebi <u...@apache.org> wrote: > >> On Mon, Dec 8, 2014 at 11:05 AM, Márton Balassi <balassi.mar...@gmail.com >> > >> wrote: >> >> > Ok guys, then I also agree to skip 0.7.1 and go straight for 0.8.0. As >> for >> > the streaming side we would like to finish a couple of features (lambda >> 8 >> > support, type handling rework, filesystems i/o support, at least once >> fault >> > tolerance prototype). I'm confident that we can get most of the things >> that >> > we really want in there done by the end of this week. >> > >> >> >> This sounds like a lot. I can understand that you want as much in a >> release >> as possible though. ;) Would it make sense to reduce this list to the most >> important changes and keep the rest for 0.8.1? >> > >
