Good questions and points of discussion. I don't believe we have a clear path for handling this particular distinction, and would advocate for the community to devise a roadmap (our newly allocated Wiki would be a prime candidate). We had a request for features to tackle moving forward and received a lot of great feedback. Would like to see maybe reviving that thread and figuring out a consensus for the best path forward. The things that are in 0.2.0 will likely need some considerable planning and design, so creating associated pages for the big features so we can hash that out, reference, and discuss would provide a nice, collaborative space to help make those notions more concrete.
To that end, I think most tickets that provide these quick shots of functionality and fixes are apt for another 0.1.x release in lieu of the 0.2.0. As far as your concerns from branching, I think git actually buys you a lot from this standpoint with its (relatively) easy branch management and rebasing to keep branches good to go. To that end, develop is still the source for branches, however there may be logistics on when and how that is merged depending on scope. Not sure I completely follow the point about the release branch you mention, although I think that may just be a remnant of the last release process. The appropriate version is captured as a tag as I would anticipate. On Fri, May 29, 2015 at 8:55 AM, Dan Bress <[email protected]> wrote: > Hi, > > Joe recently brought up the idea of thinking about what new features go in > 0.2.0 and what bug fixes go in 0.1.1. Did we make a decision on that? I > bring it up because I could see three tickets being fixed/released > (quickly) in 0.1.1 (NIFI-633, NIFI-632, NIFI-638). > > > If we decide to do an 0.1.1, did we decide how that gets handled from a > git/branching point of view? Currently develop is labeled > '0.1.1-SNAPSHOT', and so is release-nifi-0.1.0-rc13< > https://github.com/apache/incubator-nifi/tree/release-nifi-0.1.0-rc13>. > > > So where would 0.1.1 fixes go, and where would 0.2.0 features go? > > > > Dan Bress > Software Engineer > ONYX Consulting Services >
