My take on some of these issues:

* #777 (persistence concurrency) can be closed.
* #552 (odd locations) is not a 1.0 blocker (but needs to be addressed)

Additionally, I think https://github.com/apache/polaris/pull/1532 also
needs to be addressed for 1.0 at least in most aspects. In order to
enable gradual progress while taking more time to resolve controversial
points, IMHO, https://github.com/apache/polaris/pull/1566 could be merged
first.

More specifically, I believe the user-facing warnings in 1532 need to be
added for 1.0, however, I can see that people have different opinions on
how exactly those warnings should be implemented... This is why I think
1566 might be worth merging first, even though it will create additional
rebasing / reworking burden on 1532.

No opinion on other issues.

Cheers,
Dmitri.

On Thu, May 15, 2025 at 5:39 PM Yufei Gu <flyrain...@gmail.com> wrote:

> Hi folks,
>
> Many users have been asking about the Polaris release, and I believe it's
> critical to have a formal, production-ready 1.0 release ASAP. Thanks to the
> community’s hard work, we’re very close with a few remaining blockers we
> need to resolve.
>
> To keep things moving, I scheduled a community meeting for the 1.0 release
> next Monday at 9 AM PST.  At the same time, sharing all issues marked with
> 1.0 blocker. We could resolve them here if possible. Feel free to chime in,
> remove the blocker tag if you think it's not a blocker, or pick any up.
> Thanks a lot in advance!
>
> Here is the list:
>
>    - Add CI for Python code (
>       <https://github.com/apache/polaris/issues/1058>#1058),
>       - Polaris persistence concurrency issues (#777)
>       <https://github.com/apache/polaris/issues/777>
>       - Task handling is incomplete (#774)
>       <https://github.com/apache/polaris/issues/774>
>       - Generated files in regtests/client/python/polaris (#755)
>       <https://github.com/apache/polaris/issues/755>
>       - Resources not properly closed, resource & memory leaks (#563)
>       <https://github.com/apache/polaris/issues/563>
>       - Make Polaris safe against certain unparseable locations (#552)
>       <https://github.com/apache/polaris/issues/552>
>       - [BUG] Assumption that cache eviction does not happen (#544)
>       <https://github.com/apache/polaris/issues/544>
>
> To make it more interactive, you can also comment on the google
> spreadsheet here:
>
> https://docs.google.com/spreadsheets/d/1GyLvp2cdYwioOsBwszNWiphZt_IIdo4LIfsZBFV88mc/edit?usp=sharing
>
> Yufei
>

Reply via email to