syun64 commented on issue #872:
URL: https://github.com/apache/iceberg-python/issues/872#issuecomment-2229454584
Very exciting to hear that you were already able to get a package published
through Github Actions! For now, I'm leaning towards this approach of having a
separate namespace for for nightly builds like `pyiceberg-nightly`.
One downside of that approach is that this will create a name collision
issues if users accidentally install both `pyiceberg` and `pyiceberg-nightly`
packages in the same environment.
But I think there's still a lot to gain by separating out the package
namespace of an intentional publication (release candidates, and successful
releases) versus an automated nightly publication from main, just in terms of
how easy it would be for us to manage our packages. I'm not quite sure what the
best way to do this would be, but I would imagine we would want to support the
concept of having a retention policy on the nightly package as well, so we
clean up packages that were published a year ago, as an example.
Here's a link to some relevant discussion on this topic on a [PyPi
warehouse discussion thread](https://github.com/pypi/warehouse/issues/8792)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org
For additional commands, e-mail: issues-h...@iceberg.apache.org
