Deprecate all legacy client and components towards v1

[mantzas]

Is your feature request related to a problem? Please describe

For our v1 release we should only have only the latest clients and components.

Describe the solution

• Delete all legacy client and components
• Move all remaining to the right place

[wishperera]

Can i take this task once #581 is closed?

[mantzas]

Great. The only problem I see is since this is a breaking change and we have introduced multiple ones if we should follow the pattern of breaking one thing per release.
@wishperera @xenosdio @pkritiotis WDYT?

[wishperera]

I agree it is a safer approach.

[mantzas]

Would it make sense to list them all and add them as a bullet list and sub-tasks as we have done it here?

[xenosdio]

Great. The only problem I see is since this is a breaking change and we have introduced multiple ones if we should follow the pattern of breaking one thing per release.
@wishperera @xenosdio @pkritiotis WDYT?

It is a safer approach, but what would be optimal? Each version introducing a breaking change, hence upgrading Patron would require updating the code, or all changes occurring in one single version? I would lean toward the latter.

[wishperera]

@xenosdio makes a good point , from a consumer's view point, multiple breaking changes in consecutive releases is a hassle.

[mantzas]

So we have either a big-bang breaking change that affects everybody or smaller changes that might affect some people (based on what they use). Example: not all use AWS so the breaking change blast radius is smaller.

With breaking changes per release we can provide simpler upgrade instructions. Big bang might be a mess...
I am not sure about which is the best, I tend to prefer the later in smaller steps.