Nice! Thanks & Regards, Amogh Desai
On Sat, May 31, 2025 at 4:30 PM Jarek Potiuk <ja...@potiuk.com> wrote: > And another small follow-up before we release 3.0.2 as Jed pointed out in > the previous PR, those example dags from standard provider do not really > fit the same pattern as system tests + example dags in google, amazon and > other providers - so we should likely put them in example_dags folder and > for sure remove test_common snippets from them before releasing 3.0.2. > https://github.com/apache/airflow/pull/51260 > > On Thu, May 29, 2025 at 7:55 PM Jarek Potiuk <ja...@potiuk.com> wrote: > > > As discussed at the last dev call - before we release 3.0.2 , I brought > > back example_dags back to "airflow" package - until we do the complete > > "Example Refurbish" - this one should bring back the same "experience" > for > > example dags as before - including standalone airflow and airflow > installed > > in venv: > > > > https://github.com/apache/airflow/pull/51192 > > > > This is done with a bit of cheating. The "standard" examples are still in > > "standard" provider - thanks to that all the docs work nicely, but in our > > repo I created a symbolic link "standard" in the 'examples" directory to > > the "standard" examples - and I removed all the "hacks" to read them from > > standard provider in breeze. I checked that it nicely works for package > > preparation (the standard symbolic links are copied as folder to both > sdist > > and whl. packages) > > > > This way "source of truth" - standard examples are in the standard > > provider, but they are also present in the main airflow folder. This has > a > > bit of a watch-out, because when we cherry-pick it to 3-0-test, we should > > also probably cherry-pick any changes to standard provider's examples - > for > > now https://github.com/apache/airflow/pull/50864 (and it's predecessor) > > is the only change v3-0-test vs. main. > > > > > > J. > > > > > > On Mon, May 12, 2025 at 8:44 AM Amogh Desai <amoghdesai....@gmail.com> > > wrote: > > > >> Sounds great Jens, thanks for creating the channel and > >> thanks for updating us on it. > >> > >> Thanks & Regards, > >> Amogh Desai > >> > >> > >> On Sun, May 11, 2025 at 7:54 PM Jens Scheffler > <j_scheff...@gmx.de.invalid > >> > > >> wrote: > >> > >> > Hi, > >> > > >> > following-up on the discussion we had and the verbal discussion in > >> > Airflow 3 Dev call May 22nd (see notes in > >> > > >> > > >> > https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+3+Dev+call%3A+Meeting+Notes#Airflow3Devcall:MeetingNotes-22May2025 > >> ) > >> > > >> > I propose the following next steps: > >> > > >> > 1) start a separate interactive discussion in Slack in channel > >> > #sig-examples (https://apache-airflow.slack.com/archives/C08RUFEL466) > - > >> > Note: If you have the feeling we need to discuss in Devlist, please > also > >> > feel free to replay to the thread here. Butmaybe we need to have a bit > >> > more interaction w/o generating too much noise in the devlist) > >> > > >> > 2) Within the discussion document some targets and tasks as a > concept. I > >> > started a skeleton in > >> > > https://cwiki.apache.org/confluence/display/AIRFLOW/Examples+Refurbish > >> - > >> > Feel free to extend, comment! > >> > > >> > 3) Once our discussion in #sig-examples/Slack/Devlist is sttled I > >> > propose a follow-up [VOTE] in the devlist validating agreement > >> > > >> > Everybody who likes to join and engage, please feel free to join > >> > #sig-examples in Slack or let me know! > >> > > >> > Jens > >> > > >> > On 01.05.25 06:54, Daniel Standish wrote: > >> > > Yeah, along Jens lines... > >> > > > >> > > Yes, probably too many example dags. Probably this is a consequence > >> of > >> > > using them as test dags. > >> > > > >> > > Probably ideally we are more selective in curating example dags and > >> > > distinguishing them from test dags. > >> > > > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org > >> > For additional commands, e-mail: dev-h...@airflow.apache.org > >> > > >> > > >> > > >
