On 2020/11/05 17:34:25, Clebert Suconic <[email protected]> wrote: > *My* particular issue around this was not knowing what to do with > configuration parameters and APIs. > > If we simply remove those, older clients, older configs would not work any > longer. > > Is deprecation here a valid approach? Is there consensus around it ? Yes, we definitely recommend that you have a published deprecation plan, so that there's sufficient warning, and you don't break existing installations. Exactly what that timing is, is going to vary a great deal from one project to another, and only you and your users can figure that out.
- ActiveMQ and problematic language Rich Bowen
- Re: ActiveMQ and problematic language Clebert Suconic
- Re: ActiveMQ and problematic language michael.andre.pearce
- Re: ActiveMQ and problematic language Rich Bowen
- Re: ActiveMQ and problematic language Clebert Suconic
- Re: ActiveMQ and problematic language Jean-Baptiste Onofre
- Re: ActiveMQ and problematic languag... Christopher Shannon
- Re: ActiveMQ and problematic la... Clebert Suconic
- Re: ActiveMQ and problemati... Clebert Suconic
- Re: ActiveMQ and proble... Jean-Baptiste Onofre
- Re: ActiveMQ and proble... Clebert Suconic
- Re: ActiveMQ and proble... Jean-Baptiste Onofre
- Activemq and problematic language Rich Bowen
- Re: Activemq and problematic language Hossack, Etienne
