#dev
Title
r
Robin Moffatt
05/30/2023, 4:48 PMis the release process documented somewhere?
we need to update it to include the new build & publish of the
-duckdbtreeverse/lakefs:0.101.0-duckdbb
Barak Amar
05/30/2023, 4:50 PM
yes, on dev repository
but it should be part of the automatic release process. not manual one, right?
r
Robin Moffatt
05/30/2023, 4:51 PMyes, it should be automated
I've found the checklist now, thanks Barak.
does it sound ok to:
1. Create an issue to get the automation created
2. update the release checklist to note that until automated, it needs doing manually
b
Barak Amar
05/30/2023, 8:18 PM
This is the issue https://github.com/treeverse/lakeFS/issues/5837 that we require for 1?
About 2 - yes, will require the steps to publish the +duckdb image
Question - do we build the image for all target architectures we currently build lakefs?
https://github.com/treeverse/lakeFS/pull/5984 DRAFT!
this one will automate the build.
Think this is the preferred way that will automate the release and split the build.
Pending testing before moving out of draft for review
r
Robin Moffatt
05/31/2023, 10:35 AMgreat, thanks @Barak Amar
is there a clever way to automate the reference to the image version in the docs? https://docs.lakefs.io/quickstart/launch.html
b
Barak Amar
05/31/2023, 4:36 PM
we can label the latest as duckdb
r
Robin Moffatt
05/31/2023, 4:38 PMso something like
treeverse/lakefs:latest-duckdbb
Barak Amar
05/31/2023, 4:39 PM
yes. or just duckdb
r
Robin Moffatt
05/31/2023, 4:40 PM👍 would you be ok to make this change? I can then update the quickstart doc
b
Barak Amar
05/31/2023, 4:41 PM
left the keyboard. can open an issue I will add it to the next release process. and check how to retag the current release until tomorrow
r
Robin Moffatt
05/31/2023, 4:41 PMno worries - I'll open an issue
thanks @Barak Amar
3 Views