Kubeclient next: tracker of non backward compatible issues about kubeclient

[grosser]

• remove KubeException #195

[cben]

#240 probably (start or stop always wrapping SSL errors — either one may break code expecting current behavior, though current behavior is inconsistent.)

[abonas]

@moolitayer have you considered tracking backward incompatible issues by labeling them directly as such? tracking them here is nice, but manual tracking is fragile and some things can slip away

[moolitayer]

@abonas sounds great. Note I cannot label stuff ATM

[abonas]

@abonas sounds great. Note I cannot label stuff ATM

@moolitayer do you mean you cannot create new labels or you can't apply existing labels? I think you should be able to label things. Please check. I can create a new label, any preferred name?

[moolitayer]

As a non administrator (is that how it is called) I cannot assign labels. I think that why we label things using the bot in miq?

[abonas]

@moolitayer I believe that you're right. I can create a new label and assign to the relevant issues. How would you like this label to be called?

[moolitayer]

api change ?

[abonas]

api change ?

But backwards incompatible changes can be also non related to api change, so perhaps something more generic would be better

[moolitayer]

I sent PRs for the items mentioned here:

• #292
• #293
• #290

And some fixes:

• #288
• #291
• #294

I did not tackle #240 at this time. We need something to do for the next release ;)

[cben]

Out of date. Most already done. We've had a couple major releases since.
We have a couple outstand backward-incompatible changes, but tracking in issue like this doesn't scale, I'll use labels if needed.