I agree we need more detailed instructions when we release 2.0. I think however we should wait with describing all details and instructions until we are closer to 2.0 release and we close the list of incompatibilities. I think for now just describing what changed should be enough.
We might yet want to revert some of the changes after we test it or there might be some sequence of operations to execute in the right order. Or we can combine several notes in Updating.md in one So I think it's best to do this kind of detailed description when we are preparing to actual release. J. On Mon, Dec 30, 2019 at 1:44 AM Kamil Breguła <[email protected]> wrote: > Hello, > > I think that before automatic tools, we should try to improve the manual > process. Some notes in the UPDATIND.md file are laconic, enigmatic and do > not allow you to migrate easily. > I have created PR, which contains some tips > https://github.com/apache/airflow/pull/6960/files > If we develop a precise manual migration process, we can automate it. I > think that it will be difficult for us to develop an automatic tool if the > manual process is complex, problematic and hardly understood by the user. > > Best regards, > Kamil > > > On Sun, Dec 29, 2019 at 1:27 PM Jarek Potiuk <[email protected]> > wrote: > > > I thought (and discussed with the users at various conferences) that we > > should make it super-easy to migrate to Airflow 2.0 when we release it. > > There is a number of incompatibilities that we mention in UPDATING.md so > we > > have quite a good 'base' for the list of incompatibilities but I think > > people have 100s or 1000s of DAGs sometimes so we should do better than > > that and provide a semi-automated migration tool for them. > > > > I'd love to hear what you think about it. > > > > I created a JIRA issue for it: > > https://issues.apache.org/jira/browse/AIRFLOW-6390 > > > > Here is what it says: > > > > Before releasing 2.0.0, we should create DAG migration tool for migrating > > DAGs to Apache Airflow 2.0 based on UPDATING.md and incompatibilities > > introduced in 2.0.0 > > > > It should mostly automate migrating DAGs and correcting the DAGs they > have > > where needed and print warnings for all cases that need some manual > review > > and corrections (with appropriate instructions). > > > > All the changes performed automatically should be explained and described > > and logged so that you can refer to changes made to your DAG. > > > > The instructions in case of manual corrections needed should be more > > detailed than just describing the changes in UPDATING.md. It should > mention > > consequences of such changes, reasoning and explain what the user might > > expect after migration. > > > > J. > > > > -- > > > > Jarek Potiuk > > Polidea <https://www.polidea.com/> | Principal Software Engineer > > > > M: +48 660 796 129 <+48660796129> > > [image: Polidea] <https://www.polidea.com/> > > > -- Jarek Potiuk Polidea <https://www.polidea.com/> | Principal Software Engineer M: +48 660 796 129 <+48660796129> [image: Polidea] <https://www.polidea.com/>
