You can see all the discussions in https://lists.apache.org/[email protected]. The SLA discussion is in progress in the google docs for now (soon to be converted into cwiki AIP).
J, On Sun, Mar 19, 2023 at 10:15 PM Damian Shaw <[email protected]> wrote: > > I'm missing the previous conversation / who this is replying to and I don't > see a new AIP yet, is this still in progress? > > I would definitely want to be able provide feedback on an AIP for SLAs, while > the current SLA system is limited I am making heavy usage of it. > > -----Original Message----- > From: Jarek Potiuk <[email protected]> > Sent: Sunday, March 19, 2023 4:29 PM > To: [email protected] > Subject: Re: [DISCUSS] Airflow - New SLA AIP > > > Jarek - thank you for the suggestions - those are great suggestions in > > enhancing the proposal... Regarding your first point - how does deprecating > > an existing feature work for Airflow? Do we need to give a grace period of > > a minor or major patch over which we continue to support the feature after > > marking it for deprecation? Or do we remove them right away on a major > > version / minor version update? > > We raise a deprecation warning. You can see a number of examples in a number > of places. We cannot remove them in minor. We have not yet discussed the > timeline for Airflow 3 - but that is the first time when things can get > removed. > > > Also, do you folks have any thoughts on my last point listed in 'Other > > Considerations' section? I've highlighted the section to make it easier to > > identify, and I think it's an edge case that would be worth thinking about. > > responded in the doc. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > ________________________________ > Strike Technologies, LLC (“Strike”) is part of the GTS family of companies. > Strike is a technology solutions provider, and is not a broker or dealer and > does not transact any securities related business directly whatsoever. This > communication is the property of Strike and its affiliates, and does not > constitute an offer to sell or the solicitation of an offer to buy any > security in any jurisdiction. It is intended only for the person to whom it > is addressed and may contain information that is privileged, confidential, or > otherwise protected from disclosure. Distribution or copying of this > communication, or the information contained herein, by anyone other than the > intended recipient is prohibited. If you have received this communication in > error, please immediately notify Strike at [email protected], and > delete and destroy any copies hereof. > ________________________________ > > CONFIDENTIALITY / PRIVILEGE NOTICE: This transmission and any attachments are > intended solely for the addressee. This transmission is covered by the > Electronic Communications Privacy Act, 18 U.S.C ''2510-2521. The information > contained in this transmission is confidential in nature and protected from > further use or disclosure under U.S. Pub. L. 106-102, 113 U.S. Stat. 1338 > (1999), and may be subject to attorney-client or other legal privilege. Your > use or disclosure of this information for any purpose other than that > intended by its transmittal is strictly prohibited, and may subject you to > fines and/or penalties under federal and state law. If you are not the > intended recipient of this transmission, please DESTROY ALL COPIES RECEIVED > and confirm destruction to the sender via return transmittal. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
