Thanks Jarek for proposing this. One minor question I have on this is how we put this side-by-side with the " *Install*" tab/button on our site.
Due to how Python packages work, for most users, there is no process of " *Download*". Instead, it is always an "*Install*" process. So for a new user visiting our site, does she/he click the "Install" button or click the "Downloads" page? This may cause minor confusion from the site UX aspect. But overall this is a good idea to me, if it's a requirement to have such a page in order to do the release announcement via [email protected]. XD On Wed, May 5, 2021 at 8:54 PM Tomasz Urbaszek <[email protected]> wrote: > +1 for the idea. I think this would be another way we can emphasize > the core/providers split and definitely. Probably we may consider > pointing to external providers, but not sure how this is aligned with > ASF rules. > > Cheers, > Tomek > > On Tue, 4 May 2021 at 13:00, Jarek Potiuk <[email protected]> wrote: > > > > Hello everyone, > > > > Just wanted to ask what do you think about adding a "Downloads" page to > the Airflow website? > > > > I am subscribed to "[email protected]" mailing list and see new > releases coming from various apache projects. It's a bit sad we do not > announce Airflow there. The main reason is that we have no "Downloads" page > similar to those (this is a strict requirement for "announce" messages): > > > > Few examples: > > > > * https://druid.apache.org/downloads.html > > * https://flink.apache.org/downloads.html > > > > Since we have now airflow core, providers, python client and soon helm > chart - maybe we should have such a "Downloads" page where we > (automatically) get the list of all latest packages released by Airflow, > including the checksums. signatures etc., all pointing to the right links > from https://downloads.apache.org/airflow/ > > > > Then we could officially announce releases :). > > > > WDYT? > > > > J. > > > > > > -- > > +48 660 796 129 >
