Thanks Pierre On Sun, 18 Oct 2026 at 17:23, Jarek Potiuk <[email protected]> wrote:
> Merged :) > > On Sun, Oct 18, 2026 at 6:11 PM Andrew Chang <[email protected]> > wrote: > > > Hi all, > > > > Since the lazy consensus period has passed without any objections, and > > there have been no further suggestions on PR #74589, I think we’re ready > to > > move forward with merging it! > > > > This should also help provide clearer guidance for contributors and their > > coding agents. > > > > Many thanks to Pierre for proposing the lazy consensus! > > > > Looking forward to continuing to contribute to the Airflow community. > > > > Best, > > Andrew > > > > Pierre Jeambrun <[email protected]>於 2026年10月14日週三，19:26寫道： > > > > > Hi all, > > > > > > Following the discussion thread started by Kaxil > > > https://lists.apache.org/thread.html/o4jknx0v7p0x8f1qvpvtl6ol8jm2ytjj > > I'm > > > calling for a lazy consensus on when to add newsfragments: > > > * Only use 'significant' newsfragments > > > > > > * Used for 'notable' changes that need user attention when upgrading > such > > > as a behaviour change, migration guidelines, etc... It doesn't have to > > be a > > > breaking change, but significant enough to be placed at the top of the > > > release note, interpreted as a "You need to read this before > upgrading". > > > > > > *Bug fixes, documentation, features and other changes are classified by > > > label type and used to construct the body of the release note similarly > > to > > > what we do today, no newsfragment needed. > > > > > > Update the agent.md and documentation accordingly. A PR is already > > opened: > > > https://github.com/apache/airflow/pull/74589 (thanks Andrew) > > > > > > The lazy consensus is running for 72 hours, until Saturday, 17 Oct > 2026, > > > 11:30 UTC. It is considered accepted if there are no objections. > > > > > > Pierre Jeambrun > > > > > >
