Skip to content

build: implement release process in odev#5592

Merged
tisonkun merged 14 commits intoapache:mainfrom
tisonkun:odev-release
Feb 2, 2025
Merged

build: implement release process in odev#5592
tisonkun merged 14 commits intoapache:mainfrom
tisonkun:odev-release

Conversation

@tisonkun
Copy link
Copy Markdown
Member

@tisonkun tisonkun commented Feb 1, 2025

Add:

  • just update-version for update all the release targets' version field
  • just release for generate all the release artifacts

Signed-off-by: tison <wander4096@gmail.com>
Signed-off-by: tison <wander4096@gmail.com>
Signed-off-by: tison <wander4096@gmail.com>
Signed-off-by: tison <wander4096@gmail.com>
Signed-off-by: tison <wander4096@gmail.com>
Signed-off-by: tison <wander4096@gmail.com>
Signed-off-by: tison <wander4096@gmail.com>
Signed-off-by: tison <wander4096@gmail.com>
Signed-off-by: tison <wander4096@gmail.com>
@github-actions github-actions bot added the releases-note/build The PR modifies build related content or has a title that begins with "build" label Feb 1, 2025
let files = output.lines().collect::<Vec<_>>();
archive_and_checksum(&package, &files)?;

let prefix = format!("apache-opendal-{}-src", package.name.replace("/", "-"));
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Need to add the version to prefix

Signed-off-by: tison <wander4096@gmail.com>
Signed-off-by: tison <wander4096@gmail.com>
Signed-off-by: tison <wander4096@gmail.com>
Signed-off-by: tison <wander4096@gmail.com>
Signed-off-by: tison <wander4096@gmail.com>

#### Release List

<!-- Generate release list by `./scripts/version.py`, please adapt with the actual needs. -->
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I wish we can have something like:

/// Generate a release plan in text at `target/release.txt` and print to console.
just release plan

/// Dev can edit the release plan by hand on need like bump to 0.y+1 instead of 0.0.z+1

/// Execuate the generated plan.
just release run

The release plan can also be pasted in to PR and discussion to make the review easier.


The current way works either, maybe we can merge and move on first.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I'd considering an interactive experience like cargo-release, that prompt package versions one by one and ask the release manager to input the correct version. Then commit the updates as well as generate a release list.

Perhaps pick up in the next month.

Copy link
Copy Markdown
Member

@Xuanwo Xuanwo left a comment

Choose a reason for hiding this comment

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

Let's move!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

releases-note/build The PR modifies build related content or has a title that begins with "build"

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants