On 2021/10/07 15:30, Anand Buddhdev via nsd-users wrote: > NSD's release model is, IMHO, fast and loose. The NSD version number looks > like semver, ie. X.Y.Z. X should change when there are major, breaking > changes. Y should be reserved for new features, and Z should be for bug > fixes. > > Sadly, NSD went from 4.3.6 to 4.3.7 (looking like a bug fix update), but > introduced new features such as cookies and XOT, and the cookies were turned > on by default. An operator updating for bug fixes also get the new features, > which they may not want. Okay, I could also deal with new features, but the > fact that they're on by default is annoying. Suppose there's a bug in the > new feature. Suddenly an update enables the feature, and break things.
This reasoning doesn't quite make sense - so this was changed in one minor version (which at least one OS is shipping in a stable release) and now you're requesting an equally major change in a second minor version update? _______________________________________________ nsd-users mailing list nsd-users@lists.nlnetlabs.nl https://lists.nlnetlabs.nl/mailman/listinfo/nsd-users
