Hello!
You are receiving this email because this address was added
to the organisation Apache Cloudberry
on www.postgresql.org.
If this is not correct, please ignore this email and the
record of the address will be automatically deleted.
If this is correct, please click the below link to confirm
Hi everyone,
I have registered the org `Apache Cloudberry` on the PostgreSQL website.
You can find us here: https://www.postgresql.org/account/orglist/.
In the future, we can share Cloudberry's milestone news, such as releases,
through the PostgreSQL news channel.
Later, I will try to submit our
Run the test image successfully on my Macbook.
Approved. Thanks!
Best,
Dianjin Wang
On Mon, Dec 9, 2024 at 10:52 PM Dianjin Wang wrote:
> Thanks so much, Ed! I really appreciate it. I'll take a look later.
> If anyone else is available to help with the technical review, that would
> be better,
I like the Clickhouse year version number thought but feel it doesn't
communicate enough and could potentially mean a 2024 major release is where
Cloudberry is at in 2025 which is not a message worth communicating.
Along the year number line of thought, consider PostgreSQL does major
releases annu
Lots of great thoughts in this thread. Just want to share the sentiment as
someone who did professional services for Greenplum for almost a decade
that something like pg_upgrade would be really *really *great to have to
perform whatever conversions need to happen for major upgrades with the
user da
Thanks so much, Ed! I really appreciate it. I'll take a look later.
If anyone else is available to help with the technical review, that would
be better, thanks in advance.
On Monday, December 9, 2024, Ed Espino wrote:
> Dianjin,
>
> I have a PR (https://github.com/apache/cloudberry-devops-releas
On Mon, Dec 9, 2024 at 3:27 AM Ed Espino wrote:
>
> Hi Andrey,
>
> Thanks for bringing up the ClickHouse versioning model - it's a fascinating
> alternative to consider. I particularly like how the year-based scheme
> instantly communicates version currency to users and the tiered
> functionality
Dianjin,
I have a PR (https://github.com/apache/cloudberry-devops-release/pull/8)
that addresses this issue. If you could review and possibly approve, we
will have arm64 containers for Rocky 8 & 9.
-=e
On Sun, Dec 8, 2024 at 7:07 PM Dianjin Wang wrote:
> Hi Ed,
>
> I encountered an issue while
Hi Andrey,
Thanks for bringing up the ClickHouse versioning model - it's a fascinating
alternative to consider. I particularly like how the year-based scheme
instantly communicates version currency to users and the tiered
functionality approach.
After considering both approaches, I still lean tow
GitHub user edespino added a comment to the discussion: Sync up behavior on how
partition maintenance works between Greenplum 6/7 and Cloudberry
@yjhjstz As far as the Apache Cloudberry project is concerned, if they are
needed, these resources should be reworked to use the DockerHub Apache
Cl
GitHub user yjhjstz added a comment to the discussion: Sync up behavior on how
partition maintenance works between Greenplum 6/7 and Cloudberry
https://github.com/apache/cloudberry/blob/main/deploy/docker/Dockerfile
docker.artifactory.hashdata.xyz/docker/cbdb:devel-devtoolset-10-cbdb-docker-ub
GitHub user edespino added a comment to the discussion: Sync up behavior on how
partition maintenance works between Greenplum 6/7 and Cloudberry
@yjhjstz I am not sure what you mean by _"maybe we need a pipeline to sync
docker sandbox image ?"_
GitHub link:
https://github.com/apache/cloudber
Hi everyone,
Happy Monday! Last week, we received a lot of valuable feedback from the
community—thank you for sharing your insights! I truly appreciate the
strength of our community.
This week, we will continue the discussion. Please feel free to share more
thoughts via the mailing list or commen
Hi Ed,
Agree that we have the first version 2.0 first, which can help us go
through the entire process
and run the release pipeline.
Generally speaking, the time for the first release will be longer than
later. Thank you for volunteering as the release manager.
Your many experiences will definite
Hi Andrey,
Good to see you!!!
Yes, we need to add some checks in codes to let the program automatically
discover incompatible issues.
As for the issue of functional classification, it can be added with
corresponding tags during code review, and the document can be
associated with this information
GitHub user tuhaihe added a comment to the discussion: Sync up behavior on how
partition maintenance works between Greenplum 6/7 and Cloudberry
I'm uncertain about this, but I would like to involve @edespino.
GitHub link:
https://github.com/apache/cloudberry/discussions/691#discussioncomment-
> On 9 Dec 2024, at 11:26, Max Yang wrote:
>
> Welcome to discuss
Hi!
Let’s consider also Clickhouse versioning.
Clickhouse version is “year.release.patch”. Also they add tags “stable” or
“lts” to some releases.
The basic idea is that you have continuous development process not tied to
sp
17 matches
Mail list logo
