What's stopping you from releasing 0.0.1 on master? Get the code to a reasonable safe building spot and release it as 0.0.1.
NiFi doesn't need to be "done" to have a release; you don't need to jump directly from 0.0.1 to 1.0.0. I think "periodically" is a mistake (if by periodically, you basically mean randomly). I would instead suggest at least some form of stability on the releases, so that at minimum, most everything at least hopefully builds on the average platform. We should get in the habit of targeting JIRA tickets to milestones/releases and then moving to release. Release early - release often. 0.x.y releases are meant to be previews. Adam On Tue, Dec 16, 2014 at 11:05 PM, Joe Witt <[email protected]> wrote: > > Hello > > Does anyone feel that it would be a bad idea/mistake to periodically merge > develop into master as we work toward an initial release? > > Our intent for 'master' is to reflect the latest release but since we as of > yet do not have a release master is not reflecting any of those changes. > The very first thing folks try to build or operate on is master. > > I'm inclined to merge develop to master periodically just to help those > folks who may not realize that the 'develop' branch is where the fun is at. > > Anyway...curious to hear others views. > > Thanks > Joe >
