+1, Looking forward to this.

*Ankit Chaurasia*
HomePage <https://ankitchaurasia.info/> |  LinkedIn
<https://www.linkedin.com/in/sunank200/> |  +91-9987351649






On Tue, 26 Mar 2024 at 15:02, Phani Kumar <phani.ku...@astronomer.io.invalid>
wrote:

> +1 binding - looking forward to this one
>
> On Tue, Mar 26, 2024 at 1:11 PM Amogh Desai <amoghdesai....@gmail.com>
> wrote:
>
> > +1 binding
> >
> > I like the thought behind this and understand why this was repeatedly
> asked
> > by the community.
> > Good work on the proposal so far!
> >
> > Thanks & Regards,
> > Amogh Desai
> >
> >
> > On Tue, Mar 26, 2024 at 9:58 AM Rahul Vats <rah.sharm...@gmail.com>
> wrote:
> >
> > > +1 (non-binding)
> > >
> > > Regards,
> > > Rahul Vats
> > > 9953794332
> > >
> > >
> > > On Mon, 25 Mar 2024 at 22:46, Jed Cunningham <jedcunning...@apache.org
> >
> > > wrote:
> > >
> > > > Hello Airflow Community,
> > > >
> > > > I would like to start a vote on AIP-64: Keep TaskInstance try
> history.
> > > >
> > > > You can find the AIP here:
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-64%3A+Keep+TaskInstance+try+history
> > > >
> > > > Discussion Thread:
> > > > https://lists.apache.org/thread/vvm43tfchyo92hmf40fqvmq0f5845bjr
> > > >
> > > > This is the first step in the AIP-63 DAG Versioning journey, though
> > this
> > > > provides value in isolation as well:
> > > >
> > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/AIRFLOW/AIP-63%3A+DAG+Versioning
> > > >
> > > > The vote will last until 2024-03-28 17:30 UTC and until at least 3
> > > binding
> > > > votes have been cast.
> > > >
> > > > Consider this my binding +1.
> > > >
> > > > Please vote accordingly:
> > > >
> > > > [ ] + 1 approve
> > > > [ ] + 0 no opinion
> > > > [ ] - 1 disapprove with the reason
> > > >
> > > > Only votes from PMC members and committers are binding, but other
> > members
> > > > of the community are encouraged to check the AIP and vote with
> > > > "(non-binding)".
> > > >
> > > > Thanks,
> > > > Jed
> > > >
> > >
> >
>

Reply via email to