Anything that's on the mailing list with [plugin author action required]
is likely breaking the API.
Recently we had the mass change from FactoryGirl to FactoryBot (which is
causing a lot of pain while cherry picking to older releases as well).
That had to be coordinated to sync it up with all plugins that were
using it.
I recall Stephen got so sick of his salt plugin breaking every time he
stopped maintaining it. That was mostly due to accidental breakage
because there's no clear API that we guarantee.
So I'd disagree we use SemVer.
On Wed, Nov 29, 2017 at 01:04:45PM +0100, Lukas Zapletal wrote:
Where exactly do we have any info about SemVer for core? I know about
plugins, but not core.
Core plugin API gets rarely broken, we've been only extending it in
the past (although there were some cases I think).
LZ
On Wed, Nov 29, 2017 at 12:01 PM, Greg Sutcliffe
<[email protected]> wrote:
On 29/11/17 10:45, Lukas Zapletal wrote:
Oh no, *everyone* is talking features. :-) This has really nothing to
do with features, because that can easily fall into "neverending"
category of what's big enough change or not.
Well, *technically* we use SemVer (I know, I know...). For that, while
features play a part, for me it's more about correctly calling out
breaking changes. So if we're every going to deprecate a bunch of stuff,
then we should call *that* 2.0. Otherwise it's just grandstanding ;)
*Technically* we should be including the internal plugin API in our
SemVer and bumping the major version every time plugins need to
update... but that might get silly :P
--
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.
