Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some new thoughts on cutting a release, especially scripts/release.sh #309

Merged
merged 37 commits into from
Jun 24, 2024

Conversation

daw3rd
Copy link
Member

@daw3rd daw3rd commented Jun 19, 2024

Why are these changes needed?

We need to automate the process of version management and release cutting. This is just a start with some initial thoughts based on recent discussion. Initial changes include

  1. Change .make.versions to define a common repo-wide version for all libraries and images.
  2. Add scripts/release.sh which tries to outline the steps needed to changes versions, create and tag a branch.
  3. Makefile new target to show-version based on .make.versions content
  4. Fixed a lot of set-versions problems
  5. Set all versions back to 0.2.0.dev6

Relies on make build publish being enough to actually publish the release to pypi and quay.io

Also see PR #297

Related issue number (if any).

#294

Signed-off-by: David Wood <dawood@us.ibm.com>
@daw3rd daw3rd marked this pull request as draft June 19, 2024 20:23
@@ -29,8 +29,6 @@ image::

load-image::

set-versions: workflow-reconcile-requirements
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please rebase, this should be fixed now in dev branch. thanks

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@roytman
Copy link
Member

roytman commented Jun 20, 2024

@daw3rd please do not do the release automation before we agree on the process. Some of the functionality can be done by GitHub actions

daw3rd added 18 commits June 20, 2024 11:17
Signed-off-by: David Wood <dawood@us.ibm.com>

n#
…rules

Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
Added docs in .make.versions
Add RELEASE.md.
Fix checking for pypi credentials

Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
@daw3rd
Copy link
Member Author

daw3rd commented Jun 20, 2024

@daw3rd please do not do the release automation before we agree on the process. Some of the functionality can be done by GitHub actions

I didn't think I was, except that I added the make tests for the test, clean, publish, build, set-versions top-level rules and some Makefiles needed to implement these

Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
Signed-off-by: David Wood <dawood@us.ibm.com>
…ter order in .make.defaults

Signed-off-by: David Wood <dawood@us.ibm.com>
set-versions:
$(MAKE) TOML_VERSION=$(DOCKER_IMAGE_VERSION) .defaults.update-toml
$(MAKE) TRANSFORM_PYTHON_VERSION=$(DOCKER_IMAGE_VERSION) .transforms.set-versions
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not think that's working , TRANSFORM_PYTHON_VERSION here is the value of PROFILER_RAY_VERSION while it should be PROFILER_PYTHON_VERSION. I tried to fix that in #323

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You are correct. To be more clear i set to ...=not-used when there is a no python versions (profiler, e/fdedup, doc_id). code_quality, malware and proglang_select did need the change.

HOWEVER, in the end since all version numbers are now the same, it was working ok :)

@roytman
Copy link
Member

roytman commented Jun 24, 2024

We should deploy 2 kfp-data-processing images one for KFPv1 and another for KFPv2. Will try to update the script to proceed with that.

.make.versions Outdated
CODE_QUALITY_RAY_VERSION=0.4.0$(RELEASE_VERSION_SUFFIX)
CODE_QUALITY_RAY_VERSION=$(DPK_VERSION)
CODE_QUALITY_PYTHON_VERSION=$(DPK_VERSION)
CODE_QUALITY_RAY_VERSION=$(DPK_VERSION)
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It appears twice.

@daw3rd daw3rd marked this pull request as ready for review June 24, 2024 19:20
… section for the repo's version dependencies.

Signed-off-by: David Wood <dawood@us.ibm.com>
@daw3rd daw3rd merged commit 5aace3a into dev Jun 24, 2024
18 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants