Fix a couple Airflow release doc errors

[jedcunningham]

No description provided.

[phanikumv]

can you please mention the context of why we are doing this(in the description), is it because the last time RC packaging wasn't correct ?

[potiuk]

Approved with the command restoring :)

[potiuk]

can you please mention the context of why we are doing this(in the description), is it because the last time RC packaging wasn't correct ?

We usually place little context in case we correct those instructions @phanikumv :). The thing which such instructions (which you learn when you start doing release manager duty) is that pretty much every-single-time (TM) when you follow such instructions you find typos and mistakes, and changed circumstances that made previous instructions slightly wrong.

This means that every time the context wil be "Found those small typoes with last iteration of following the process". There are possibly tens or hundreds similar commits in the past :).

This is more-or-less fact of life we have to deal with until you just make it part of a fully automated CI/release process (in which case also things stop working occasionally and you need to fix it occasionally).

The good thing is that I hope in about 6-8 months the ASF will have a way to automate some of the release process so that we do not have to do it manually on "release-manager exclusively administered machines" (currently this is a requirement by the ASF) and hopefully, we will be able to make it more of trigger in a CI that we will keep on running on a daily basis.

[phanikumv]

can you please mention the context of why we are doing this(in the description), is it because the last time RC packaging wasn't correct ?

We usually place little context in case we correct those instructions @phanikumv :). The thing which such instructions (which you learn when you start doing release manager duty) is that pretty much every-single-time (TM) when you follow such instructions you find typos and mistakes, and changed circumstances that made previous instructions slightly wrong.

This means that every time the context wil be "Found those small typoes with last iteration of following the process". There are possibly tens or hundreds similar commits in the past :).

This is more-or-less fact of life we have to deal with until you just make it part of a fully automated CI/release process (in which case also things stop working occasionally and you need to fix it occasionally).

The good thing is that I hope in about 6-8 months the ASF will have a way to automate some of the release process so that we do not have to do it manually on "release-manager exclusively administered machines" (currently this is a requirement by the ASF) and hopefully, we will be able to make it more of trigger in a CI that we will keep on running on a daily basis.

Thank you Jarek, makes more sense to me now :)

[hussein-awala]

I just realized that my first review was a comment and not an approve