Hi Yufei
Yeah, pre-1.0 or 1.0-alpha is OK for me. Good idea.
Regards
JB
On Mon, Mar 17, 2025 at 7:59 AM Yufei Gu wrote:
>
> Thanks for the explanation, JB! In that case, we may focus on 0.10.0 only.
> How about a name like pre-1.0, which clarifies that it's a release mainly
> to test out someth
Thanks for the explanation, JB! In that case, we may focus on 0.10.0 only.
How about a name like pre-1.0, which clarifies that it's a release mainly
to test out something for 1.0.0?
Yufei
On Fri, Mar 14, 2025 at 11:33 PM Jean-Baptiste Onofré
wrote:
> Hi Yufei
>
> That's a good point.
>
> What
Hi,
I’ve made quite some progress on building the integration for NoSQL
databases. The initial code supports MongoDB [A], but is not limited to
that database. A working implementation has been pushed as a draft-PR
[1] for illustration purposes how it can look like when it is fully
integrated.
+1
From: Jean-Baptiste Onofré
Sent: Monday, March 17, 2025 6:48:37 AM
To: dev@polaris.apache.org
Subject: Re: [DISCUSS] Preparing 0.10.0 release including binary distributions
Usually, at Apache, we have two kind of versioning for "pre-release":
- 1.0.0.M1 and 1
Hi Robert,
Thanks for the update and the draft PR !
I would like to use this thread to thank Dennis. Big kudos to Dennis
for the changes he made: without these changes, it would have been
impossible to add new backends like MongoDB.
I propose we review and comment on Robert's PR.
I would also l
Using 1.0.0-preview1 implies the scope of 1.0 is well-defined... but my
impression is that it is not so.
I think the 0.10.0 version is clear enough that it comes before 1.0 and
does not have any implied scope.
While 0.10.0 is in progress, I believe we need to review the scope of 1.0
as a communit
Agreed with JB that 1.0-pre makes sense. My concern with 0.10.0 is that it
could mislead users into thinking an arbitrary cut from main qualifies as a
stable release.
Yufei
On Mon, Mar 17, 2025 at 10:30 AM Jean-Baptiste Onofré
wrote:
> It depends. For instance, Spark 4.0-preview started more
Wasn’t that the intent of naming the first release 0.9.0?
It seems wrong to cut a new version not from main
On Mon, Mar 17, 2025 at 12:16 AM Jean-Baptiste Onofré
wrote:
> Hi Yufei
>
> Yeah, pre-1.0 or 1.0-alpha is OK for me. Good idea.
>
> Regards
> JB
>
> On Mon, Mar 17, 2025 at 7:59 AM Yufei
I'm not sure I follow you, Eric.
0.10.0 or pre-1.0 will be cut from main, for sure.
It's also possible to cut 0.9.1 from the 0.9.x branch. It's pretty
classic for maintenance release, we do that in almost all Apache
projects.
So, my proposal is to cut 0.10.0 or pre-1.0 (both versions are ok for
Shall we name it like 1.0-pre? That aligns with common pattern across many
opensource projects, another thought is to make that more semver friendly
From: Yufei Gu
Sent: Sunday, March 16, 2025 11:59:27 PM
To: dev@polaris.apache.org
Subject: Re: [DISCUSS] Prepari
Usually, at Apache, we have two kind of versioning for "pre-release":
- 1.0.0.M1 and 1.0.0.RC1 (Apache Superset, Apache Camel, Apache Karaf,
Apache Cassandra, ... used this versioning)
- 1.0.0-preview1 (Apache Spark, Apache Flink, ... used this versioning)
For "clarity" for our community and users
It depends. For instance, Spark 4.0-preview started more than a year
ago, and the scope changed.
If we communicate clearly it's just a previous and the scope can still
change, it's acceptable.
I did the same on multiple projects: Camel 4.0.0.M1, M2, RC1, RC2,
were different in content.
I would se
Hi folks,
Some of you asked me: "what should we do heading to graduation ?"
To answer this question, I created Apache Polaris (incubating)
Maturity Model document listing the important items to work on:
https://docs.google.com/document/d/1qBIxClspQA--uQB0MS3LQO-uEDjdXtbqMPSRNbgeKdk/edit?usp=shar
Yea, I second that we don't have a consensus on what's supposed to be in
1.0. IMO, and very general, 1.0 should provide (at least) the basic
functionality, being easily consumable by users and being "rock solid".
Despite "1.0" (for engineers) is rather "just a number", it is quite a
strong sig
14 matches
Mail list logo
