Re: Creating a plugin-for-tests (was [foreman-dev] Plugin test failures)

- Original Message - > From: "Dominic Cleal" > To: foreman-dev@googlegroups.com > Sent: Tuesday, November 8, 2016 5:42:04 AM > Subject: Re: Creating a plugin-for-tests (was [foreman-dev] Plugin test > failures) > > On 07/11/16 15:39, Stephen Benjamin wrote: > > The

Re: Creating a plugin-for-tests (was [foreman-dev] Plugin test failures)

On 07/11/16 15:39, Stephen Benjamin wrote: > The wiki says that public methods will be deprecated and given a chance > to adjust our code in a reasonable time where possible: > > "Foreman will always strive to make no incompatible changes in a minor > release, but be prepared > to make

Re: Creating a plugin-for-tests (was [foreman-dev] Plugin test failures)

- Original Message - > From: ssht...@redhat.com > To: "foreman-dev" > Sent: Sunday, November 6, 2016 3:34:40 AM > Subject: Re: Re: Creating a plugin-for-tests (was [foreman-dev] Plugin test > failures) > > +1 for Daniel. > > IMHO most of the breakages

Re: Re: Creating a plugin-for-tests (was [foreman-dev] Plugin test failures)

On 11/03, Greg Sutcliffe wrote: > > > > You should file a bug against Foreman immediately if you see that a > > plugin interface has been broken, so we can ensure the change isn't > > released and a fix can be written. > > > > Fair enough - in this case it's an interface that wasn't tested and a