> Bikeshedding about SemVer aside, I'm good with doing a 2.0 release in > the near future, but *please* lets use it to deprecate / drop stuff we > no longer want to maintain. Otherwise there's no real point to it.
I agree we can take this "opportunity" to drop some deprecated things like V1 API, but I don't see many other things. We are pretty good in deprecating things using our "two releases" rule which should be followed no matter if we bump major version or not. Let's not block 2.0 with any feature, I wrote the reasons, if we fit in some deprecation work why not. But's let's agree on 2.0 timeframe regardless of any planning. -- Later, Lukas @lzap Zapletal -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
