Hey Jakob, Cool, that's what I was trying to understand. So for now, we can just got an 0.7.1 branch, and back port bug fixes to it. That makes sense to me.
Cheers, Chris On 7/7/14 8:44 AM, "Jakob Homan" <[email protected]> wrote: >Generally, I'd say bug fixes go back to the appropriate branch (0.7 in >this >case) with an eye for a release (0.7.1 itc) and all new feature work goes >to trunk with the goal of a new x.0.0 release (0.8.0 itc). Whether or not >to actually cut and release the bug fix version would depend on the >severity of the bug and the demand from the user community, but having a >branch with the fixes ready to go seems prudent. If we decide to cut the >release, we don't need to go and find all the bugs and, if users don't >want >to wait for the release, they can build the branch themselves and deploy >it. >-jg > > >On Mon, Jul 7, 2014 at 8:35 AM, Chris Riccomini < >[email protected]> wrote: > >> Hey Guys, >> >> I noticed Jakob mentioned an 0.7.1 release in >> https://issues.apache.org/jira/browse/SAMZA-321. Are we planning on >>doing >> an 0.7.1 or just going straight to 0.8.0? >> >> I believe 0.8.0 should encompass some larger work (RocksDB upgrade, >> SAMZA-245, SAMZA-75, and YARN UI at least). The thing that concerns me >> about an 0.7.1 release is: when do we draw the line to cut the release? >>It >> looks like we've already found one nasty bug (SAMZA-321) in the 0.7.0 >> release. >> >> Cheers, >> Chris >>
