Order the release commands properly

[amoghrajesh]

closes: #32877

Due to the documentation, updating the version is done after the TAG is set for the release. We should re order it

---

^ Add meaningful description above

Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[pierrejeambrun]

I don’t think this will have much effect. Git tagging is done as part of the breeze release command earlier than this

[amoghrajesh]

Can you point me to it @pierrejeambrun?

I can fix it if thats the case

[pierrejeambrun]

It's done by the following command, earlier in the process:

breeze release-management start-rc-process ...

The source for the command is here, the git_tag fn.

[amoghrajesh]

Thanks Pierre.

Can you point me to what you think is the issue? I can pick it up

[pierrejeambrun]

As I understand the reported issue, an idea would be to update the dockerfile airflow version when we upgrade the airflow version in the test-branch. (update airflow/__init__.py, airflow/api_connexion/openapi/v1.yaml, just before building the release note and running the breeze start-rc-process).

This way the tag will have the appropriate version in the dockerfile.

We already have a line:

Updating Dockerfile with the new version.

For updating version in main, we also need this in the test branch I think

[potiuk]

Yes. @amoghrajesh. Again - as I suggested before - you can try to PERFORM release process by following the guide and then you will see. what is going on and where you need to fix it. If you are attempting to fix it without actually following the release process, you are attempting to fix something theorethical. The ONLY way to improve the release process is to follow it yourself and find the place where to fix it. This is pretty much an imperative. You really need to experience what's going on if you want to fix it.

You will not be able to push or publish the packages, but all the rest you will be able to do it with your own hands - otherwise you will make changes like the last time where you misunderstood what you need to do.

[amoghrajesh]

Thanks for that @potiuk
I didn't try to experience it this time because it looked like I didn't have rights to create or push packages.

But from your comment, it looks like I can try out the rest of the stuff at the very least. Will be mindful of it and try it out.

Apologies for the confusion the last time