I agree with @ajelenak-thg and @marqh here -- I don't see a utility in having a next branch.
In general, master is supposed to be the "lastest" version, not ready for release yet. As for "CF isn't software that we're releasing with continuous delivery, having fewer, but larger, changes between versions is probably the better way to go." I'm not sure that it makes much difference how many changes there are between versions. Also -- maybe we should move to a more continuous delivery model -- why nothve point releases that have clarifications and typos corrected? What we should do is be sure to crate a branch for significant changes or additions, then they can be fully developed in that branch until ready for merging into master. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/cf-convention/cf-conventions/issues/130#issuecomment-399480412
