potiuk commented on issue #10085: URL: https://github.com/apache/airflow/issues/10085#issuecomment-667622228
I love to switch to Github issues for planning. However I think we should organise it slightly differently, Github already has all the levels of details that we need and trying to squeeze it all into "Umbrella" issue is not the best use of those. I have two proposals: 1) I think it's much better if we use "Projects" features for each of the "sub-tasks" leading to 2.0 - for example I added my https://github.com/apache/airflow/projects/3 to complete the "Production Docker Image". It gives much better feeling of the status and progress. 2) I believe what is described in this issue as a description should be in 2.0.0 Milestone description and status should not be an issue, but more of a Wiki page as it will get continually updated, I think it might be a better idea to enable Wiki part of the GitHub and keep all the 2.0 related stuff in it (including the roadmap and status). It will be much better to keep it linked to the Github Issues and Projects, and at the same time we can eventually gradually move all the relevant stuff from the confluence - similarly as we did with JIRA issues. @mik-laj @kaxil @apache/airflow-committers WDYT? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
