On Sat, Feb 9, 2019 at 12:14 PM Nick Couchman <[email protected]> wrote: > > > > > Definitely. > > > > Outside of the above, it looks like scope is generally settled. I'll move > > forward with the creation of 1.1.0 branches, etc.: > > > > http://guacamole.apache.org/release-procedures-part1/ > > > > Very nice. > > Do we want to create any branches for other versions - 1.1.1, 1.2.0, 2.0.0, > etc. - at this point? Or just continue to be careful about what gets > merged to master until we get past 1.1.0? >
IMHO, let's hold off on creating other release branches until the time comes to make a decision about API-incompatible changes. We should do what we can to ensure that all changes are compatible, and bristle accordingly at changes which propose to break compatibility. If breaking compatibility is the only option, then I suppose it's discussion time for whether the community wants to support 1.2.x and 2.0.x branches simultaneously. - Mike
