On Tue, Jan 22, 2019 at 19:45 Mike Jumper : > > > > > > Very nice. So shall we try for a 1.1.0 release, next (soon)? Maybe > squash > > a few more bugs that have surfaced from 1.0.0? > > > > Sounds good to me. > > > > And do we want to continue this versioning scheme, or continue to toss > > around some of the other ideas we've talked about? > > > > I think the new versioning scheme still seems sensible, but following 1.1.0 > I suggest we consider whether we should adopt a branching scheme like you > mentioned before. It would be nice to rely on being able to always produce > bugfix/minor releases without breaking compatibility.
Agreed, and, until we do handle the branching scheme, we need to be looking really close at any commits we make to insure that we're not Introducing changes that will impact compatibility, or, if we do, that we're introducing the necessary changes to keep things backward-compatible. Just something for all committers to be aware of at this point. > > Our issues with producing a release following 1.0.0 are more with the > current existence of an incompatible change on master (and the upgrade > headache that implies for any users affected by bugs in 1.0.0), not with > the numbering. Sounds good. -Nick
